Telegram RegisterThe public register of Telegram
Telegram profile photo for Python: задачки и вопросы

Channel

Python: задачки и вопросы

@quiz_python

On this record: Topic · Growth · Engagement · Reactions · Advertising · Posts · Citations · Telegram's recommendations · Cite this entry

6,846subscribers

-163 since we began measuring on 6 August 2026

Risers and fallers across the register · movement among entries of 3,162–10,000.

Register entry

Telegram ID-1001190099093
TypeChannel
Username@quiz_python
CreatedBetween 1 March 2018 and 31 July 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded6 August 2026
Last confirmed live10 November 2026
Measurements held25
Confirmed unchanged1 time, most recently 10 November 2026
On Telegramt.me/quiz_python

Topic

Education — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-FP8, prompt version 1) read this channel’s own recent posts on 12 September 2026 and assigned it the closest of 31 fixed categories, at 78% confidence. This is a model’s judgement about what the channel is likely to be about, not a fact this register measured the way a subscriber count or a view count is measured — it can be revised on a later pass, and it carries no weight anywhere else on this page. How this classification works, and the other topics.

Growth

6,8467,0096,927.56 August 2026 — 7,009 subscribers6 August 2026 — 7,009 subscribers9 August 2026 — 6,993 subscribers12 August 2026 — 6,990 subscribers15 August 2026 — 6,982 subscribers18 August 2026 — 6,979 subscribers21 August 2026 — 6,969 subscribers24 August 2026 — 6,963 subscribers31 August 2026 — 6,957 subscribers3 September 2026 — 6,947 subscribers8 September 2026 — 6,940 subscribers12 September 2026 — 6,941 subscribers16 September 2026 — 6,937 subscribers24 September 2026 — 6,932 subscribers4 October 2026 — 6,907 subscribers10 October 2026 — 6,906 subscribers14 October 2026 — 6,902 subscribers17 October 2026 — 6,895 subscribers20 October 2026 — 6,886 subscribers26 October 2026 — 6,877 subscribers29 October 2026 — 6,870 subscribers1 November 2026 — 6,866 subscribers4 November 2026 — 6,858 subscribers6 November 2026 — 6,853 subscribers10 November 2026 — 6,846 subscribers6 August 202610 November 2026
25 measurements spanning 97 days, net -163. 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 6,822–7,033 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 25
Measured (UTC)SubscribersChange
10 Nov 2026, 22:006,846-7
6 Nov 2026, 22:356,853-5
4 Nov 2026, 05:196,858-8
1 Nov 2026, 00:066,866-4
29 Oct 2026, 08:366,870-7
26 Oct 2026, 06:356,877-9
20 Oct 2026, 15:186,886-9
17 Oct 2026, 14:596,895-7
14 Oct 2026, 10:396,902-4
10 Oct 2026, 17:156,906-1
4 Oct 2026, 17:406,907-25
24 Sept 2026, 21:226,932-5
16 Sept 2026, 08:016,937-4
12 Sept 2026, 14:206,941+1
8 Sept 2026, 18:376,940-7
3 Sept 2026, 09:376,947-10
31 Aug 2026, 01:156,957-6
24 Aug 2026, 23:346,963-6
21 Aug 2026, 11:346,969-10
18 Aug 2026, 08:236,979first reading

Engagement

66 posts held, back to 27 July 2026 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 23 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
4.07%
avg views ÷ 6,846 subscribers
Avg views / post
278
32 posts measured
Reaction rate
0.326%
reactions ÷ views · ER floor
Posts in window
32
of 66 held

ERR is average views per post over the last 30 days divided by subscribers, the definition TGStat uses, so this figure is comparable with the one you will see elsewhere. It falls structurally as a channel grows: a high ERR on a small channel and a low one on a large channel describe reach mathematics, not quality. We publish the figure and the sample it came from and pass no verdict on it.

ER is defined industry-wide as (forwards + reactions + comments) ÷ views — note the denominator is views, not subscribers. Telegram’s public web preview carries views and reactions but not forward or comment counts, so the reaction rate above is the reactions term only and is therefore a floor: the true ER for this channel is higher by an amount we have not measured and will not estimate. It is computed over the 4 of 32 measured posts that carry a reaction reading, and over those same posts' views.

What these figures were computed from
WindowRolling 30 days · latest post in window 9 November 2026
Posts held66 (27 July 2026 – 9 November 2026)
Views total8,906
Reactions total4
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken10 Nov 2026, 17:14 UTC

Views are a single reading per post, taken at the time above. A post published in the last day or two is still accumulating views, which pulls the 30-day average down slightly. That is a property of the standard definition rather than a fault in it, so we keep the definition rather than “correcting” the number into something nobody can reproduce.

Precision. Telegram publishes view counts on its public widget in short form — 8.12K, 3.7M — so any reading at or above 1,000 reaches us rounded to three significant figures, and only counts below 1,000 are exact. Averages and rates derived from them are shown to the same precision rather than to the unit: a figure like 3,701,250 would assert digits nobody measured.

Reaction counts are published per emoji and rounded the same way, so a total below 1,000 is exact and a larger one is a sum that may carry a rounded component from each emoji above 1,000. Because it is a sum, it does not look rounded — read a large reaction total as three significant figures per contributing emoji rather than as the figure it prints.

Reaction mix

65 reactions across 37 posts, in 1 kind.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
✍65100.0%

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 37 of the 66 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 65 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 66 most recent posts we hold, published 27 July 2026 to 9 November 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.

Advertising

Ad load
4.55%
3 of 66 posts carry an ad marker
Regulatory tokens
3
posts carrying an erid · 3 distinct tokens
Median views · ads
351
over 3 measured posts
Median views · rest
294
over 63 measured posts

An ad marker, not a judgement about a post. A post is counted here because it carries one of two explicit markings: an erid token, which Russian law has required on paid placements since 2022 and which is issued against a specific advertising contract, or a #реклама / #ad hashtag in the body, which is the channel declaring it itself. The first is documentary; the second is a self-declaration and is weaker. No classifier reads the text and decides — nothing on this site guesses that a post is an advertisement.

This is a floor, and it can only ever be a floor. A channel that runs paid placements without marking them produces no marker for us to count, and an unmarked ad is indistinguishable from an ordinary post on the public surface. The ad load above therefore means “the share of posts that declared themselves”, never “the share of posts that were paid for”. A low figure is not evidence of a channel that runs few ads.

Both figures are medians, and no ratio between them is published. Each is a view reading that actually occurred on a post, picked by percentile_disc rather than averaged, so one viral post cannot move it and no interpolated value is invented between two readings. The sample on one side is under five posts, which is too thin to compare. The two figures are shown side by side with the count behind each, and deliberately not divided into a headline like “ads get x% fewer views” — an arithmetic that is easy to print and, at this sample size, means nothing.

Advertising tokens recorded on this entry
eridPostsFirst seenLast seen
2W5zFFzVHzh128 July 202628 July 2026
2W5zFK4PUL9130 July 202630 July 2026
2W5zFKAB2eV129 July 202629 July 2026

A token repeated across several posts is one advertising contract placed more than once, which is what the identifier is for. The strings are reproduced exactly as they appeared in the post or in its click-through URL and are not validated against any registry — we record the marker a channel published, and whether it resolves to a real contract is a question for the register that issued it.

Measured over the 66 most recent posts we hold, published 27 July 2026 to 9 November 2026. Views are the latest single reading held for each post, and any reading at or above 1,000 is rounded by Telegram to three significant figures.

Recent posts

Telegram’s own ‘edited’ marker: 0 of 32 posts held from the last 30 days (0%) carried it when this register last read them. The marker says a post was changed after publishing, not what it said before — this register holds the earlier wording only where an edit fell between two of its own reads (see the edit ledger and how it is measured).

9 Nov 2026, 09:18 UTC180 viewsread 10 November 2026

Почему slug пересчитывается 1. Job("Night Build") вызывает сгенерированный __init__, затем __post_init__. В первый раз slug становится "night-build". Следующая строка вручную заменяет его на "manual". 2. replace(old, name="Quick Fix") создаёт новый Job через __init__. Поле slug помечено init=False и из old не копируется. 3. У нового объекта снова вызывается __post_init__. Именно наш метод вычисляет slug из нового …

8 Nov 2026, 09:08 UTC221 viewsread 10 November 2026

Отмена внутри, TimeoutError снаружи 1. asyncio.timeout(0) назначает отмену на ближайшую итерацию цикла событий. Event создан без установленного флага, и никто не вызовет set(). Поэтому wait() приостанавливает текущую задачу. 2. Тайм-аут отменяет эту задачу. В точке await возникает asyncio.CancelledError. Внутренний except TimeoutError его не перехватывает, строка inside не печатается. 3. При выходе из async with м…

7 Nov 2026, 09:11 UTC221 viewsread 10 November 2026

Где заканчивается компонент пути 1. Здесь явно импортирован posixpath, поэтому обе строки разбираются по правилам POSIX независимо от ОС запуска. 2. commonprefix() сравнивает строки посимвольно. Вторая строка начинается с первой целиком, поэтому результат — /srv/config. 3. commonpath() сравнивает компоненты. После общего /srv идут разные имена: config и config-old. Общий путь — /srv. Правильный вариант: /srv/conf…

6 Nov 2026, 09:05 UTC259 viewsread 10 November 2026

Аргументы до и после apply_defaults() 1. bind("eu") сопоставляет строку "eu" параметру region. Функция fetch при этом не выполняется. Объект BoundArguments описывает вызов. 2. В arguments сначала попадают только явно связанные аргументы. Поэтому первый print выводит {'region': 'eu'}. Значение timeout=5 пока пропущено. 3. apply_defaults() добавляет недостающие значения по умолчанию. Для timeout это 5, для **options…

5 Nov 2026, 09:18 UTC278 viewsread 10 November 2026

Что остаётся доступным после CycleError 1. В словаре TopologicalSorter значения — предшественники узла. Для build нужен test, а для test нужен build. Ни один из них не готов к запуску. 2. У lint нет предшественников. prepare() обнаруживает цикл и выбрасывает CycleError, который код перехватывает. 3. После такой ошибки разрешено вызвать get_ready(). Независимый lint остаётся доступным, поэтому вывод — ('lint',). Ед…

4 Nov 2026, 09:17 UTC279 viewsread 10 November 2026

Два пути к значению по умолчанию 1. Пустой список в parse_args([]) означает, что ни --limit, ни --rate не переданы. Аргументы запуска самого скрипта здесь не читаются. 2. Значение default="08" — строка. argparse пропускает её через type=int и получает число 8. Первый print выводит 8 int, без начального нуля. 3. Значение default=8.5 уже имеет тип float. Для нестрокового default преобразователь не вызывается. Вторая…

Showing the 12 most recent of 66 posts we hold for @quiz_python. 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.

Forward network

Republished by

Channels on the register that have forwarded this channel's posts into their own feed.

Built only from forwarded posts we have actually read, on both sides. Coverage is early and deliberately incomplete: a missing link means we have not read the post that would prove it, never that the relationship does not exist. Counts are distinct forwarded posts observed, so they only ever go up as we read more.

Mentions

Named by 2 registered channels — every channel on the register whose own posts have named this one, by its current username or any other username it currently holds, merged from two separately captured readings of the same fact so a namer caught by only one of them is not missed and a namer both caught is not counted twice. A username this channel has since dropped is not matched — that handle may belong to someone else now, and crediting today’s namer to yesterday’s owner would misattribute it.

Named by

Channels on the register whose posts name this channel's handle.

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.

Appears in Telegram’s recommendations for other channels

The reverse of the list above, and a different kind of signal. This does not require this channel to have ever been asked about directly — each row below is a channel we DID ask Telegram about, whose Telegram-generated list happened to include this one. A channel can appear here with an empty list above it, because being named by someone else’s query is independent of having been queried itself.

Zen of Python
@zen_of_python · 18,630
Telegram ranks this channel #2 of 91 here — alongside 90 others — read 5 October 2026
Python Academy
@python_academy · 43,823
Telegram ranks this channel #29 of 87 here — alongside 86 others — read 28 August 2026
Pythonist.ru - образование по питону
@pythonist_ru · 23,873
Telegram ranks this channel #41 of 82 here — alongside 81 others — read 17 September 2026
Поколение Python 🐍
@pygen_ru · 50,348
Telegram ranks this channel #41 of 93 here — alongside 92 others — read 25 August 2026
Библиотека питониста | Python, Django, Flask
@pyproglib · 36,972
Telegram ranks this channel #47 of 84 here — alongside 83 others — read 1 September 2026
Python и 1000 уязвимостей
@osint_pythons · 36,463
Telegram ranks this channel #48 of 84 here — alongside 83 others — read 1 September 2026
Python Learning
@Python_per_month · 27,870
Telegram ranks this channel #61 of 86 here — alongside 85 others — read 9 September 2026
Python обучающий
@pythonist24 · 55,221
Telegram ranks this channel #62 of 88 here — alongside 87 others — read 23 August 2026
Однажды в трендах
@trendo · 66,417
Telegram ranks this channel #63 of 90 here — alongside 89 others — read 20 August 2026
Senior Python Developer
@seniorpy · 39,134
Telegram ranks this channel #65 of 92 here — alongside 91 others — read 30 August 2026
Python Job | Вакансии | Стажировки
@job_python · 23,452
Telegram ranks this channel #73 of 96 here — alongside 95 others — read 19 September 2026

This channel appears in 11 seed channels' Telegram-generated recommendation lists in total. Each is Telegram’s list for THAT channel, not this one — see how this is measured.

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 10 November 2026 — this entry's latest reading, not the date you are reading this.

“Python: задачки и вопросы” (@quiz_python), 6,846 subscribers as measured 10 November 2026. Telegram Register, tgregister.com/channel/quiz_python.

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.