Не попадитесь на накрученные каналы! Узнайте, не накручивает ли канал просмотры или подписчиков Проверить канал на накрутку
Прикрепить Телеграм-аккаунт Прикрепить Телеграм-аккаунт

Телеграм канал «Находки в опенсорсе: Python»

Находки в опенсорсе: Python
366
0
15
5
15
Легкие задачки в опенсорсе из мира Python

Чат: @opensource_findings_chat
Подписчики
Всего
1 054
Сегодня
0
Просмотров на пост
Всего
265
ER
Общий
25.14%
Суточный
21.25%
Динамика публикаций
Telemetr - сервис глубокой аналитики
телеграм-каналов
Получите подробную информацию о каждом канале
Отберите самые эффективные каналы для
рекламных размещений, по приросту подписчиков,
ER, количеству просмотров на пост и другим метрикам
Анализируйте рекламные посты
и креативы
Узнайте какие посты лучше сработали,
а какие хуже, даже если их давно удалили
Оценивайте эффективность тематики и контента
Узнайте, какую тематику лучше не рекламировать
на канале, а какая зайдет на ура
Попробовать бесплатно
Показано 7 из 366 постов
Смотреть все посты
Пост от 22.10.2026 13:51
142
0
2
🚀 New issue to fast-collections/fast-collections by @Khabib73
📝 Fix README fast-python button link to fast-collections (#185)


In the README, the fast-python button currently points to the wrong link. It should point to https://github.com/fast-collections instead.


#help_wanted #fast_collections
sent via relator
😁 5
Пост от 13.10.2026 20:08
102
0
1
🚀 New issue to wemake-services/django-modern-rest by @joefefs
📝 None endpoints still document a JSON null response body. (#1733)


What's wrong?

For endpoints that returns nothing, the server correctly sends an empty body, but the schema describes that response as application/json with a null schema.

Anything that trusts that schema (like an SDK generator) might try to read this null body as JSON and crash.

How it should be?

The response should NOT have a content key, only a { "description": "No Content" } should suffice so that clients relying on the spec won't try to read a body that does not exist.

Used versions
• django-modern-rest 0.16.0
• Django 5.2.17
• Python 3.13.12
• pydantic 2.13.5
• msgspec 0.22.0

OS information

macOS 26.3.2


#bug #good_first_issue #help_wanted #openapi #django_modern_rest
sent via relator
Пост от 10.10.2026 09:28
228
0
1
🚀 New issue to wemake-services/django-modern-rest by @sobolevn
📝 Set `security=None` for concrete login views (#1719)


We already set auth=None for them, but security= must also be disabled for the consistency.


#bug #good_first_issue #help_wanted #openapi #django_modern_rest
sent via relator
Пост от 06.10.2026 10:52
84
0
1
🚀 New issue to wemake-services/wemake-python-styleguide by @sobolevn
📝 Move skills into the `wemake_python_styleguide` folder (#3842)


https://library-skills.io requires skills to be in the source folder, see https://github.com/wemake-services/django-modern-rest/tree/master/dmr/.agents/skills

Let's move them there :)


#help_wanted #levelstarter #good_first_issue #wemake_python_styleguide #wps
sent via relator
Пост от 01.10.2026 21:32
22
0
1
🚀 New issue to wemake-services/django-modern-rest by @sobolevn
📝 Improve `dmr` skill with CSRF example (#1671)


Currently this example shows how to protect a view with CSRF:

django-modern-rest/dmr/.agents/skills/dmr/references/security.md

Lines 117 to 176 in 1cb33fb

However, there are better ways for CSRF protection, see csrf_exempt=False.
This example must show something else :)


#feature #good_first_issue #help_wanted #django_modern_rest
sent via relator
Пост от 01.10.2026 21:30
34
0
1
🚀 New issue to wemake-services/django-modern-rest by @sobolevn
📝 Improve `dmr` skill with `concrete_views` example (#1670)


We should state that using concrete_views is better than implementing your own views that do not change anything.

Add this to the dmr skill.


#feature #good_first_issue #help_wanted #django_modern_rest
sent via relator
Пост от 30.09.2026 10:52
67
0
1
🚀 New issue to wemake-services/django-modern-rest by @Izcarmt95
📝 Router.include() raises KeyError for a route with an empty pattern ('') (#1657)


Router.include() raises KeyError when the included router has a route with an empty pattern (path('', ...)), which is the usual way to mount a list endpoint at the router's prefix.

from dmr import Controller
from dmr.plugins.pydantic import PydanticSerializer
from dmr.routing import Router, path


class UserListController(Controller[PydanticSerializer]):
def get(self) -> str:
return 'ok'


users = Router('/users', [path('', UserListController.as_view(), name='users')])
api = Router('api')
api.include(users, namespace='users') # KeyError: '/users'

File ".../dmr/routing.py", line 173, in include
router.metadata_for(original_path),
File ".../dmr/routing.py", line 217, in metadata_for
return self._path_metadata[pattern]
KeyError: '/users'

Router.__init__ stores the metadata of the empty route under '/users/' (normalized with original_prefix=''), but include() looks it up as '/users' (normalized with original_prefix=router.prefix). Routes with a non-empty pattern (path('/<id>', ...)) are fine.

Workaround: use an empty router prefix and write the full segment in each route (Router('', [path('/users', ...)])).

• django-modern-rest 0.15.0 (it worked in 0.13.0, before include() looked up the metadata)
• Django 5.2, Python 3.13
⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯

AI disclaimer: an AI assistant was used only to help write this issue.


#bug #good_first_issue #help_wanted #opensource_september #django_modern_rest
sent via relator
Смотреть все посты