Python 2.5 PIL Gone in Lucid?

Why do half my tests suddenly fail, thinks me?  Me thinks, me looks, me finds no PIL!  Egadzooks, thinks me, thinking thinkily, what has become of my Python 2.5 PIL?  Aptitude thinks, and returns no thoughts of a Python 2.5 python-imaging?  Me thinks methinks me thoughts must turn to source.

[Update] For those who encounter this, latest PIL can be installed with a simple easy_install on the PIL*.tar.gz download.  You need to make sure that you've got the dependency dev libraries installed first, but with that it installs cleanly in a virtualenv.  (I didn't test Tk, but the image-manipulation stuff seems to work).


  1. Me

    Me on 04/24/2010 10:23 p.m. #

    Methinks you've been reading John Lennon's "In His Own Write".

  2. Brett Haydon

    Brett Haydon on 04/25/2010 12:52 a.m. #

    I don't get it. Why would you use lucid but not use Python 2.6 with python-imaging

  3. Mike C. Fletcher

    Mike C. Fletcher on 04/25/2010 1:20 a.m. #

    Well, because sysadmins are a conservative lot.

    I have to push to get that new-fangled Python 2.5 and a modern PostgreSQL on their servers. I may develop on my Lucid laptop, but they want to run on Debian stable (or RHEL 4.x, etc) and use only the most "time-tested" tools available.

    Of course, I could just use VMs with Debian stable, but I find that cumbersome unless there's a real need for it. I can more easily keep my code cross-version than maintaining the server images.

    Consultants still have to target Python 2.4 for some projects launching today (particularly for RHEL). 2.5 is reasonably accepted, and I generally require clients to go for at least that. 2.6 on a production server is crazy talk :) ;) .

Comments are closed.


Pingbacks are closed.