Python 3.15's JIT is now back on track

Re:Python 3.15's JIT is now back on track by LtWorf on Wednesday March 18, 2026 @10:19AM (#47426119)

Another thread can access it and do that, how could the compiler possibly know about it?

[ Parent | on HN ]

Re:Python 3.15's JIT is now back on track by bmm6o on Wednesday March 18, 2026 @01:46PM (#47428879)

There are documented ways to ensure that changes are visible across threads (e.g. locks). If these are not used, the compiler is within its rights to not go out of its way to pull changes from another thread.

[ Parent | on HN ]

Re:Python 3.15's JIT is now back on track by LtWorf on Wednesday March 18, 2026 @04:58PM (#47431365)

Except python has a well documented global lock.

[ Parent | on HN ]

Re:Python 3.15's JIT is now back on track by anematode on Wednesday March 18, 2026 @05:56PM (#47431923)

This thread is discussing Java, not Python

[ Parent | on HN ]

Re:Python 3.15's JIT is now back on track by LtWorf on Thursday March 19, 2026 @02:49AM (#47435799)

java has private attributes, python does not

[ Parent | on HN ]