I wrote down a few of my thoughts a few weeks ago at https://notes.pault.ag/why-write/ -- I find myself scanning text to see if it's LLM before I actually engage with the content.

It is getting harder to do by the day, and has slowly moved from a mental exercise (look for specific markers) into a "gut feel" based on how the pieces fit together.

Most of this just has to be done. I take your point, but I couldn't find much. And I'm a debian developer - who knows what most non-Debian people would find. The best APIs are in `libapt`, which is C++, and cgo won't work with that all that well.

So, yes, you're right. This is yet another project. That's uncool, but there's not a ton of other ways out, short of me making a clean C shared library and get everyone to switch to that :)

Sorry, I didn't document this since i'm rushing stuff out as soon as I get it together -- I was looking at the Trove classifiers, and setting candidate to true iff it says it's Python 3 compatable but no Python 3 package :)

Also, our releases aren't timed, they're based on bug count, so the timing of the releases wasn't even the main point (and doesn't really matter) :)

I also typoed Python 3 as Python 2 in one of the lines, so, uh, just switch those two numbers. I'm pretty sure it works like that.

Either way, getting Buster off Python 2 means the transition will be more bug free, since we'll have a bit of slack time.

Yes, it's hilarious that version of Mailmain needs to be ported to Python 3.

It works both ways, and bi-directional interop is intended! Just `import hy` then you can import any `.hy` on `sys.path` :D

(yes, this means you can make Hy code pip installable, just like Hy itself!)

If you want a clear failure mode - if this installs requests globally, think about the chaos if you're on Debian stable, with 0.12.1, before the API break - after a pip install, you may end up with all the software on your system broken.

When this happens, please don't file bugs with Debian. Thanks.