Channel
@python_fastapi_uz
On this record: Growth · Engagement · Reactions · Posts · Citations · Handles named that no longer answer · Cite this entry
515subscribers
+0 since we began measuring on 8 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1002251646383 |
|---|---|
| Type | Channel |
| Username | @python_fastapi_uz |
| Created | Between 1 October 2024 and 31 March 2025— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 8 August 2026 |
| Last confirmed live | 8 August 2026 |
| Measurements held | 2 |
| Confirmed unchanged | 1 time, most recently 8 August 2026 |
| On Telegram | t.me/python_fastapi_uz |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 8 Aug 2026, 21:23 | 515 | no change |
| 8 Aug 2026, 15:31 | 515 | first reading |
20 posts held, back to 22 November 2025 — the 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 23 April 2026. An engagement rate over an empty window would be a number about nothing.
157 reactions across 17 posts, in 10 distinct kinds. The most used accounts for 33.1% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 👍 | 52 | 33.1% | |
| 🔥 | 45 | 28.7% | |
| ❤ | 39 | 24.8% | |
| 👏 | 11 | 7.01% | |
| ❤🔥 | 3 | 1.91% | |
| ⚡ | 2 | 1.27% | |
| 😁 | 2 | 1.27% | |
| 👀 | 1 | 0.637% | |
| 👌 | 1 | 0.637% | |
| 🤝 | 1 | 0.637% |
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 17 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 157reactions 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 22 November 2025 to 23 April 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.
📡 Ngrok nima? Oddiy tushuntirish! Agar siz dasturchi bo‘lsangiz yoki lokal server bilan ishlasangiz, ngrok sizga juda foydali bo‘lishi mumkin 👇 🔹 Ngrok — bu sizning kompyuteringizda (localhostda) ishlayotgan serverni internet orqali hammaga ochib beradigan xizmat. 💡 Ya’ni: Sizda lokal ishlayotgan sayt yoki API bor (masalan: http://localhost:3000) Ngrok uni quyidagicha public linkka aylantiradi: 👉 https://abc123.ng…
👍5❤4🔥4👌1👏1🤝1
🌍 FastAPI va ko‘p tilli dastur: Zarurati va imkoniyatlari Siz FastAPI bilan backend qurayotganingizda ko‘p tilli dastur (i18n) haqida o‘ylash juda muhim. Nega? 1️⃣ Nima uchun ko‘p tilli qilish kerak? 🌐 Global auditoriya: Foydalanuvchilar bir nechta tilni biladi. Sizning API faqat bir til bilan javob qaytarsa, foydalanuvchi tajribasi buziladi. 🔒 Xabarlar va xatoliklar: Har bir error yoki success xabari foydalanuvch…
👏2🔥2😁2👍1
🐍 Pythonda funksiya ichidan funksiya qaytarish mumkinmi? 🤯 Quyidagi kodga qarang: def create(m, n): if m == 'Max': return lambda v: v < n elif m == 'Min': return lambda v: v > n checker = create('Max', 31) print(checker(15)) # ? print(checker(32)) # ? 🤔 Nima chiqadi? Bir o‘ylab ko‘ring... 👇 ✅ Javob: True False 🧠 Nima bo‘lyapti o‘zi? create() funksiyasi oddiy qiymat emas, boshqa funks…
👍4🔥3👏2❤1
🐍 Scope nima? (oddiy tushuntirish bilan) Siz yozgan o‘zgaruvchi kodning hamma joyida ishlaydimi? 🤔 Yo‘q. Python har bir o‘zgaruvchiga qayerda yaratilganiga qarab ruxsat beradi. Bu tushuncha — scope deyiladi. 🧭 Python o'zgaruvchini qanday qidiradi? Python o‘zgaruvchini 4 bosqichda qidiradi: L → E → G → B • Local — hozirgi funksiya ichida • Enclosing — tashqi (nested) funksiya ichida • Global — fayl darajasida …
❤2👏2👍1
🐍 Pythonda Name Mangling nima? Pythonda double underscore (__) bilan boshlanadigan atribut va metodlar tashqaridan bevosita ko‘rinmas bo‘lishi uchun avtomatik ravishda o‘zgartiriladi. Bu mexanizm name mangling deb ataladi. Python ichida atribut nomi quyidagicha o‘zgartiriladi: __attr → _ClassName__attr Shu sababli class tashqarisidan __attr ga to‘g‘ridan-to‘g‘ri murojaat qilib bo‘lmaydi. 📌 Misol class MyClass: …
❤3👍2👏1🔥1
🐍 RxPy — Pythonda Reactive Programming Agar siz: — asinxron jarayonlar — event va real-time data — murakkab oqimlarni soddalashtirish bilan ishlayotgan bo‘lsangiz, RxPy siz uchun juda foydali kutubxona. 🔹 RxPy nima? RxPy (ReactiveX for Python) — bu Observable (ma’lumot oqimi) va Observer (kuzatuvchi) konsepsiyasiga asoslangan reaktiv dasturlash kutubxonasi. Oddiy qilib aytganda: “Ma’lumot keladi → oqimdan o‘tadi…
❤6👍4🔥4
📌 Base64 nima va u nima uchun kerak? Base64 — bu binary (ikkilik) ma’lumotlarni matn (text) ko‘rinishida ifodalash usuli. Ya’ni rasm, video, fayl kabi ma’lumotlarni xavfsiz uzatish uchun ishlatiladi. ❓ Nega Base64 kerak? Ba’zi tizimlar faqat text bilan ishlaydi (masalan: JSON, XML, email). Shu sababli binary ma’lumotlarni to‘g‘ridan-to‘g‘ri uzatib bo‘lmaydi. 👉 Base64 bu muammoni hal qiladi. 🔤 Base64 qanday ishla…
👍4❤2🔥2
📌 Pythonda with context manager bilan bir nechta fayl ochish mumkinmi? 👉 Ha, mumkin va juda qulay! Pythonda with operatori fayllarni avtomatik yopish imkonini beradi. Eng yaxshi tomoni — bir vaqtning o‘zida bir nechta faylni ochish mumkin 🔥 ✅ 1️⃣ Bitta with ichida bir nechta fayl with open("file1.txt") as f1, open("file2.txt") as f2: print(f1.read()) print(f2.read()) 📌 with bloki tugashi bilan barcha fayll…
👍4❤🔥3🔥2⚡1
💡 Python if shartlari va tekshirish ketma-ketligi Pythonda if dagi shartlar operatorlarga qarab tekshiriladi va short-circuit (qisqa tutashuv) baholash qo‘llanadi. 1️⃣ and operatori if shart1 and shart2: ... • Python chapdan o‘nga tekshiradi. • Agar birinchi shart False bo‘lsa, ikkinchi shartni tekshirmaydi. • Foydasi: keraksiz tekshiruvdan qochadi va xatolardan saqlaydi. Misol: if os.path.exists("data.txt…
🔥5👍4❤3
🔍 Profiling nima? Profiling — bu dastur bajarilishi vaqtida: • qaysi funksiya • necha marta chaqirilgani • qancha vaqt ishlagani haqida aniq statistika beradigan tahlil usuli. Pythonda buning uchun eng asosiy modul — cProfile. 🧠 cProfile nima? cProfile — Pythonning standart (built-in) profiling moduli bo‘lib, u: • butun dastur bajarilishini tahlil qiladi • sekin ishlayotgan funksiyalarni topadi • optimallas…
👍5❤3🔥2
✅ Qachon biz SQL ishlatishga majburmiz? 1️⃣ Murakkab querylar ORMdan chiqib ketganda Ba’zan ORM bilan yozish imkonsiz yoki juda noqulay bo‘lgan holatlar bo‘ladi: • Window functionlar (ROW_NUMBER, RANK, LAG, LEAD) • Murakkab subquerylar • Analytics / reporting querylar • Recursive querylar (CTE — WITH RECURSIVE) ORM bunday joylarda ortiqcha kod yozishga majbur qiladi yoki umuman qo‘llab-quvvatlamaydi. 2️⃣ Perfo…
🔥5👍4❤3
Dasturchi SQL queryni bilishi kerakmi? Bugungi kunda ko‘pchilik ORMdan foydalanadi. Lekin bu SQL bilish shart emas, degani emas. 1️⃣ Ha, SQL ni bilishi — shart. Negaki, ORM faqat qulay vosita. Lekin backend logikasi oxir-oqibat baribir SQL queryga aylanadi. Shu sababli: • Query nima bo‘layotganini tushunish • Performance muammolarini topish • Noto‘g‘ri join, filtr yoki index sababli sekinlashishni aniqlash • O…
👍4❤1🔥1
Showing the 12 most recent of 20 posts we hold for @python_fastapi_uz. 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 — 642,447 of 1,169,250entries 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.
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.
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.
@python_fastapi_uz named 2 handles that resolve to nothing today. That is a fact about the reference, not necessarily a fact about the handle’s history — see the two groups below.
Most of these may never have existed as a live channel at all.A handle a channel names can be a typo, an aspirational name nobody registered, or a channel that was already gone before this one ever mentioned it. Unless a row below is marked evidenced, all we know is that it references a handle that is not a live channel today — not that anything “died”. How this is measured.
References a handle that is not a live channel — we have no record it ever was one.
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.
“Isoqjanov Ilyos | Python” (@python_fastapi_uz), 515 subscribers as measured 8 August 2026. Telegram Register, tgregister.com/channel/python_fastapi_uz.
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.