Last day for PyCon early bird registration!

PyCon 2009 has its last day for early bird registration today (Feb 21)!

Want some help porting to Py3K? Come to PyCon!

Ted Leung made a good point that the sprints at PyCon this year are an ideal time to get help with porting your code to Python 3.0. With a good number of core developers showing up this year there will be plenty of experienced people with 3.0 to answer questions in whatever room the core sprint will be in (once I get around to registering the core sprint).

Three days left for PyCon early bird registration!

Just a reminder that PyCon early bird registration ends in three days! There are 439 people publicly registered at the moment which, last time I heard, puts us on track to be over 1,000 attendees again! Looks like the economy is not going to suppress attendance at PyCon which is great!

Actually, this PyCon will probably have the highest number of core developers in attendance than any other previous PyCon thanks to the language summit. That should make the conference interesting to me just from the standpoint of the hallways conversations that will most likely spring up.

Benchmark numbers for DVCSs on Python's repository

Robert Fendt benchmarked Python's repository on various DVCSs. It confirms my numbers that Bazaar, Mercurial, and Git are all fast enough for our needs.

Invited speakers at PyCon announced

When the list of accepted talks for PyCon 2009 was released, it wasn't the whole story in terms of scheduled content. This year the program committee decided to do something different and have invited talks. Now, short of the keynotes which have not been announced, people have a very clear picture of the great content that is set to be shown at PyCon this year.

[Full disclosure: I am on the PyCon program committee as well as an invited speaker, although I didn't know I was invited until I got the invitation =) ]

importlib.import_module() packaged up for PyPI

Importlib is now on the Cheeseshop. I took what was in the trunk for Python 2.7 and tossed it up. At the moment I know it can go as far back as Python 2.5, but I bet it will go back even farther without issue; just need to get my hands on older interpreters to see how compatible it is.

With import_module() one does not need to call __import__ and try to comprehend how to use it. Instead you use import_module() and get a much saner API.