deleted by creator

deleted by creator

deleted by creator

deleted by creator

Maybe because people who needed it knew there were better ways to do it, like ipython and Jupyter. I’ve never heard of anyone gushing about the stock REPL.

Reminder that I don’t like the company’s stance on the matter.

What you have posted is your interpretation of the definition, which has little legal or practical value. A product does not need a successor, superior or otherwise, to become obsolete. Nothing you have posted has any relation to the definition of obsolete, and are mostly word play.

That being said, right to repair needs to become a real thing and companies should be supplying repair manuals for items they consider obsolete.

I certainly don’t agree with the company’s position, but did you read definition 1b? I think you may have stopped reading a little early

Use pipenv and don’t think about it anymore.

Very little of this is uniquely a problem in Python. It seems to me that your problem is with software development in general.

deleted by creator

Did you read the article?

This brings back trauma

It’s always Patrick, so both are the same

Buy a 3d printer. You’re getting cancer regardless

Are you ok?

I have 1010 fingers

In my opinion, the settings file isn’t where this information should be presented. I would put these notes in the release log and readme and example settings file. I have also written this information to logging during startup so a user knows what to do, or I write a migration that does the change automatically if that’s possible.

This is only my opinion and you can use the comment method described like “//“: “Deprecated” if desired.

For settings files I always have an example file with sensible values filled in and along with descriptive keys that serves as reasonable documentation. If something is truly unknowable, I’ve probably done something wrong.

Agreed. Except that it’s not easier to write imo

Every time I have reached for TOML I have ended up using JSON. The first reason is that Python standard library can read but not write TOML, which is generally useless for me. The second reason is TOML does not add any benefit over JSON. It’s not that much easier to read and IMO JSON is easier to write by hand because the syntax rules are completely obvious.