ΠΠΈΠ±Π»ΠΈΠΎΡΠ΅ΠΊΠ° Python ΡΠ°Π·ΡΠ°Π±ΠΎΡΡΠΈΠΊΠ° | ΠΠ½ΠΈΠ³ΠΈ ΠΏΠΎ ΠΏΠΈΡΠΎΠ½Ρ
ΠΠΎΠ³ΡΡΠΆΠ΅Π½ΠΈΠ΅ Π² CPython ΠΈ Π°ΡΡ ΠΈΡΠ΅ΠΊΡΡΡΡ. Π Π°Π·Π±ΠΈΡΠ°Π΅ΠΌ Π½Π΅ΠΎΡΠ΅Π²ΠΈΠ΄Π½ΠΎΠ΅ ΠΏΠΎΠ²Π΅Π΄Π΅Π½ΠΈΠ΅ (GIL, Memory), Best Practices (SOLID, DDD) ΠΈ ΡΠΎΠ½ΠΊΠΎΡΡΠΈ Django/FastAPI. Π Π΅ΡΠ°Π΅ΠΌ Π·Π°Π΄Π°ΡΠΈ Ρ ΠΏΠΎΠ΄Π²ΠΎΡ ΠΎΠΌ ΠΈ ΠΎΠΏΡΠΈΠΌΠΈΠ·ΠΈΡΡΠ΅ΠΌ Π°Π»Π³ΠΎΡΠΈΡΠΌΡ. π ΠΠΎ Π²ΡΠ΅ΠΌ Π²ΠΎΠΏΡΠΎΡΠ°ΠΌ @evgenycarter Π ΠΠ clck.ru/3Ko7Hq
Show moreπ Analytical overview of Telegram channel ΠΠΈΠ±Π»ΠΈΠΎΡΠ΅ΠΊΠ° Python ΡΠ°Π·ΡΠ°Π±ΠΎΡΡΠΈΠΊΠ° | ΠΠ½ΠΈΠ³ΠΈ ΠΏΠΎ ΠΏΠΈΡΠΎΠ½Ρ
Channel ΠΠΈΠ±Π»ΠΈΠΎΡΠ΅ΠΊΠ° Python ΡΠ°Π·ΡΠ°Π±ΠΎΡΡΠΈΠΊΠ° | ΠΠ½ΠΈΠ³ΠΈ ΠΏΠΎ ΠΏΠΈΡΠΎΠ½Ρ (@bookpython) in the Russian language segment is an active participant. Currently, the community unites 17 959 subscribers, ranking 7 250 in the Technologies & Applications category and 36 565 in the Russia region.
π Audience metrics and dynamics
Since its creation on Π½Π΅Π²ΡΠ΄ΠΎΠΌΠΎ, the project has demonstrated rapid growth, gathering an audience of 17 959 subscribers.
According to the latest data from 04 November, 2026, the channel demonstrates stable activity. Although there has been a change in the number of participants by -87 over the last 30 days and by -3 over the last 24 hours, overall reach remains high.
- Verification status: Not verified
- Engagement rate (ER): The average audience engagement rate is 5.31%. Within the first 24 hours after publication, content typically collects 2.70% reactions from the total number of subscribers.
- Post reach: On average, each post receives 953 views. Within the first day, a publication typically gains 485 views.
- Reactions and interaction: The audience actively supports content: the average number of reactions per post is 4.
- Thematic interests: Content is focused on key topics such as numbers, yield, ΠΌΠΎΠ΄ΡΠ»Ρ, none, Π΄Π΅ΠΊΠΎΡΠ°ΡΠΎΡ.
π Description and content policy
The author describes the resource as a platform for expressing subjective opinions:
βΠΠΎΠ³ΡΡΠΆΠ΅Π½ΠΈΠ΅ Π² CPython ΠΈ Π°ΡΡ
ΠΈΡΠ΅ΠΊΡΡΡΡ. Π Π°Π·Π±ΠΈΡΠ°Π΅ΠΌ Π½Π΅ΠΎΡΠ΅Π²ΠΈΠ΄Π½ΠΎΠ΅ ΠΏΠΎΠ²Π΅Π΄Π΅Π½ΠΈΠ΅ (GIL, Memory), Best Practices (SOLID, DDD) ΠΈ ΡΠΎΠ½ΠΊΠΎΡΡΠΈ Django/FastAPI. Π Π΅ΡΠ°Π΅ΠΌ Π·Π°Π΄Π°ΡΠΈ Ρ ΠΏΠΎΠ΄Π²ΠΎΡ
ΠΎΠΌ ΠΈ ΠΎΠΏΡΠΈΠΌΠΈΠ·ΠΈΡΡΠ΅ΠΌ Π°Π»Π³ΠΎΡΠΈΡΠΌΡ. π
ΠΠΎ Π²ΡΠ΅ΠΌ Π²ΠΎΠΏΡΠΎΡΠ°ΠΌ @evgenycarter
Π ΠΠ clck.ru/3Ko7Hqβ
Thanks to the high frequency of updates (latest data received on 05 November, 2026), the channel maintains relevance and a high level of publication reach. Analytics show that the audience actively interacts with content, making it an important point of influence in the Technologies & Applications category.
IndexError and KeyError, you may and should use LookupError, their common ancestor. It proved to be useful while accessing complex nested data:
try:
db_host = config['databases'][0]['hosts'][0]
except LookupError:
db_host = 'localhost'keys, values and items methods of dicts return view objects. They returned lists back in Python 2. The main difference is views don't store all items in memory, but yield them as long as they are requested. It works just fine as long as you are trying to iterate over keys (which you usually are), but you can't access elements by index anymore.
TypeError: 'dict_keys' object does not support indexing
You can argue that you don't really need indexing keys since their order is random, but it's not completely true. First of all, d.keys()[0] can be a proper way to get any key (use next(d.keys()) in Python 3). Second, since Python 3.6 dicts are insertion ordered in CPython and that will be a language feature since Python 3.7.dir(), callable(), getattr()
ΠΠΎΡΠΌΠΎΡΡΠ΅ΡΡ ΠΏΡΠΈΠΌΠ΅Ρ Π² ΠΎΠ½Π»Π°ΠΉΠ½ ΡΠ΅Π΄Π°ΠΊΡΠΎΡΠ΅.
ΠΠΎΠ΄ΠΏΠΈΡΡΠ²Π°ΠΉΡΠ΅ΡΡ Π½Π° ΠΊΠ°Π½Π°Π» π@pythonofffdict remembers the order of elements in Python3.6+, why do you need collections.OrderedDict anymore? That's why:
>>> OrderedDict(a=1, b=2) == OrderedDict(b=2, a=1)
False
>>> dict(a=1, b=2) == dict(b=2, a=1)
True<Π°ΡΠ³ΡΠΌΠ΅Π½ΡΡ>: <Π²ΡΡΠ°ΠΆΠ΅Π½ΠΈΠ΅>
Π’Π°ΠΊΠΈΠ΅ ΡΡΠ½ΠΊΡΠΈΠΈ ΠΎΠ±ΡΠ·Π°Π½ Π·Π½Π°ΡΡ ΠΊΠ°ΠΆΠ΄ΡΠΉ ΠΏΡΠΎΠ³ΡΠ°ΠΌΠΌΠΈΡΡ, ΠΈΡ
ΠΏΡΠΈΠΌΠ΅Π½Π΅Π½ΠΈΠ΅ ΡΠΈΠ»ΡΠ½ΠΎ ΡΠΎΠΊΡΠ°ΡΠ°Π΅Ρ ΠΊΠΎΠ΄.
ΠΠΎΠ΄ΠΏΠΈΡΡΠ²Π°ΠΉΡΠ΅ΡΡ Π½Π° ΠΊΠ°Π½Π°Π» π@pythonofff