2026-03-10 20:14:18
Always grateful for the new levels of stability and reliability that #RustLang rewrites of #Python stuff bring.
> a = Tibs.from_i(-1, 128)
^^^^^^^^^^^^^^^^^^^^
E pyo3_runtime.PanicException: attempt to negate with overflow
https://github.com/scott-griffiths/tibs/issues/1
So, remember how all the cool kids dumped #Sphinx and went for the shiny #MkDocs thing? And then used the shiny Material for MkDocs theme?
Well, apparently MkDocs 1.x is dead, and MkDocs 2.0 is coming with no support for plugins, incompatible theming system, closed contribution model and unclear licensing.
So which hype train are the cool kids jumping to these days?
#Python
Oh, in other news, Wheel Variants (formerly PEP 817) is being split into smaller PEPs that will be easier to comprehend. The draft of the first split part, PEP 825, titled "Wheel Variants: Package Format" has been merged. We'd appreciate your feedback!
#Python #packaging
#Steady #Klimacrew
#BahnMonitor-Projekt: 7. Zufall ist nicht gleich Zufall. 🤭
Nach der Verspätungsmeldung kommt ein Wissenshäppchen. Der
Only $1.5mil?
#Python #Anthropic
Thonny, Python IDE for beginners
#IDEsofMarch #python
#Steady #Klimacrew
#BahnMonitor-Projekt: 5. Automatisierte Skripte brauchen Kontrolle – besonders bei API-Aufrufen.
Jetzt bekommt das
In #Python, you could write sensible and transparent code, like this:
if (curNode):
curNode = curNode.next
But if you prefer something that is functionally identical, but harder to read, try this:
curNode and (curNode := curNode.next)
Follow me for more great tips on how to make life hell for the next person working with your code (which could be you).
Video tutorials for modern ideas and open source tools. #python
1. Do random changes to cython-test-exception-raiser, and commit them as "initial code".
2. Move the extension module from the package directory into top-level "raiser.*.so", for no apparent reason.
3. Switch to CalVer, so that #Twisted newer upgrades to the new releases (it pins to <2).
4. I file a bug, because I'd like to finally remove the old version from #Gentoo.
#Python
Finally put together type stubs for an old (last release 2017!) python library I've been depending on for years. And now wondering whether it would have been easier to just contribute types to the library directly. I thought it abandoned but then the maintainer responded up on an unrelated ticket.
(Though there's no CI infra actually working anymore. Makes testing contributions painful. Wonder whether building that first would be worthwhile & welcome...)
#python #packaging
I made a utility to bulk-upload calendar entries to a #CalDAV server from a JSON file:
https://pypi.org/project/caldav-event-pusher/
📋 #SkillSeekers - #Python tool automatically transforms documentation, #GitHub repos & PDFs into production-ready AI skills
I hear that #Python folk are going to enjoy their Monday.
#setuptools removed pkg_resources.
Thanks to Eli Schwartz for the advance warning. We're going to mask it in #Gentoo.
MapToPoster is a beautiful utility to create minimalist posters of the (water)ways of a city.
If you have uv installed, it takes a moment to get going
#python
#ZenOfAICoding: 16 theses on the future of #softwaredevelopment in the #AI era — a homage to the Zen of
Aaand we're seeing the first '#setuptools < 82' runtime dependencies in random packages because they are trying hard to workaround breakage due to pkg_resources removal.
#Python
Fun case of circular logic in #Python #standards:
https://discuss.python.org/t/spaces-not-considered-a-valid-verbatim-character-for-glob-patterns/106463
1. Use "globs" in the specification.
2. Decide that "glob" may be ambiguous, so add severe restrictions on what's supported.
3. Because of the severe restrictions, people may have reinvented the wheel instead of using system `glob` module.
4. Since people may have used their custom implementations, just relaxing the spec is a problem.
Did you know that #PEP425 ("Compatibility Tags for Built Distributions") said:
> Why isn’t there a . in the Python version number?
>
> CPython has lasted 20 years without a 3-digit major release. This should continue for some time. Other implementations may use _ as a delimiter, since both - and . delimit the surrounding filename.
This didn't age well.
#Python
> The next great […] library for #Python
Checks.
> Last commit: 4 years ago. Already broken.
#Python is just doing great. We're not having impossible constraints, as some projects need old #setuptools for pkg_resources, and other projects are starting to require newer setuptools for some fancy new features. And ofc after promising to release pkg_resources standalone over a month ago, setuptools upstream didn't deliver.
#Gentoo
It's not like I'm entirely surprised by this #OpenAI. That's the kind of software that we should build as a community.
#Astral #Python #Capitalism #floss
Ah yes, brew upgraded some ssl-related .so file and broke the python binaries linked against it. Again. So many venvs now lay in ruins.
There has got to be a better way.
(Why do pyenv-built pythons seem to habitually get built using the brew-provided libraries? There's no way for brew to know about that dependency.)
#brew #python #macdev #complaining #askfedi
🧠 #Headroom - The Context Optimization Layer for #LLM Applications #opensource #Python
…
#PythonPoetry is yet another project that disrespectfully treats human bug reporters with #slop:
#NoAI #NoLLM
Sometimes I wonder why do I even bother. I mean, people are perfectly happy to let statistical models designed as bullshit generators do their coding. Why do I even bother running their test suites and inspecting the failures as a human, if these tests may well be complete bullshit?
#FreeSoftware #OpenSource #Gentoo #Python #AI #LLM #NoAI #NoLLM #VibeCoding
Binary partitioning with k-d trees is silly amazing. And with OSM data in radians and pretending the planet is a perfect sphere, scikit-learn's BallTree works wonderfully for quickly finding things nearby some reference point.
Like how far away the nearest bicycle_parking is for every building in a city.
#IMadeAThing #python #osm #overpassql
I'm looking at Repology, and I think most of the distributions and other downstreams have rightfully boycotted #Python #chardet #copywashing. Of course, there's the possibility that some of them are simply out-of-date, though.
So far chardet-7 is distributed by #Chromebrew, #CondaForge (not on Repology), #Homebrew, #KaOS, #OpenIndiana, #openmamba, #Ravenports, #Spack and #T2 SDE. Shame on you!
https://repology.org/project/chardet/versions
https://repology.org/project/python:chardet/versions
There's a new piece explaining "The Slow Collapse of #MkDocs": "How personality clashes, an absent founder, and a controversial redesign fractured one of Python's most popular projects."
#httpx?
Well, turns out no, not at all. It looks like encode has already crumbled and became immensely toxic.
httpx is not allowing bug reports anymore, apparently because of "absurdly skewed gender representation", whatever that means.
#OpenSource.
#FreeSoftware #Python
Proper #security nightmare time.
#LMDB is a database that's designed to operate on trusted input. Upstream has historically rejected all bug reports regarding problems with malformed input.
Py-LMDB project provides #Python bindings to LMDB that are normally built against bundled LMDB. Someone recently started mass-filing "untrusted input" vulnerabilities against py-lmdb, and py-lmdb started #slop - coding fixes to their bundled LMDB. Of course, nobody even bothered reporting most of these bugs upstream, and the one that I've seen reported was rejected as "don't do that".
Py-LMDB supports building against system LMDB, and #Gentoo was doing that so far. However, now we are facing a problem: system LMDB operates under the assumption that it is working on trusted input, while py-lmdb (and its bundled LMDB) operates under the assumption that it may be working with untrusted input. The guarantees no longer align.
If we continue to use system LMDB (and skip all the added slop tests that literally cause Python to crash), then Gentoo's py-lmdb package will now have different input expectations than upstream py-lmdb. And of course we can't just remove that crap because someone added exactly one package (TorchVision, i.e. part of the plagiarism machine suite) depending on it.
https://bugs.gentoo.org/971352
#DigitalIndependence #diday for #SocialScience #researchers:
#Rstats #Jamovi #Python <-- #SPSS #Stata
#LibreOffice #LaTeX #Typst editors #Gnumeric <-- #MicrosoftOffice
#CollaboraOnline <-- #GoogleDocs #GoogleWorkspace #Microsoft365
#Zotero <-- #Endnote #Mendeley #Citavi
#ODK #KoboToolbox #LimeSurvey <-- #Qualtrics #SurveyMonkey etc.
#requal #Taguette <-- #MaxQDA #AtlasTI #NVivo
#PoliticalScience #Economics #Statistics #Econometrics #QualitativeResearch #Evaluation #QuantitativeResearch
> Concretely, we expect to add ML-KEM and ML-DSA APIs that are only available with #LibreSSL/#BoringSSL/AWS-LC, and not with #OpenSSL.
(from #Cryptography and #Qt simultaneously, right? (Qt rejected LibreSSL support.)
#Python