Channel
@pyHints
On this record: Growth · Engagement · Reactions · Posts · Citations · Telegram's recommendations · Cite this entry
9,953subscribers
+91 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
| Telegram ID | -1001898229283 |
|---|---|
| Type | Channel |
| Username | @pyHints |
| Created | Between 1 November 2022 and 31 August 2023— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 6 August 2026 |
| Last confirmed live | 22 August 2026 |
| Measurements held | 7 |
| Confirmed unchanged | 1 time, most recently 22 August 2026 |
| On Telegram | t.me/pyHints |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 22 Aug 2026, 11:38 | 9,953 | +22 |
| 18 Aug 2026, 21:46 | 9,931 | +26 |
| 16 Aug 2026, 04:08 | 9,905 | +7 |
| 12 Aug 2026, 16:04 | 9,898 | +29 |
| 10 Aug 2026, 00:02 | 9,869 | +9 |
| 7 Aug 2026, 02:17 | 9,860 | -2 |
| 6 Aug 2026, 22:01 | 9,862 | first reading |
26 posts held, back to 13 June 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 24 pagesof Telegram’s post history, 20 posts per page.
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.
| Window | Rolling 30 days · latest post in window 20 August 2026 |
|---|---|
| Posts held | 26 (13 June 2026 – 20 August 2026) |
| Views total | 40,338 |
| Reactions total | 336 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 21 Aug 2026, 05:17 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.
912 reactions across 25 posts, in 1 kind.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 👍 | 912 | 100.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 25 of the 26 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 912reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 26 most recent posts we hold, published 13 June 2026 to 20 August 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.
داشتم دنبال یک ویدئو میگشتم که ببینم کسی ماژولهای مهم رو برای پایتون توضیح داده ؟ یک بخشی از داکیومنت رو خوندم و فهمیدم ماژول چیزی هست که دنبالشم و توی این سرچ متوجه شدم ۳ سال قبل با این ابزار آشنا شدم؛ یا اون موقع بدردم نمیخورده یا پروژههام همه رو اسکریپت بوده و کار میکرده یا ایراداتی داشته که نتونستم استفاده کنم. خواستم این نکته رو هم اضافه کنم که : هرچیزی به زمانش و به وقت نیاز بهش خوبه؛ چیزی که امروز خیلی راج…
👍14
این دقیقا یکی از اون جاهایی هست که گفتم نیروی جونیور توی تیم لازم هست. مسئله این هست که من اسکریپتهام و راهاندازی کانتینر dev برای ابزارها و کانفیگشون با اسکریپت و ... رو شاید ۱-۲ ماه بعد از یادگیری داکر (اوایل معروف شدن) شروع کردم همین امروز هم اگر تنبلی باعثش نبود عمرا همچین چیزی رو سرچ نمیکردم. حتی اگر احمق بودن بیش از حد LLM ها نبود هم اینکار رو نمیکردم؛فیچرهایی که خواستم تست کنم جدید بود و البته چون نمیدو…
👍20
من همیشه دیتابیس تست و ... رو براش اسکریپت مینویسم (دستی) بعد توی کدهام از اون موارد استفاده میکنم کار تمیزی هست ولی زمانبر الان همینطوری یک سرچ زدم آنلاین ببینم روش دیگری هست ؟ پروژهای که دستم هست خیلی سادهاس و فقط میخواستم چندتا فیچر جدید رو هم تست کنم اینکه یک سری اسکریپت دقیق بنویسم و کانفیگ کنم بنظرم زیاد بود testcontainer رو پیدا کردم که بنظر میاد دقیقا برای همچین وقتایی هست گفتم معرفی کنم برای دوستان د…
👍15
اینم برای دوستان دانشجو یا علاقمندای به Data Structure & Algorithm این سایت با انیمیشن بهتون نحوه کار هر اگوریتم رو نشون میده (برای دانشگاه سنگاپور هست) و برای هر کدوم : ۱- کوئیز داره (نمره نداره یک سری سوال رندم برای درک میزان یادگیری هست) ۲- یک بخش پرینت داره که خلاصهی کامل رو بهتون میده مثل یک cheat sheet که توی چند مورد که من خوندم خیلی خوب و درست نوشته شده. خلاصه این رو روزی ۱ بار بهش سر بزنید.
👍41
داشتم داستان ۲ هفته troubleshoot کردنم برای یک شرکت رو مینوشتم و اینکه ۷ نفر قبل من رفته بودند و راهکاری پیدا نشده بود. حتی بهشون جابجایی استک پایتون رو هم پیشنهاد داده بودند. و حتی اینکه خرید سرور تا ۳ برابر قویتر هم کمکی نکرده بود. که سیستمم خاموش شد (نوسان برق) خلاصهاش رو بگم، تیبل refresh token رو براش بکگراند جاب بنویسید تمیز کنه. که اگر یکی refresh token رو اشتباهی گذاشت روی 1 ساعت و ۵ میلیون یوزر داشتید ت…
👍28
بنظرم ویدئوهای کنفرانس امسال خیلی کم داره دیده میشه PyData Youtube
👍16
یک آپشن روی sqlalchemy برای relationship هست که شخصا خیلی دوسش دارم؛ باعث میشه به کوئری که سمت دیتابیس میفرستم فکر کنم بجای اینکه سادهترین راه رو انتخاب کنم. هرجا هم که نیاز دارم دولوپرها به کوئریهاشون دقت کنند حتما ازش استفاده میکنم. lazy = "raise" الان داشتم خروجی پروفایلینگ یک پروژه رو نگاه میکردم؛ توی RandRng گفتم راجبش. دیدم خیلی کوئریهای دیتابیس زمان بر هست؛ ی سرچ توی مدلهای دیتابیس زدم و همهی relatio…
👍39
این ترکیب به راحتی میتونه خیلی از پروژهها رو از Postgres به Sqlite منتقل کنه؛ Sqlite + Litestream توی خیلی پروژهها برای خودم پیش اومده که یک دیتابیس نیاز داشتم؛ شاید ۵-۱۰ تا جدول ولی اینکه فقط روی یک سرور نباشه هم برام مهم بوده که خب سرویسهای کلاد رو استفاده میکردم. همزمان هم Latency میرفت بالا هم کلی هزینه پرفورمنس واسه سربارهایی کار کردن با Postgres میدادم درحالی که به ۹۰٪ اون ویژگیها نیازی نداشتم. الان د…
👍21
اینو یادداشت کرده بودم که بذارم: تقریبا ۱.۵ سال پیش روی یک پروژهای کار میکردم (فکر کنم گفتم جزو معدود پروژههایی بود که از اول توی پروژه بودم) امشب با مدیرعامل شرکت و صاحب پروژه صحبت میکردم (شاید پروژه دوم) میگفت علاوه بر دولوپرهای بعدی ادمین دیتابیس هر چندوقت یکبار که روی دیتابیس کار میکنه ی دمش گرم هم به ما میگه. من استانداردهای زیادی رو رعایت کردم روی اون پروژه ولی این ۵ خط بنظر میاد خیلی بچههایی که رو…
👍70
Background jobs رو توی دو مرحله پیادهسازی کن مرحله اول رو با خود Fastapi پیاده سازی کن ببرش زیر لود تست بعد ببین چه اتفاقی میوفته ADR-0015 رو نمیدونم چی هست ولی اینکه بدونی تا چه زمانی از خود Fastapi میتونی استفاده کنی خیلی مهمه بعدش برو روی Dramatiq —————— Auth رو با Argon2 هم چک کن (خیلی واجب نیست فقط برای اینکه بهش آشنا باشی) ———————— برای متریک prometheus_client استاندارد اصلی هست ———————— چندتا چیز دیگه که به…
👍14
#Backend_RoadMap #Sample_Project زحمت این فایل رو شایان عزیز کشیده (با استفاده درست از AI) و توی گروه گذاشت من چندتا نکته رو اضافه کردم و با اجازهاش گفتم بعنوان نمونه اینجا منتشر کنم پست بعدی نکاتی هست که من اضافه کردم.
👍18
یادآوری : https://t.me/pyHints/423
👍12
Showing the 12 most recent of 26 posts we hold for @pyHints. 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.
Citation-graph rank — 731,681 of 1,581,209entries in the measured graph. A weighted position computed from the forward and mention edges below — republished posts weigh more than named mentions — and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channel’s name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page — a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
Republishes
Channels on the register whose posts this channel has forwarded.
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.
Named by 1 registered channel — 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.
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.
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.
This channel appears in 18 seed channels' Telegram-generated recommendation lists in total. Each is Telegram’s list for THAT channel, not this one — see how this is measured.
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 22 August 2026 — this entry's latest reading, not the date you are reading this.
“Python Hints” (@pyHints), 9,953 subscribers as measured 22 August 2026. Telegram Register, tgregister.com/channel/pyHints.
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.