Is 463 some joke I'm not getting?
[deleted]
500 Python Interpreters
21–30 of 35 posts
Re: 500 Python Interpreters
#22Does this mean that even the Python 3.13 version is around the corner we have to expect some issues when running threads on a program?
Maybe I’m slow today, but are the author complaining (rightfully so) about the buggy no-gil implementation?
Should we wait until the feature is more stable before implementing new libraries? I was thinking on making use of it in new libraries I plan to develop.
What are the most blatant use case to test this feature?
PD: So many questions, I know, sorry everybody!
Re: 500 Python Interpreters
#23Does this mean that even the Python 3.13 version is around the corner we have to expect some issues when running threads on a program? Maybe I’m slow today, but are the author complaining (rightfully so) about the buggy no-gil implementation? Should we wait until the feature is more stable before implementing new libraries? I was thinking on making use of it in new libraries I plan to develop. What are the most blata…
The article says that embedding (calling Python from C/C++) is currently buggy. It is not clear whether the Python interpreter was compiled with --disable-gil.
I did not check the claim, since, as the article rightly points out, there are general issues in the Python space and other languages like Lua are far better for embedding.
Re: 500 Python Interpreters
#24Earlier quoted context omitted.
CSS may still be broken. At least, I'm getting some really obnoxious color combinations (magenta on salmon, etc.)
It should be a brighter orange closer to what you see on HN's top bar. I've been waffling on the magenta. It works "fine" in low usage. This is the first post where I used it a great deal. I'm gonna be spending some time working with the colors over the weekend, as you're the 5th person to say something to me about it. It could be worse, however. My last design would flashbang you, even if you used darkreader
If you wanna flashback more go for wide gamut colors: https://webkit.org/blog/10042/wide-gamut-color-in-css-with-d...
Re: 500 Python Interpreters
#25Does this mean that even the Python 3.13 version is around the corner we have to expect some issues when running threads on a program? Maybe I’m slow today, but are the author complaining (rightfully so) about the buggy no-gil implementation? Should we wait until the feature is more stable before implementing new libraries? I was thinking on making use of it in new libraries I plan to develop. What are the most blata…
The article says that embedding (calling Python from C/C++) is currently buggy. It is not clear whether the Python interpreter was compiled with --disable-gil. I did not check the claim, since, as the article rightly points out, there are general issues in the Python space and other languages like Lua are far better for embedding.
Thanks, I’m not an embedded developer and was losing the train of thought of the author.
Re: 500 Python Interpreters
#26Earlier quoted context omitted.
The article says that embedding (calling Python from C/C++) is currently buggy. It is not clear whether the Python interpreter was compiled with --disable-gil. I did not check the claim, since, as the article rightly points out, there are general issues in the Python space and other languages like Lua are far better for embedding.
Thanks, I’m not an embedded developer and was losing the train of thought of the author.
[deleted]
Re: 500 Python Interpreters
#27> // 500 interpreter states > static constexpr auto MAXIMUM_STATES = 463; There is a joke here that I’m missing. Does anyone understand what it is?
In the TV show "The Orville" a character has their matter replicator create "500 cigarettes", but it only created 463 after someone counted them all. This is a meme that's been making the rounds for a few weeks in some circles now.
Ah, so that's the origin of that meme
TIL, thanks
Re: 500 Python Interpreters
#28Earlier quoted context omitted.
The article says that embedding (calling Python from C/C++) is currently buggy. It is not clear whether the Python interpreter was compiled with --disable-gil. I did not check the claim, since, as the article rightly points out, there are general issues in the Python space and other languages like Lua are far better for embedding.
Thanks, I’m not an embedded developer and was losing the train of thought of the author.
These threading issues may also be present when not using embedding. Embedding the interpreter frequently shows general threading bugs much quicker.
In other words, when "torturing" the interpreter with embedding a threading bug might show up after 30 min. The same threading bug might show up once every 6 months in a web server (which is a nasty security risk, since it is hard to detect and to reproduce).
Re: 500 Python Interpreters
#29So this means modules like concurrent.futures can create a thread pool object (as opposed to processpool) and run in parallel? Or is the functionality as of 3.13 still limited to low level python embedding applications?
It is expected that many of the more complex Python libraries will break, as they assume no race condition on things that could have now a race condition when GIL is removed.
It will also mean that we can use threads instead of processes and a lot of pain related tot his should disappear in long term.
Re: 500 Python Interpreters
#30Unfortunately, pocketpy moved to global reference to vm recently while changing implementation from C++ to C. Weird decision.