Telegram RegisterThe public register of Telegram

Channel

Cool and Fun Python

@Python3k

On this record: Growth · Engagement · What this channel posts · Reactions · Stars · Posts · Polls · Citations · Cite this entry

513subscribers

+0 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Telegram ID-1001156435082
TypeChannel
Username@Python3k
DescriptionКрутой и весёлый Python. Случаи из практики и не только.
CreatedBetween 1 April 2018 and 31 July 2021— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded8 August 2026
Last confirmed live8 August 2026
Measurements held2
On Telegramt.me/Python3k

Growth

5137 Aug 2026, 12:08 — 513 subscribers8 Aug 2026, 04:05 — 513 subscribers7 Aug 2026, 12:088 Aug 2026, 04:05
2 measurements taken within a single day. Dots are measurements; the straight line between them is drawn to join them, not to claim we know the path taken in between — snapshots are recorded only when a count changes, so gaps mean “no change observed”, never “interpolated”. The vertical axis spans 512–514 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
8 Aug 2026, 04:05513no change
7 Aug 2026, 12:08513first reading

Engagement

20 posts held, back to 4 November 2024the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 1 pageof Telegram’s post history, 20 posts per page.

Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 20 posts for this entry, the most recent from 25 February 2026. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Photos
30
Videos
8
Links
39

Lifetime counters from Telegram’s own channel header, read 8 August 2026 — not the date at the top of this page, which is when the subscriber count was last read. Below Telegram’s rounding threshold, so these counts are exact.

Video runtime
10m 20s
Average length
5m 10s

Measured directly from 2 videos with a duration reading, out of the posts we hold for this channel — not this channel’s whole posting history, only the sample this register has actually read. An exact reading to the second, taken from the post itself rather than from Telegram’s own rounded chrome, so it carries no mark.

Reaction mix

293 reactions across 19 posts, in 25 distinct kinds. The most used accounts for 26.3% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
7726.3%
👍4716.0%
🤯3612.3%
🎄175.80%
👨‍💻144.78%
134.44%
🤓124.10%
🔥113.75%
😎93.07%
🤷‍♂93.07%
72.39%
🍾62.05%
😁62.05%
❤‍🔥51.71%
💔51.71%
🤩51.71%
💯41.37%
🏆20.683%
🤔20.683%
👀10.341%
5 further kinds51.71%

No sentiment is inferred, and none should be read in. This table is ordered by count and by nothing else. Emoji do not carry stable meaning across languages or communities — 🙏 is thanks in one channel and mourning in another — so we publish which ones were pressed and how often, and pass no judgement on what an audience meant by them.

Precision. Telegram publishes reaction counts per emoji and short-forms each one — 4.34K, 1.2M — so any single kind at or above 1,000 reaches us at three significant figures, and only counts below 1,000 are exact. The shares above are ratios of those figures and carry the same error. This is also why the total here can differ slightly from a reaction total printed elsewhere on the page: both are sums of the same rounded parts, taken over samples with different edges.

Coverage. Reactions were read on 19 of the 20 sampled posts in this sample. Summed by Telegram’s own count on each post — not by adding up the per-emoji breakdown above — those same posts carry 293reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 20 most recent posts we hold, published 4 November 2024 to 25 February 2026, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.

Telegram Stars

Stars received
9
across the posts below
Posts paid on
4
of 20 we hold a reading for · 20%
Most on one post
5
single highest reading

A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @Python3k. Telegram publishes the count on the public post preview alongside ordinary reactions, and this register reads it there. It is the only figure on this site that measures money moving rather than attention.

Stars are not reactions, and the two are never added. They are rendered in the same strip on Telegram and counted in the same shape, but one is a tap and the other is a purchase. The reaction totals and the engagement rate elsewhere on this page exclude every figure in this section, and no rate here is computed against a reaction count.

This is not revenue, and we publish no currency figure. What a Star costs a reader and what it pays a channel are different numbers, Telegram takes a share we cannot observe, and the terms have changed. Converting a Star count into money would be an estimate dressed as a measurement, so the count is where we stop.

Counted over the 20 most recent posts we hold for this entry, published 4 November 2024 to 25 February 2026. Star counts above 1,000 reach us in Telegram’s short form and carry the same three-significant-figure rounding as everything else on this page.

Recent posts

25 Feb 2026, 07:11 UTC355 views10 reactionsread 8 August 2026

Магические числа Нравится волшебство? А вот и зря. Магические числа - антипаттерн в программировании. Вместо того, чтобы делать срез до -38, надо явно сказать что это за число. STANDART_SUFFIX = -38 text = "Очень много текста. Прям очень. И он весь нужен для кода. Стандартное завершение любого текста." useful_data = text[0:STANDART_SUFFIX] Тут должен начаться спор. Может быть хранить в константе положительное числ

7🤯2👨‍💻1

9 Feb 2026, 11:37 UTC373 views28 reactionsread 8 August 2026

Про ОС Оказывается мысли о том, что у программиста должен быть MacBook, а код надо писать под Linux, живы в умах юных (не по возрасту, в по опыту) айтишников до сих пор. Представляете, человек верит что нельзя программировать под Виндой, потому что код будет работать на сервере с Пингвином. При этом он же хочет взять кредит на Мак, потому что иначе ты не программист. Познавательная минутка 🤓 Python код работает од

🤓12😎9🤩5👨‍💻2

1 Feb 2026, 12:54 UTC389 views10 reactionsread 8 August 2026

Кто-нибудь пользовался новой удалённой отладкой в Python 3.14? Поделитесь своим опытом в комментария. 👨‍💻- пользовался pdb 🤷‍♂️ - что за зверь?

🤷‍♂9👨‍💻1

25 Jan 2026, 20:52 UTC451 views13 reactionsread 8 August 2026

Redis хорош, но... Ничего не имею против хранения данный в ОЗУ при помощи Redis. Быстрый доступ, копия на диске, очереди и прочие плюшки. Но что же вы иногда творите, коллеги? 😱 Если программе нужен набор ключ-значение и этот набор не выходит за пределы вашего однопроцессного однопоточного приложения, используйте словарь. Всем спасибо, я высказался и восстанавливаюсь от постигшего меня шока. ✍️ - беру на вооружен

👨‍💻63💯2👀1🤯1

20 Jan 2026, 13:30 UTC458 views9 reactionsread 8 August 2026

В продолжение идеи про словарь функций Начало тут def handle_negative(): print("Обработка отрицательных значений") ... def handle_zero(): print("Обработка нуля") ... def handle_positive_less_than_ten(): print("Обработка положительных чисел меньше десяти") ... def handle_greater_or_equal_to_ten(): print("Обработка чисел больше или равных десяти") ... condition_func_map = {

5🤯3👨‍💻1

11 Jan 2026, 10:41 UTC367 views28 reactionsread 8 August 2026

Альтернатива if-elif-else / match-case из далёкого прошлого Этот приём я узнал лет пять назад. Ага! Пять. На календарь посмотри, star-пёр. 2026 на дворе. Ты этот приём узнал лет 15-20 назад. 🤓 Итак, есть большой, просто огромный if. if data == "one": # много строк кода ... elif data == "two": # ещё больше строк кода ... elif data = "three" # кода меньше не становится ... else: # тут не

13🎄9🤯6

5 Jan 2026, 14:54 UTC360 views5 reactionsread 8 August 2026
Poll

Как часто вы используете match-case в Python?

  1. Только match-case, не использую if-elif-else3%
  2. В основном if-elif-else, но иногда match-case7%
  3. Часто match-case и редко if-elif-else3%
  4. И match-case, и if-elif-else примерно одинаково7%
  5. Часто if-elif-else и редко match-case10%
  6. В основном if-elif-else, но иногда match-case7%
  7. Только if-elif-else, не использую match-case63%

Shares as published. No per-option vote count is published by Telegram, so none is shown.

🤔2🤯2😱1

13 Sept 2025, 05:30 UTC656 views15 reactionsread 8 August 2026
Photo

Всем, кто отмечает 100000000 день в году, с праздником. С круглым числом. ❤️‍🔥 - обожаю этот день ⚡️ - электрон мне в SSD 👨‍💻 - а у меня проект #python #python3k Python3k

6❤‍🔥5👨‍💻21👍1

29 Aug 2025, 13:42 UTC719 views7 reactionsread 8 August 2026

Забавный факт Вполне ожидаемо, что defaultdict возвращает значение по умолчанию, если ключ отсутствует в словаре. Но только при поиске через квадратные скобки: defaultd = defaultdict(default_func) default_value = defaultd[key] А что будет, если воспользоваться методом get ? В этом случае получаем поведение классического словаря dict. Т.е. при обращении к несуществующему ключу вернётся None. defaultd = defaultdict

4🤯2👍1

7 Aug 2025, 07:10 UTC701 views7 reactions1 Starread 8 August 2026

Меня по телеку Телеграм каналу показывают. https://t.me/zen_of_python/4401 А о чём хотелось бы почитать вам на моём канале?

🔥41👍1👏1

1 May 2025, 08:11 UTC818 views18 reactionsread 8 August 2026

Всех с праздником! Ура! 🎉 И держите праздничный фокус. my_dict = { 1: 'целое', 1.0: 'вещественное', True: 'логическое', } print(my_dict) Что же лежит внутри словаря, что же выведем на печать? 🤔 Познавательная минутка 🤓 Для хранения пар ключ-значение в словаре Python использует технологию хеширования ключа. Так можно быстро найти значение. Скорость O(1), т.е. быстрее некуда. Итак, вычисляем хеш от

🤯7🍾64🕊1

25 Apr 2025, 08:11 UTC819 views18 reactions5 Starsread 8 August 2026
Video

Всем отличной удалёнки. Или офиса с ништяками. 😉😂

6😁5🔥3💯2👍1👨‍💻1

Showing the 12 most recent of 20 posts we hold for @Python3k. View and reaction counts are the latest single reading for each post, not a live figure, and a recent post is still accumulating both. A view count marked was rounded by Telegram before we ever saw it — t.me prints views in full below 1,000 and to three significant figures above, so ≈1,200,000 means somewhere between 1,150,000 and 1,249,999. Unmarked counts are exact. Text is reproduced from the public post preview and truncated for length.

Stars beside a post are paid reactions — Telegram Stars, bought with money and spent on that post. They are a different unit from reactions and are never added to them, here or anywhere else on this page.

Polls

The 2 polls we hold for this entry, as Telegram rendered them when we read the post. A poll’s figures keep moving after that, so each one is dated.

5 Jan 2026, 14:54 UTCAnonymous Poll30 voters

Как часто вы используете match-case в Python?

  1. Только match-case, не использую if-elif-else3%
  2. В основном if-elif-else, но иногда match-case7%
  3. Часто match-case и редко if-elif-else3%
  4. И match-case, и if-elif-else примерно одинаково7%
  5. Часто if-elif-else и редко match-case10%
  6. В основном if-elif-else, но иногда match-case7%
  7. Только if-elif-else, не использую match-case63%

Shares as published. No per-option vote count is published by Telegram, so none is shown.

18 Apr 2025, 09:49 UTCAnonymous Poll58 voters

Читаете ли вы старые посты? Которые были написаны до вашего прихода в канал.

  1. Прочитал(а) все19%
  2. Несколько старых прочитал(а)45%
  3. Читаю только новое26%
  4. Не читаю, просто подписался10%

Shares as published. No per-option vote count is published by Telegram, so none is shown.

Percentages only — there are no per-option vote counts here, because Telegram publishes none.The public post preview gives each option’s share and a single voter total, and nothing else. Multiplying one by the other would produce a per-option tally that looks measured and is not: the shares are rounded to whole numbers before we ever see them. We print what was published and leave the column that does not exist empty.

The shares need not add up to 100.Rounding alone puts many polls at 99 or 101. A poll that allows more than one answer per voter runs well past 100 by design, and several here do. The bars are drawn against a fixed 100% track at each option’s own percentage rather than normalised to the total, so a poll that exceeds it shows that it does instead of being quietly rescaled.

Read from the 20 most recent posts we hold, published 4 November 2024 to 25 February 2026. Telegram labels each poll by kind — an anonymous poll, a quiz, a closed set of final results — and that label is reproduced rather than paraphrased.

Mentions

Names

Channels on the register whose handles appear in this channel's posts.

A mention is a weaker signal than a forward and is counted separately for that reason — naming a channel is not republishing it, and a handle in a post body is easy to place deliberately. The post counts beside each row below are distinct posts in which the handle appeared, from posts we have read on both sides — the “Named by N registered channels” figure above is a different count, of distinct NAMING CHANNELS rather than posts, and is not the sum of the rows under it.

Cite this entry

A live page changes as we take new readings, so a citation should name the measurement it is based on, not just the URL. The line below cites the subscriber count as measured 8 August 2026 — this entry's latest reading, not the date you are reading this.

“Cool and Fun Python” (@Python3k), 513 subscribers as measured 8 August 2026. Telegram Register, tgregister.com/channel/Python3k.

Full measurement history, CC BY 4.0. Every reading this register holds for this entry, not just the latest one, as a dated, downloadable record: CSV · JSON. Free to use with attribution to tgregister.com. Each file carries its own generation timestamp, which is the figure to cite for exactly when the data was retrieved.