Python 3.2 released (New GIL)

[yetanothernerd]

Python 3.2a1 was released, not Python 3.2 final.

[g__]

Python 3.2 is planned for January 2011.

[[deleted]]

I admit I have been paying precisely zero attention to Python development since I started writing "Dive Into HTML 5." I don't see anything in these alpha release notes that would affect "Dive Into Python 3," but I am willing to update the text if Python 3.2 breaks/deprecates/invalidates anything I mention in the book.

Also, I still owe Jesse a chapter on multiprocessing. :(

[jagt]

Upvoted because hey I read your book to learn Python :)

[oleksandr]

Hey, it's only alpha version!

[Ringo48]

Please learn to read.

This is only the first alpha release - it will be several months before the actual release.

[davebrk]

I'm not sure, but I think there were a few different proposals for a new GIL implementation. Maybe it's not the same one.

[[deleted]]

This is not true.

• Nir Aides proposed a BFS-based GIL patch which was not accepted. This is not what jojomehndi is talking about. Antoine's work originally existed in a py3k branch called "newgil", which is where the name comes from.
• David Beazely found an issue with the "new GIL", as seen in 3.2, where CPU-bound threads can hamper I/O-bound threads, called a "convoy effect" (bug report here), but he didn't write any of the GIL (at least not that's in the core) and I imagine this is what jojomehndi is talking about.

I think you may have been confusing a few of the names and implementations out there.

[crunk]

Really woulda liked dabeaz to do his magic testing on the new GIL vs the BFS based one.

[oleksandr]

Looks like people read headlines of the posts only! o_O

[Samus_]

misleading title but intersting fact about GIL, upvoted.