Знакомьтесь, Ричард Джонс (цикл заметок о выдающихся питонистах)
PyPI — централизованный каталог Python-пакетов. Сегодня в нем более 865 тысяч проектов общим весом 36 терабайт . PyPI создал Ричард Джонс . В октябре 2002-го, в электричке, по дороге на работу в Мельбурн. Будет интересно
https://habr.com/ru/articles/1007150/
#python #pythonic #питонист #Ричард_Джонс #история #история_it #история_ит
Знакомьтесь, Эндрю Кучлинг (цикл заметок о выдающихся питонистах)
Замысел в том, чтобы написать цикл о 10 программистах, чьи имена не особо примелькались, но чьи заслуги невозможно переоценить. Начну я этот цикл с Эндрю Кучлинга (A.M. Kuchling) . Я всегда знал его как автора официального туториала по регуляркам в питоне, пожалуй, лучшего по теме. Но масштаб этого человека куда больше.
@JessTheUnstill
I'm working on a programming language, going by the name of #Rocket.
It's supposed to be #Pythonic, but compilable.
Concretely, that means you can modify types, modules, etc. at compile time (e.g. inject another method into a class, replace a method with a wrapped one, create a class dynamically, etc.), but not at runtime.
Still in the early stages, though 
I am "#Python is the batteries-included language, unlike Perl or TCL!" years old, and that has aged like a prawn cocktail. The standard library is chok full of awkward "un-#Pythonic" legacy code that only exists because changing it would break backward-compatibility.
But Python 3.0 *gleefully* broke backward-compatibility! They broke `print "Hello, world."` which is the most-written Python code in history!
So for my money, Python 4.0 should be a release that gets rid of boat anchors like HTTPlib, and pushes that stuff into a `from deadbatteries import ...` compatibility library for the folks who absolutely need it.
You could do statistical analysis of `requirements.txt` files out on the Internet and see what replaces-the-horrible-stdlib-version packages are imported the most. You can then mainline the winning replacements, or figure out what APIs or features everyone is reaching for when they import some new dependency and reimplement that. It doesn't matter if you NIH it, re-do the API on existing library code, or promote a third-party project to Python core library status.
Python's dependency resolution tooling is not just a mess: it's a dozen independently-maintained messes that compound the problem. I want to go back to being able to actually rely on the standard library. I do my best now, but the level of jank is only getting worse as the years drag on, and that prawn cocktail is absolutely pongin'.
#TheMetalDogArticleList
#BraveWords
Exclusive: PYTHONIC Premieres “Liturgy” Single
https://bravewords.com/black-death/exclusive-pythonic-premieres-liturgy-single/
#PYTHONIC #Exclusive #Premieres #newrelease #single #EP #announcement #guitarist #BraveWords #metal #music
For the Python programmers under you who wanted to make your app print, you probably have used pyCUPS to talk with the printing system. Perhaps you have also seen that it is not well maintained, not keeping pace with new APIs. Problem was its design, being a maintenance nightmare.
But for libcups3 it gets much better, thanks to the most Pythonic GSoC contributor we ever had, and CFFI:
https://soumyadghosh.github.io/website/interns/gsoc-2025/gsoc-pycups-is-intelligent/
Thanks @soumyadghosh
#OpenPrinting #Python #Pythonic #CFFI #CUPS #GSoC #GSoC2025
Is that really so? PyCups3 is intelligent? Well, short answer is YES. It is intelligent. Damn, sweetheart, you made an AI for PyCups? Not everything that’s intelligent is an AI. An imaginary conversation, between me and my girlfriend. Now, what’s the twist here is, PyCups3 is actually very very intelligent. So, from my last blog post, I detailed how, PyCups2 got lost due to the lack of upgrades and implmentation of new APIs.
Habr
Saupreiss #Präparat500 🗽
OOTS
Space Hobo
El Pregoner del Metall
🤘 The Metal Dog 🤘
Zeyang
Till Kamppeter
N-gated Hacker News