Free-threaded CPython is ready to experiment with

Re:Free-threaded CPython is ready to experiment with by ahartmetz on Saturday July 13, 2024 @04:40AM (#40952677)

Is that because the compiler failed with "foo.h not found" or the build system said "libfoo not found"? CMake is most common and it will tell you. Worst case it's difficult to derive the package name from the name in the diagnostic.

It's not great, but usually not a big deal neither IME. Typically a couple of minutes to e.g. find that required libSDL2 addon module or whatever, if there is that kind of problem at all.

[ Parent | on HN ]

Re:Free-threaded CPython is ready to experiment with by stavros on Saturday July 13, 2024 @05:53AM (#40952957)

Yes it is, and it's usually such a big deal for me that I just don't use that software. I don't have time to go through a loop of "what's the file name? What package is it in? Install, repeat". This is by far the worst experience I've had with any language. Python has been a breeze in comparison.

[ Parent | on HN ]

Re:Free-threaded CPython is ready to experiment with by dgfitz on Saturday July 13, 2024 @09:07AM (#40953902)

I’m not going to refute your points. If you’re going to wear rose-tinted glasses about all of the bad parts about python, that’s fine, I also like python.

[ Parent | on HN ]

Re:Free-threaded CPython is ready to experiment with by stavros on Saturday July 13, 2024 @09:08AM (#40953904)

What's rose-tinted about "one of them downloads dependencies automatically, the other one doesn't"?

[ Parent | on HN ]

Re:Free-threaded CPython is ready to experiment with by cozzyd on Saturday July 13, 2024 @04:44PM (#40956740)

I mean this is a documentation problem. It's pretty common for python to import something it doesn't say it depends on too, btw...

[ Parent | on HN ]