Tootfinder

what in the actual fuck is going on with sdcc

Eigentlich wollte ich nur mal eben ein Tool ausprobieren, mit dem man Messergebnisse von fio grafisch aufbereiten kann. Jetzt stochere ich halt in Python3, pip3, pipx und Python Environments rum. Gnah! #shavingayak

Any suggestions OTHER than upgrading to AlmaLinux 9 to fix these kind of issues with ansible? Ansible server is Alma 10, but I have a few v8 boxes and mostly v9. "FAILED! => {"changed": false, "msg": "Could not import the dnf python module using /usr/bin/python3.9 (3.9.20 (main, Oct 23 2024, 09:34:14) [GCC 8.5.0 20210514 (Red Hat 8.5.0-22)]). Please install `python3-dnf` package or ensure you have specified the correct ansible_python_interpreter. " ?? …

Comparative Analysis of Two Astrometric Measuring Methods on Five Known Binaries
Syfrett Malachi, Major John, Gamage Gihan
https://arxiv.org/abs/2508.11777 https://

Comparative Analysis of Two Astrometric Measuring Methods on Five Known Binaries
Data on five Washington Double Star catalog binaries were collected from the Dimension Point Observatory (Mayhill, New Mexico) and Las Cumbres Observatory (Cerro Tololo, Chile) on February 19, 2025, and March 5, 2025, respectively. Student researchers participating in the Four Corners Research Seminar measured the position angle (theta/deg) and separation (rho/arcsec) of each target using AstroImageJ and an author-created script utilizing the Astropy module in Python3. Each target was imaged us…

One of the goals I've set for further development of #Python eclasses in #Gentoo was to avoid needless complexity. Unfortunately, the subject matter sometimes requires them. However, many of the functions added lately were already manually done in ebuilds for years.
We've started disabling plugin autoloading years ago. First we just did that for individual packages that caused issues. Then, for these where tests ended up being really slow. Finally, pretty much anywhere `python_test()` was declared. Doing it all manually was particularly cumbersome — all I needed for `EPYTEST_PLUGINS` is a good idea how to generalize it.
Similarly, `EPYTEST_XDIST` was added after we have been adding manually `epytest -p xdist -n "$(makeopts_jobs)" --dist=worksteal` — and while at it, I've added `EPYTEST_JOBS` to override the job count.
Perhaps `EPYTEST_TIMEOUT` wasn't that common. However, it was meant to help CI systems that could otherwise get stuck on hanging test.
Similarly, "standard library" version (like `3.9`) matching to `python_gen_cond_dep` was added after a long period of explicitly stating `python3_9 pypy3`. As an extra benefit, this also resolved the problem that at the time `pypy3` could mean different Python versions.