Tootfinder

Sen. Thom Tillis says he won’t seek re-election
after opposing Trump megabill
“It’s not a hard choice, and I will not be seeking re-election” -- Sen. Thom Tillis announced.
His announcement comes after he voted against advancing Trump’s megabill.
Trump has repeatedly criticized Tillis over his opposition to the sweeping tax package — and has threatened to explore primary challengers to the two-term Senator

Sen. Thom Tillis says he won't seek re-election after opposing Trump megabill
Sen. Thom Tillis' announcement is likely to spur a competitive and costly election in the key battleground.

{lubridate} makes working with dates in R just that little bit easier: #rstats #dates

Make Dealing with Dates a Little Easier
Functions to work with date-times and time-spans: fast and user friendly parsing of date-time data, extraction and updating of components of a date-time (years, months, days, hours, minutes, and seconds), algebraic manipulation on date-time and time-span objects. The lubridate package has a consistent and memorable syntax that makes working with dates easy and fun.

So #Gentoo #Python eclasses are pretty modern, in the sense that they tend to follow the best practices and standards, and eventually deal with deprecations. Nevertheless, they have a long history and carry quite some historical burden, particularly regarding to naming.
The key point is that the eclasses were conceived as a replacement for the old eclasses: "distutils" and "python". Hence, much like we revision ebuilds, I've named the matching eclasses "distutils-r1" and "python-r1". For consistency, I've also used the "-r1" suffix for the remaining eclasses introduced at the time: "python-any-r1", "python-single-r1" and "python-utils-r1" — even though there were never "r0"s.
It didn't take long to realize my first mistake. I've made the multi-impl eclass effectively the "main" eclass, probably largely inspired by the previous Gentoo recommendations. However, in the end I've found out that for the most use cases (i.e. where "distutils-r1" is not involved), there is no real need for multi-impl, and it makes things much harder. So if I were naming them today, I would have named it "python-multi", to indicate the specific use case — and either avoid designating a default at all, or made "python-single" the default.
What aged even worse is the "distutils-r1" eclass. Admittedly, back when it was conceived, distutils was still largely a thing — and there were people (like me) who avoided unnecessary dependency on setuptools. Of course, nowadays it has been entirely devoured by setuptools, and with #PEP517 even "setuptools" wouldn't be a good name anymore. Nowadays, people are getting confused why they are supposed to use "distutils-r1" for, say, Hatchling.
Admittedly, this is something I could have done differently — PEP517 support was a major migration, and involved an explicit switch. Instead of adding DISTUTILS_USE_PEP517 (what a self-contradictory name) variable, I could have forked the eclass. Why didn't I do that? Because there used to be a lot of code shared between the two paths. Of course, over time they diverged more, and eventually I've dropped the legacy support — but the opportunity to rename was lost.
In fact, as a semi-related fact, I've recognized another design problem with the eclass earlier — I should have gone for two eclasses rather than one: a "python-phase" eclass with generic sub-phase support, and a "distutils" (or later "python-pep517") implementing default sub-phases for the common backends. And again, this is precisely how I could have solved the code reuse problem when I introduced PEP517 support.
But then, I didn't anticipate how the eclasses would end up looking like in the end — and I can't really predict what new challenges the Python ecosystem is going to bring us. And I think it's too late to rename or split stuff — too much busywork on everyone.

3 Dallas Cowboys depth pieces who could start in 2025 https://insidethestar.com/3-dallas-cowboys-depth-pieces-who-could-start-in-2025

«AI systems are an attack on workers, climate goals, our information environment, and civil liberties. Rather than enhancing our human qualities, these systems degrade our social relations, and undermine our capacity for empathy and care.»
Nice writing by @…!
https://thedabbler.patatas.ca/pages/ai-is-dehumanization-technology.html

„Physik ist linksextrem“¹ – @…
Das gehört auf T-Shirts.
__
¹https://mastodon.social/@spinni81/114770614666399189

Reverse Physics Rap Battle: String Theory vs Loop Quantum Gravity - 😆
Take the top expert in each of two competing theories, and assign each to defend the other's theory. I can't recall the last time I laughed so hard. Best of all, it's all true and they both know it, but yes, one has had 'promising' results for more decades than the other. 🤣
https://www.youtube.com/watch?v=jEr038WOKFI

Probing missing physics from inspiralling compact binaries via time-frequency tracks
Debtroy Das, Soumen Roy, Anand S. Sengupta, Cosimo Bambi
https://arxiv.org/abs/2507.21566 ht…

Probing missing physics from inspiralling compact binaries via time-frequency tracks
The orbital evolution of binary black hole (BBH) systems is determined by the component masses and spins of the black holes and the governing gravity theory. Gravitational wave (GW) signals from the evolution of BBH orbits offer an unparalleled opportunity for examining the predictions of General Relativity (GR) and for searching for missing physics in the current waveform models. We present a method of stacking up the time-frequency pixel energies through the orbital frequency evolution with t…

Its good to have many tests in your R package, but it can be a pain to debug some failing tests when it happens. {lazytest} for the rescue: only rerun the failing tests, until they pass: #RStats

«AI systems are an attack on workers, climate goals, our information environment, and civil liberties. Rather than enhancing our human qualities, these systems degrade our social relations, and undermine our capacity for empathy and care.»
Nice writing by @…!
https://thedabbler.patatas.ca/pages/ai-is-dehumanization-technology.html