I second this: it might be obvious to software developers, but _not_ to software users. IMO, this addition should be added in many other packages' FAQ, not just PIL. :-) Thanks, Aubrey.
DG --- On Sun, 12/14/08, Aubrey Barnard <afbarn...@wisc.edu> wrote: > From: Aubrey Barnard <afbarn...@wisc.edu> > Subject: [Image-SIG] Addition to PIL FAQ > To: image-sig@python.org > Date: Sunday, December 14, 2008, 4:55 PM > Dear PIL developers of the image SIG, > > I have an addition that I would like to make to the PIL FAQ > (located at http://www.pythonware.com/products/pil/faq.htm). > I would like to add the following information to the answer > to "Why does PIL say 'The _imaging C module is not > installed'?" > > I saw this problem because I was using PIL with a different > version of Python than was used to compile PIL. So the tip > to add is that PIL must be compiled and used with the same > Python. > > While this requirement might seem obvious, it can be > obscured on machines with multiple versions of Python when a > user requests a particular Python that is not the first one > found via the path. (E.g. PIL will be built with the default > Python, but the user will try to use it with a different > Python.) > > Thank you for considering adding this to the FAQ. I think > it will save PIL users such as myself many headaches. > > Sincerely, > > Aubrey Barnard > _______________________________________________ > Image-SIG maillist - Image-SIG@python.org > http://mail.python.org/mailman/listinfo/image-sig _______________________________________________ Image-SIG maillist - Image-SIG@python.org http://mail.python.org/mailman/listinfo/image-sig
