Wow! Wish the majority of packages i encounter has this problem; too many releases.

That sounds really nice. Actively maintained packages for a change.

Have successfully installed py315 pyenv install 3.15.0

Which packages currently support py315

pyenv please do what you do so can start testing py315

no. No it wouldn't. It would break 99.9999% of python interpreter version checks cuz we are all following the exact same patterns.

... the next day you'd be here saying that was a really bad idea.

Luckily people smarter than us already decided that was not worth pursuing. And we are better off for those folks with foresight instead of 100% clarity in hindsight.

Luckily people smarter than us realized code checking for versions couldn't distinguish from 3.14 and 3.14blahblahblah

That idea sucks please forget you ever supported it and i'll do the same. The point is now mote anyway.

As long as they are based in Sweden and owned by Swedish citizens then you have no standing to even complain.

A derivative browser like Mullvad is merely a patch on top of a base browser. No one is forcing you to use it.

The lead up to py315 is better than sex. Out with the py310 (2026-10-01) in with the py315 (2026-10-09)!

Waiting one more whole day is torture.

I get to be this excited for lazy imports

Wow! What a great read.

The terrorists preying upon our women and throwing society into a state of perpetual persecution failed at even issuing a well deserved ticket for tailgating.

Instead the highwayman and political activist clergy proceeded in terrorizing a rando person for the crime of existing and breathing.

The political activist clergy edict clearly documents this fact.

The highwayman is even shown on camera using a mass surveillance service. Which they know is highly illegal. He is not in jail cuz he is a member of this mafia and in cahoots with the political activist clergy class.

The highwaymen and political activist clergy, for allow it, should be sued. If no legal remedy is on offer, the society itself should reject them in their entirety.

It's a clear as day violation of the 4A and any form of decency. And points to them being terrorists and not public servants as they'd have you believe.

Do you think the defendant, now, feels she has freedom to travel unimpeded? Does she now hide in fear of leaving her house?

Fck the 4A, this is a violation of life liberty and the pursuit of happiness without prior approval and ritualized acts of submission and compliance. And illegal detention that she is punished by the process.

Fck these people! They are clearly terrorists who both got paid for this theater, while society gets dragged thru the mud for their personal gain.

i'm not interested in Twitter. I am interested in software repos like github. Those must be the front runners on implementing ekyc.

Can't tell if made a convincing argument or sneezed without covering my nose.

The entire point of the argument was to convince others to deliberately not engage it. It being ruff.

A clearer comment might be, "yeah i love flake8, black, and isort. They are great or at least sufficient!"

There is no "me" in FOSS. The package is either maintained or it's tech debt or a plague in peoples' tech stack.

Is this a call for maintainers? In which case should direct that at your user base. They have skin in the game.

I'm being kind and assuming there is a user base.

ruff is Rust. I stay away from introducing Rust into Python tech stack. Since if something goes wrong, the burden of maintaining it falls upon user base all of which are not Rust experts. It's a heavy burden.

Would recommend removing it.

What's the ruff pitch? memory safety in a linter is about as important/useful as tits on a bull.

Been seeing most packages atm supporting py310 - py314. Other abandoned packages just have py3+ which is good enough.

The issue is when you go full async native and drop sync codebases. Then no choice but to step up and help maintain other AWOL author/maintainers projects.

Glad to be helpful. Did you try out interrogate and typos?

... and after arriving. Have to load a minimal image. So this causes a major tax and inconvenience upon everyone. Tax after tax after tax.

Those who are a patriot are a curiosity. Their speech can be reduced and measured in whines/hr

At a certain point spyphones are just an inconvenience.

There is no way for xyz to be either included or excluded from a package cuz everyone should be running python -m build and checking the tarball and .whl before even considering a commit or a release.

So although the OP chose hitch that doesn't change the workflow of manually checking the tarball.

I use setuptools, wreck (requirements management), and drain-swamp (choose versioning by either "tag" or "current" rather than specifying exact semantic version). What i use has no bearing on the opinion above.

"modern" means you are a little bitch. I'm very tired of that term. A function with multiple return statements is considered "modern". Whereas i see that as wrong. So now that "modern" word is being thrown around for packaging?! Please stop using that term. It's a cope for not being able to code your own build backend (drain-swamp), frame stack free locals inspection (logging-strict), and requirements management (wreck)!

Use whatever you are familiar with without peer pressuring others.

py310 ... nah ... bah ... chigau ... passu ... sochi ga ii

stubtest (static vs runtime)

rather than

pyrefly coverage check (static only)

So pyrefly is a bean counter. If using mypyc, e.g. black, doesn't have stubs, then understandable this could be a valid use case.

BUT that is an outlier. Without stubs that removes the usefulness of pyright which catches actual bugs.

static vs runtime matters

Similarly to how test coverage measures how much of a library's source code is hit by its tests, type coverage measures what percentage of a library's typables have type annotations.

Errrr no!

type coverage should be how much of the typing has corresponding tests. This is particularly important for stub packages. Which are focused on confirming the advertised typing accurately reflects actual typing.

Hope they didn't cyber squat the package name.

Listen to Yoda, "Try? Either do or do not! No try there is."

The correct answer to percentage of a libraries typables having type annotations is either zero or all. This is advertised by the py.typed file. There is no middle ground.

Wtf is wrong with pyrefly authors?

Stub package with naming starting with type- does not follow PEP561.

The convention is types-*.

So yeah, what is type-coverage?!