Today's #WTF: how threadpoolctl (a #Python package) asserts that the tests are run on a specific CPU. Sigh.
Of course I've noticed because my CPU is not on the list! I wonder if we should start filing bugs about missing CPUs until upstream realizes it's a bad idea.
"I bought the energy, I paid for it, so I can use it to do whatever I want" is such extreme capitalist thinking.
Where does this energy come from? Of course from the fact that someone arbitrarily claimed it in the past — either because they had influence, money, power or simply were the first to claim it. They claimed coal/oil deposits, they claimed the land to build power plants on. They "produced" (or rather converted) energy and now they're selling it.
Where does your money come from? Most likely you're getting it because you're turning some cogs in the grand machine of capitalism. Once you skip all the middlemen, this eventually boils down to the same thing — someone claimed some resource in the past, and used it to make money.
Humanity just loves to claim everything. Natural resources are theirs to take. All land is theirs to take. Air is theirs, water is theirs, nature is theirs.
Who cares if they're destroying everything? They worked hard and they paid for the right to do so!
"I bought the energy, I paid for it, so I can use it to do whatever I want" is such extreme capitalist thinking.
Where does this energy come from? Of course from the fact that someone arbitrarily claimed it in the past — either because they had influence, money, power or simply were the first to claim it. They claimed coal/oil deposits, they claimed the land to build power plants on. They "produced" (or rather converted) energy and now they're selling it.
In other #Python news, the new #scikit-build-core #pep517 backend turns out to break building extensions via #setuptools in yet another way, this time noticed via #pdm-backend.
Oh, and there's also this bug where it breaks fail2ban too. Perhaps it's the same issue.
Remember when I said a week ago that #LLVM 17.x is nearing the branch point and it's looking good so far? Well, #Clang was broken 5 commits later, they knew it and disregarded is as "happens on just one platform". Well, surprise, it's not "just one platform", and the code is definitely broken somewhere!
Nothing better to ruin your (already bad) mood in the morning than some obstinate #Python developer that insists that others should fix and maintain a backport package forever because they can't have literally a single `if` condition in their precious package.
@mgorny TBH the discussion doesn't seem bad to me. They don't say "fuck off", just ask a few questions. I've seen discussions way worse, especially in PyCQA and PyPA projects where dramas are a daily routine.
FOSS maintainers live in a different world. Our "current" #python version is 3.8. The 3.10 version reaches EoL in Ocy 2026, and that's when we'll be able to unconditionally use ExceptionGroup. So, yeah, we're careful about using anything that isn't in 3.8 🙃
Somewhat active, name-collision with `progressbar` (it's supposed to be backwards compatible but it's not fully compatible with its *current* version), and — guess what — exactly one revdep.
Your proper #NIH reinvent-all-the-wheels library used by exactly one package. They also include progress reporting function. The best part: they actually admit they know about tqdm but tqdm uses threads, so they rewrote that.
Sigh.
So let's discuss #Python progress bar libraries in #Gentoo.
Somewhat active, name-collision with `progressbar` (it's supposed to be backwards compatible but it's not fully compatible with its *current* version), and — guess what — exactly one revdep.
A certain person commented news of another senior being scammed: "How stupid you have to be to fall to *this*." I thought "probably the same stupid as you".
Yes, elderly people fall victim to scams. So do middle-aged people and young people. The only real difference is that they lived in different times, and they fall victim to *different* scams.
People think they're smart because they don't fall for "elderly" scams but they give their PII freely to all kinds of surveillance capitalism corporations when baited with a few cents (or not even baited properly, just "some companies give you discount, so maybe this one will give one too"). Or fall victim to "great" offers.
A certain person commented news of another senior being scammed: "How stupid you have to be to fall to *this*." I thought "probably the same stupid as you".
Yes, elderly people fall victim to scams. So do middle-aged people and young people. The only real difference is that they lived in different times, and they fall victim to *different* scams.
Continuing the topic of content warnings about lewd stuff in movies, I really think there should be one for "washing dishes under running tap water".
That said, #dishwasher commercials that claim that by buying a new dishwasher people are going to "save the planet" trigger me. I mean, sure, if you wash dishes under running tap water, with the faucet fully open, then I suppose dishwasher will save water.
However, a much better solution is to pour the water into a closed sink or a bowl first, and wash there.
Dishwashers are not ecological at all. Dishwashers usually mean that:
1. You usually have to pre-rinse the dishes first (→ extra water use).
2. You usually have to run the full cycle with electric heat drying to avoid streaks.
3. They sometimes fail to wash the dishes properly, especially if you didn't pre-rinse them first. You may end up with the plates being dirtier than they were before the washing.
4. They scale to different number of dishes worse than hand washing.
5. Once you get one, you're going to be forced to run it regularly to avoid the leftover waste water going bad.
Continuing the topic of content warnings about lewd stuff in movies, I really think there should be one for "washing dishes under running tap water".
That said, #dishwasher commercials that claim that by buying a new dishwasher people are going to "save the planet" trigger me. I mean, sure, if you wash dishes under running tap water, with the faucet fully open, then I suppose dishwasher will save water.
@mgorny pre-rinse? My parents had a dishwasher in like 2008+ and it didn't need that and stuff being badly cleaned was pretty rare.
But well closed sink here so far, annoying part is more that kitchens are terribly badly designed, the bottom of the sink should be leveled with the counter.
For two programs to be meaningfully called "compatible" with each other, it takes more than for them to be able to run simultaneously on the same computer.
Stage I: "Thank you for purchasing our software. For this license, we guarantee you'll get free updates for life!"
Stage II: "We've noticed that you're running an outdated version of our software. Please purchase an upgrade in order to ensure that it continues working seamlessly."
Stage III: "We've moved our software to the #cloud now. For a small monthly fee, you will be able to use an up-to-date version of our software on any device! Furthermore, your files will be secure in the cloud and available from any place in the world!"
Stage IV: "We're sorry but due to increasing cloud hosting costs we have to increase our monthly fees. But don't worry, you can resign anytime and lose all your data!"
Stage V: "With regret we have to announce that the market has forced us to discontinue our services. However, don't worry — you can move your data to our new cloud service for free!"
In the meantime, #OpenSource software: "Sure, have it for free. No, no need to pay me. I may starve to death but don't worry, it's #FLOSS, so somebody else will take it over."
Stage I: "Thank you for purchasing our software. For this license, we guarantee you'll get free updates for life!"
Stage II: "We've noticed that you're running an outdated version of our software. Please purchase an upgrade in order to ensure that it continues working seamlessly."
@mgorny you forgot "we discontinued this feature and you can't install old versions but don't worry we also sell this other thing with those features in" 🥲
Back when I joined #Gentoo I was one of the "young'uns". I was full of energy, ideas and motivation, and I was the one to complain about "grampas" wanting to keep things as they were.
Now, almost 13 years later I feel that the roles have shifted. I became much more conservative, and well, more critical of changes. Today's "young'uns" are trying to burn the world, and I'm trying to save it.
That said, I'm trying my best not to be the bad guy and find compromises. While I don't think it's right for us "old folks" to prevent youngsters from taking over, I think that Gentoo has a lot of valuable "old school" vibes that make it stand out in today's IT world. It would be a shame to lose them.
I think how we handled #RustLang is an example of a reasonable solution here. We accept it but we also try to maintain "best effort" support for older hardware that Rust can't work on.
Back when I joined #Gentoo I was one of the "young'uns". I was full of energy, ideas and motivation, and I was the one to complain about "grampas" wanting to keep things as they were.
Now, almost 13 years later I feel that the roles have shifted. I became much more conservative, and well, more critical of changes. Today's "young'uns" are trying to burn the world, and I'm trying to save it.
@mgorny the way Rust integration was added is fantastic. Best way of handling it among Linux distros. And that's coming from someone who writes and deploys tons of Rust code.
Gregory's Server
@mgorny Huh! What's interesting, they use `pytest.skipif` in the test just above, so they know how to properly skip tests but somehow decided not to.