2025-09-09 08:03:00
#Python is Dying and Nobody Wants to Admit It
https://medium.com/codeelevation/python-is-dying-and-nobody-wants-to-admit-it-4260f774117a
#Python is Dying and Nobody Wants to Admit It
https://medium.com/codeelevation/python-is-dying-and-nobody-wants-to-admit-it-4260f774117a
I’m somewhat exhausted to announce attrs 25.4.0!
The main reason for this release (and why it's published today) is that it ships the first pieces of work for Python 3.14 and PEP 749. There will be more work required and there's going to be a lot more churn once everyone starts testing 3.14 earnestly. We hope to receive more feedback before spending more time on this. #Python
Also yesterday at #OpenSSLCon25: Alex Gaynor of #Python #Cryptography saying their own X.509 parser written in Rust is six times faster than
@… and @… let's goooo!!!! It's hybrid, so there is still time to join online
#python
A feature which I'm really looking forward to is brewing in #Python packaging: Specifying default extras.
The aiocoap library I maintain can (and is tested to) work with no other dependencies than Python, but most users will like the additional features such as pretty-printing support, or more security options than just TLS. So far, they have to `pip run --spec "aiocoap[all]" aio…
BREAKING: #CPython 3.13.10 and 3.14.1 changed the multiprocessing message format in patch release. As a result, programs using multiprocessing may break randomly if they are running while #Python is upgraded (i.e. need restarting).
But apparently it's not a big deal, since all the cool kids are running Python in containers, and nobody is using Python for system tools anymore. Everything has been RIIR-ed and Python is only omnipresent in some backwaters like #Gentoo.
https://github.com/python/cpython/issues/142206
Die #Python Software Foundation hat eine #Förderung von 1,5 Millionen US-Dollar durch die US-Regierung abgelehnt, da sie an Auflagen gegen #Diversität und
I learned about PsychoPy which is an open-source package for running experiments in Python (a real and free alternative to Matlab).
Anyone using it?
#python
🧵 Scaling asyncio on Free-Threaded Python
#python
Any #Python newbies out there? (Or experts that need to teach Python)
Would you have a specific online tutorial to recommend for someone who wants to learn Python without any prior programming experience? One that also explains how to install it ?
I was thinking of something like this:
#Python on the Edge: Fast, sandboxed, and powered by #WebAssembly
https://wasmer.io/posts/python-on-the-
The #python library that we #qemu developers use for the test harness. Now with support for 3.14. Useful for deep tinkerers: https://pypi.org/proje…
🛠️ Fully #opensource #Python framework you can self-host or deploy to LiveKit Cloud with one CLI command. 🐙 https://github.com/livekit/agents
📊 Meine Top4-Beiträge der letzten Woche mit den meisten Boosts sind:
1. Die #Python Software Foundation hat 1,5 Mio USD #Förderung von US-Regierung abgelehnt.
Bravo #Python Software Foundation!
https://pyfound.blogspot.com/2025/10/NSF-funding-statement.html
Video tutorials for modern ideas and open source tools. #python
My very first experience with Python was generating programmatic art using the Turtle module.
Don’t let anyone tell you coding is only for pros, it can be an incredibly fun and liberating experience.
#PythonIsForEveryone #Python
The new Python documentary is good. Definitely worth watching if you think you might be interested. It's on YouTube.
#python #programming #history
LWN: Explicit lazy imports for #Python
I'm VERY excited by this PEP.
https://lwn.net/SubscriberLink/1041120/d969b8b8c72251be/
The #Pathfinder2E character data structure is in progress, figured a good ol'-fashioned JSON schema would be the way to go. Still, progress continues.
#python #characterSheet
Por la pega estoy haciendo un curso de #Python orientado a «Ciencia de Datos» y si bien no estš tan bueno como esperaba, el material y lo tips que he conseguido es lo mas interesante. Esto es justamente lo que quiero aprender.
Whats the replacement for crypt in python? I want to crypt a known string just like /etc/shadow/ so I can verify my students set the username/pw correctly as requested in a lab. I was using this code (image) but looks like crypt.crypt isn't there in Python3.13. Looks like my code doesn't work like it did last semester. Oops. #python3
💻 New Tech Unveiled Meet TSUs (Thermodynamic Sampling Units)! The X0 prototype chip proves these primitives work in silicon at room temp. Plus, XTR0 desktop kit for early researchers—available this fall.
📚 #OpenSource Kickstart Dive in with Thermal, the #Python library to simulate TSUs on GPUs. Build thermoAI algorithms now & collaborate!
Years ago I had this Processing app that I used to create time stamped images from a webcam. It no longer works. (It’s been years since I used it.)
I was able to rewrite what I need in Python fairly easily, so that’s pretty awesome.
I used to really love Processing but I guess I love Python now.
#processing
#Python "do not pin your new dependencies to a version that's already obsolete by the time you release your package" challenge.
This one also has difficulty: impossible.
#packaging
I think my code would work perfectly except that os.utime does not actually work...
#python #code #programming
PythonBPF - Writing #eBPF Programs in Pure #Python
https://xeon.me/gnome/pythonbpf/
Released v0.22.0 of the ha-mqtt-discoverable #python module.
New features: Lock devices
Thanks again to Steffan for all his work on the module.
#homeassistant @… @…
I'm fixing #aiocoap's memory leak tests to finally run as async functions: the original tests employed mechanisms from the age of tulip (back when asyncio was developed out-of-tree), and Python 3.14 dropping some obsolete mechanisms.
Good riddance, but also tough work fixing subtle possible leaks that are suddenly easier to discover.
hot take: a big reason for the collective anxiety around free-threading is the result of decades of copium where we assured each other that it's good, actually, that #Python has a bad threading story, because threads are dAnGeRoUs and our feeble minds need protection
So #Zope released new versions of their packages, with pkg-resources style namespace removal.
Totally normal way to do the bumps:
1. At first, keep the existing testing hack (writing `__init__.py`).
2. Notice that the next package fails because it expects test paths relative to `zope` subdirectory. Skip it for now.
3. While doing the next package, realize you could remove that hack and simply run tests within the `zope` subdirectory! Go back and update all the previous packages, including the one that failed before.
4. Back to bumping. Notice that in the very next package you've had an even better solution: instead of `cd`, you just called `python -m unittest -s …`. Go back and update all the previous packages.
5. Back to bumping. The very next package turns out to actually expects test paths relative to the top-level site-packages directory. Well, you can use a hybrid of the `__init__.py` hack with `python -m unittest -s …`.
#Gentoo #Python
📦 #Copyparty - Turn Any Device Into a Feature-Rich File Server #opensource #selfhosted #Python
Remember the package that recently had some trailing junk in the .tar.gz that broke GNU tar, and replied to my bug report with a comprehensive #LLM analysis and a slightly sloppy release checking workflow?
They've made a new release and this time the source distribution is completely broken gzip stream.
Honestly, bumping #Python packages for #Gentoo all these years, I don't recall ever seeing a problem with gzip streams. And then, #autobahn starts using #ClaudeCode heavily, and two bad releases in a row. I can't help but consider the project compromised at this point.
#NoAI #AI
"Do not introduce #NIH #RustLang dependencies in your #Python package when there's no performance, security or any other benefit to it, and it just limits portability and creates more work for packagers" challenge.
Difficulty: impossible.
#packaging
Here are some key takeaways from implementing #PyPI attestations in #Gentoo:
• With OpenPGP, you need to validate the authenticity of a key. With attestations, you need to validate the authenticity of the identity (i.e. know the right GitHub repository). No problem really solved here.
• They verify that the artifact was created by the Continuous Deployment workflow of a given repository. A compromised workflow can produce valid attestations.
• They don't provide sufficient protection against PyPI being compromised. You can't e.g. detect whether new releases weren't hidden.
On the plus side, TOFU is easier here: we don't have to maintain hundreds of key packages, just short URLs on top of ebuilds.
Security-wise, I think PEP 740 itself summarizes it well in the "rationale and motivation" section. To paraphrase, maintainers wanted to create some signatures, and downstreams wanted to verify some signatures, so we gave them some signatures.
#security #Python
🤚 Free Saturday
👉 Saturday spent working on Free Software
Highlights from #Gentoo:
• #Gemato is now compatible with #FreePG and mostly compatible with #SequoiaPGP chameleon.
• Prepared patches to support FreePG and SequoiaPGP chameleon as "gpg" symlink providers.
• #FlexiBLAS is now enabled by default on ~arch.
• Finally finished working on #PkgCheck check for missing #PyPI provenance checks.
• gpy-list-pkg-impls now includes "does this package have tests?" state, can optionally include PythonCompatUpdate results from PkgCheck and output mIRC colors. In other words, our IRC bot will now tell us when dependencies let us port new packages to #Python 3.14, and whether these packages have tests.
I've filed a report about a minor problem with a #Python package, namely that the source distribution contained some trailing junk that breaks GNU #tar. On one hand, I'm happy that upstream took the issue seriously. On the other hand, I'm terrified of how much #AI slop was involved in the response.
I mean, my short bug report yielded a few walls of text of #LLM analysis of what the cause of the problem might be, of suggested solutions… and praise of the author's fix. These are interspersed with short comments from the author, all pasted under their own personal account. And the linked pull request is also huge, with "verification code" that's quite sloppy (bits that don't do anything, conditions that will never be true… but at least it seems to do what it was supposed to do).
Honestly, I don't know what to do. Not that I ever planned using this package, but at this point I will definitely stay away from it. It's in #Gentoo, and I'll have to continue maintaining it for the sake of reverse dependencies, but I feel like it's unfair to expose our users to packages that have clearly proven to accept AI slop without reviewing it properly. Or rather, AI slop that's being reviewed… by AI. How can anyone think this a good idea?!
There were multiple times in my life when I've considered retiring from Gentoo, for variety of reasons. There were also multiple times when I wanted to get away from computers altogether. Unfortunately, we're living in a truly fucked up world, and there is no escape. The best you can do is put an ever increasing effort to keep fixing all that crap that will just keep piling on faster and faster.
#FreeSoftware #OpenSource