500 Python Interpreters
izzys.casa
500 Python Interpreters
1–10 of 35 posts
Re: 500 Python Interpreters
#2> "No matter what happens there is going to be a lock occurring. No two PyThreadStates can execute Python bytecode at the same time. However, they can execute multiple C calls at the same time which is why for long running pure C operations extension and embedding developers are encouraged to release the GIL temporarily."
Very exciting! I wonder what the first set of motivating applications are and what kind of performance gains are they expecting.
Re: 500 Python Interpreters
#3I'm lo0king forward to it, but debugging this stuff is going to be another level of hard.
Re: 500 Python Interpreters
#4You posted this 11 days ago and it's been posted by two other people in the interim. (Why is this version of the post more popular?)
Re: 500 Python Interpreters
#5You posted this 11 days ago and it's been posted by two other people in the interim. (Why is this version of the post more popular?)
Sometimes articles just don't get traction and then they're invited to resubmit (by dang, the moderator). Since the submitter submitted it twice, that was probably what happened here.
As to why it's "more popular", I guess you mean is getting more upvotes, that's part of the trick with submissions. Post it on a slow Friday work day before a holiday and you'll get more clicks than some other days or times.
Re: 500 Python Interpreters
#6You posted this 11 days ago and it's been posted by two other people in the interim. (Why is this version of the post more popular?)
It was entered into the second chance pool[1]. Interim posts were probably not as popular because I accidentally broke my site's CSS briefly that wasn't obvious in the preview deployments, but was present on the actual site. I only noticed about an hour ago
Re: 500 Python Interpreters
#7I was hoping for it to be an HTTP status code.
Re: 500 Python Interpreters
#8You posted this 11 days ago and it's been posted by two other people in the interim. (Why is this version of the post more popular?)
It was entered into the second chance pool[1]. Interim posts were probably not as popular because I accidentally broke my site's CSS briefly that wasn't obvious in the preview deployments, but was present on the actual site. I only noticed about an hour ago [1]: https://news.ycombinator.com/item?id=26998308
CSS may still be broken. At least, I'm getting some really obnoxious color combinations (magenta on salmon, etc.)
Re: 500 Python Interpreters
#9Earlier quoted context omitted.
It was entered into the second chance pool[1]. Interim posts were probably not as popular because I accidentally broke my site's CSS briefly that wasn't obvious in the preview deployments, but was present on the actual site. I only noticed about an hour ago [1]: https://news.ycombinator.com/item?id=26998308
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
Re: 500 Python Interpreters
#10When they say per interpreter GIL in PEP 684, is that per thread? I wasn't aware of multiple interpreters in one process.