Abduaziz π

Python Project Setup - Template Repozitoriya: https://github.com/AbduazizZiyodov/python-setup @AbduazizPy

Sog'lom odamlar hammasi tasavvurga ega, "osh haqida o'ylamang" desam, baribir oshni rasmi hayolingizga ... Qaysiki tasavvur tushunchasi fanda mental image deb yuritiladi. U miyamizning ko'zi. Ammo, Aphantasia bilan og'riganlarda bu kabi "rasmchalar" paydo bo'lmaydi miyada, afsus. Haftalik kalendar/jadval haqida tasavvur qilganda, hayolimga Microsoft Teams(uzur, MS Trash)dagi kalendar emas, maktab davridagi kundalik sahifasi men eng ko'p ko'radigan rasm. Boshqacha o'ylashga harakat qilganman, foydasi yo'q. Har-xil uslublarda kalendar yuritib ko'rdim(TODOlardan tashqari), hech biri intuitiv tuyulmadi - kundalik rasmi hayolda baribir. Ko'rinishidan optimal, ishlatib ko'raychi. Sahifani tashkillashtirish bo'yicha takliflar bo'lsa izohlarda qoldiramiz. #experiment @AbduazizPy

frozendict frozendict CPython'ning 3.15-talqinida yangi built-in ma'lumot turi sifatida qo'shildi. https://peps.python.org/pep-0814 Ichki detallarini hisobga olmasak, foydalanilishi jihatidan(m: metodlar, tashqi amallar) biz bilgan standart dict'dan farqi yo'q. Tuzlishi har doimgidek { key: value } tarzda, yaratilgandan keyin o'zgartirib bo'lmaydi (immutable). Xuddi tuple'dagi kabi immutability xossasi obyektning o'ziga nisbatan aytilyapdi [1]. Uning ichidagi qiymatlari(value) mutable bo'lishi mumkin (m: list). Ammo ular ham immutable bo'lsa, demak biz to'liq immutable dictionary'ga ega bo'lamiz. Demak uni keyin o'zini heshlashimiz ham mumkin(hashability), qaysiki biz bilgan standart dict holatida unday emas. Heshlab "bilishimiz"[2] bizga frozendictni boshqa dictlar uchun ham kalit(key) sifatida foydalanish imkonini ham beradi. PEPda aytilganidek frozendict "mutable default argument" muammosini ham bilvosita hal qiladi [3]. Parallel/concurrent dasturlar yozayotganingizda, bir qiymat - bir qancha protsess/thread/korutinlar o'rtasida "share" qilinishiga zarur bo'ladi. Bunda ushbu qiymat mutable bo'lsa bizda har xil muammolar tug'diradi (m: siz xohlamagan tarzda uni boshqa joydan o'zgartirilsa). Bunda frozendict standart dictga nisbatan "share" qilish uchun eng yaxshi nomzod. Bu g'oya avval ham taklif etilgan, ammo hozir bizda avvalgidan ko'ra ko'proq "use case"lar mavjud: asyncio, free-threading hamda subinterpreters. Shu tufayli ushbu urinish muvaffaqiyatli kechdi. To'liq tafsilotlar bilan PEPda tanishib chiqishingiz mumkin. [1] Aniqroq aytsak - "shallow immutability". [2] Learnt from @sanjartech [3] Mutable default argument'lar haqida - https://stackoverflow.com/questions/1132941/least-astonishment-and-the-mutable-default-argument @AbduazizPy

Abduaziz π pinned «Tsikllar == Rekursiv Funksiya ? Maqolaga havola: https://abduaziz.ziyodov.uz/articles/tsikllar-rekursiv-funksiya Funksiyalarning chaqirilishidan boshlab ular ustidagi optimizatsiya(lar) haqida yozdim. C & CPython misolida muhokama qildim. O'qib-o'rganib…»

Tsikllar == Rekursiv Funksiya ? Maqolaga havola: https://abduaziz.ziyodov.uz/articles/tsikllar-rekursiv-funksiya Funksiyalarning chaqirilishidan boshlab ular ustidagi optimizatsiya(lar) haqida yozdim. C & CPython misolida muhokama qildim. O'qib-o'rganib, quyida "diskussiya" qilishingiz ham mumkin. Foydali va qiziq deb bilsangiz, hamda sizga yoqsa - maqola(i.e. ushbu postni)ni boshqalarga ham ulashing. Desktop kompyuterda oching, agar sahifaning ba'zi qismlari yuklanmay og'irlik qilsa CTRL+SHIFT+R (yoki SHIFT`siz) bilan qayta yuklang. @AbduazizPy

996 written on September 04, 2025 (by Armin Ronacher) “Amazing salary, hackerhouse in SF, crazy equity. 996. Our mission is OSS.” - Gregor Zunic “The current vibe is no drinking, no drugs, 9-9-6, […].” - Daksh Gupta “The truth is, China’s really doing ‘007’ now—midnight to midnight, seven days a week […] if you want to build a $10 billion company, you have to work seven days a week.” - Harry Stebbings I love work. I love working late nights, hacking on things. This week I didn’t go to sleep before midnight once. And yet… I also love my wife and kids. I love long walks, contemplating life over good coffee, and deep, meaningful conversations. None of this would be possible if my life was defined by 12 hour days, six days a week. More importantly, a successful company is not a sprint, it’s a marathon. And this is when this is your own company! When you devote 72 hours a week to someone else’s startup, you need to really think about that arrangement a few times. I find it highly irresponsible for a founder to promote that model. As a founder, you are not an employee, and your risks and leverage are fundamentally different. I will always advocate for putting the time in because it is what brought me happiness. Intensity, and giving a shit about what I’m doing, will always matter to me. But you don’t measure that by the energy you put in, or the hours you’re sitting in the office, but the output you produce. Burning out on twelve-hour days, six days a week, has no prize at the end. It’s unsustainable, it shouldn’t be the standard and it sure as hell should not be seen as a positive sign of a company. I’ve pulled many all-nighters, and I’ve enjoyed them. I still do. But they’re enjoyable in the right context, for the right reasons, and when that is a completely personal choice, not the basis of company culture. And that all-nighter? It comes with a fucked up and unproductive morning the day after. When someone promotes a 996 work culture, we should push back. * edit: for more context https://en.wikipedia.org/wiki/996_working_hour_system @AbduazizPy

https://www.youtube.com/watch?v=GfH4QL4VqJ0 @AbduazizPy

Assalomu alaykum, barchaga! Yaqin vaqtlar ichida yangi meetup tashkillashtirmoqchimiz. Shu munosabat bilan quyidagi uch narsa bo'yicha sizlarni fikr va mulohazalaringni bilmoqchi edik: - Meetupda qanday mavzularda suhbat bo'lishini istaysiz? - Meetupda kimlar…

Project Verona Ownership model for python, deep immutability etc. Ko'proq: https://microsoft.github.io/verona/pyrona.html @AbduazizPy

Django: Composite Primary Keys Vanihoyat 🌝 Havola: https://docs.djangoproject.com/en/5.2/topics/composite-primary-key @AbduazizPy

Python 3.14 (π) Beta ! See what's new: * https://docs.python.org/3.14/whatsnew/3.14.html @AbduazizPy

PEP-0765: finally ichidagi return Quyidagi holat tanishmi? >>> def bool_return() -> bool: ... try: ... return True ... finally: ... return False ... >>> bool_return() False # 🙂‍↔️ Python bo'yicha texnik intervyularda so'raladi, "bu False qaytaradi" degan javob kutiladi. Ammo, True desangiz "finally qanday ishlashini bilmas ekansiz" deyiladi. Dokumentatsiya bo'yicha qaralganda, exception handlingda finally har qanday holatda eng oxirgi bo'lib bajariladigan blok sanaladi. Shu sababli, undagi return yuqori ustunlikka ega (oxirgi bo'lgani uchun): The return value of a function is determined by the last return statement executed. Since the finally clause always executes, a return statement executed in the finally clause will always be the last one executed. [1] Bu holatni qabul qilish men uchun qiyin bo'lgan. Funksiyani chaqiramiz, chaqirilgan funksiya(routine) return orqali o'z vazifasini yakunlaydi, va "return adres" tomon sakraydi(qaytadi) ya'ni avval chaqirilgan joyiga [2]. Fundamental tushuncha, shunday emasmi !? Nega 1-returnning e'tiborsiz qoldirilayotgani g'alati va yoqimsiz. Dokumentatsiyada yozilgani, yoki kimdir aytgani uchun buni shundayligicha qabul qilishimiz kerakmi ... ? finally bloki "cleanup"(tozalash) ishlarida foydalaniladi deb ta'kidlangan, va sog'lom intelekt uni shu uchun ishlatadi. Yuqoridagiga o'xshash kodlar sababli tushunarsiz xatoliklar keltirib chiqaradi. Keyinroq bildimki, bu pythondagi nozik mavzulardan biri ekan ) Eng oson yechim, dasturchiga buni yozgani qo'ymaslik & o'rgatish. Linterlar tomonidan bunga qarshi choralar ko'rilgan[3][4][5], interpretator tomonidan esa yo'q. Avvalgi urinishlar rad etilgan [6]. Yaqin o'tmishda bu mavzu qayta ko'tarildi (PEP-0765), va ushbu "xatolik" hal qilindi (deyarli). Men shunchaki returnga oid holatni ozgina yoritdim, aslida break/continue bilan bog'liq drama ham bor va ular bilan PEP orqali tanishib chiqishingiz mumkin. Yangi interpretator (3.14dan boshlab), ushbu holat uchun SyntaxWarning generatsiya qila boshlaydi (ogohlantirish, ya'ni kodni to'xtamaydi, sizni xabardor qiladi). Keyingi relizlarda SyntaxError chaqirilishi ta'kidlanmoqda. Ko'proq • PEP: https://peps.python.org/pep-0765 • Izlanish: https://github.com/iritkatriel/finally • Discussion: https://discuss.python.org/t/pep-765-disallow-return-break-continue-that-exit-a-finally-block @AbduazizPy

⛵️ Dive Docker image'larni qatlamlari bo'yicha tahlil qilish uchun foydali instrumentga o'xshayapdi, ishlatib ko'rib feedback beramiz izohlarda. Xotira bo'yicha samaradorlikni ham hisoblab berarkan, menimcha u "beta"da hali. 🔗 Havola: https://github.com/wagoodman/dive @AbduazizPy

Rasmiy integratsiyalar qatorida chiqdi bugun. edit: yozish esdan chiqibdi, sentry uchun telegram integratsiya. Telegram orqali alertlar. Avval yo'q edi. @AbduazizPy

📹 GitHub Issues VS StackOverflow Yorib qo'yibdi oxirini lekin. Reference: https://www.youtube.com/watch?v=5WCMI5wuS7U @AbduazizPy

Rust: systems programming Kecha bir postni "share" qilishgan edi, bugun o'qib chiqdim. Post "why rust" degan savolga javob berish uchun motivatsiya bilan boshlanadi. Xotira boshqaruvi masalasi Python/C++/Rust misollari bilan yoritilgan. "Garbage Collection"(GC)ni zaif tomoni ham qisqa aytib o'tilgan ekan, vaziyatdan foydalanib sizlarga agar ko'rmagan bo'lsangiz ushbu videoni ko'rishni ham aytardim. Rustni bilmayman, lekin ownership(postda egalik deyilgan) & borrowing mavzulari odamlarni ezishidan xabarim bor. Postda shu kabi va mavzular alohida yoritilgan, diqqat bilan o'qib tushunsa bo'ladi. Rust ekspert emasman, lekin yetarlicha yangilik oldim. * Rustda yozadiganlar "linked list"larni nega yoqtirmasligini ham tushunasiz. 📖 Postga havola: https://hamirturush.uz/2024-12-29-rust-tizim-dasturlash 📢 Telegram kanal: @hamirturush @AbduazizPy

~ Haqiqat Ertaga hamma "boshqacha" odam. Afsuski, 1 kunda boshqa odamga o'zgarmaysiz (1 yilda ham). 2 ta "phonk" qo'shiq qo'yilgan reels/shorts ko'rib ham. Maqsad/reja qilish, yo'l qo'yilgan xatolarni to'g'irlash & sarhisob uchun 1 yil kutish ham shart emas. Kichikroq intervallardan foydalaning (2 hafta yoki 1 oy), xatolarni aniqlash osonroq. 1 yillik sarhisobda xatolaringizni keltirib berishingiz qiyin/noaniq (kontekst: uy/moshin olish haqida emas, shaxsiy rivojlanish haqida). Xatolar ko'zdan qochiriladi, natijada yana o'sha samalyotni o'q yegan joylarini mustahkamlash uchun yopishtirilgan temir panel kabi ahvol. Maqsad/rejalaringizni ham hech kimga aytmang iloji bo'lsa: 1. Qizig'i yo'q. 2. Bajarish ehtimolingiz kamayadi, miyangiz qildim deb o'ylaydi shu reja/ishni (more: "Positive Fantasy Trap"). Quotes won't work unless you do. @AbduazizPy

Uyga kelgandan keyin kampotlarni ichayotgan man: #hazil @AbduazizPy

Iloji bo'lsa ishlatmang bunaqa narsalarni. @AbduazizPy

@AbduazizPy