On Wed, May 6, 2009 at 17:51, <josef.pktd@gmail.com> wrote:
> On Wed, May 6, 2009 at 5:07 PM, Christopher Barker
> <Chris.Barker@noaa.gov> wrote:
>>josef.pktd@gmail.com wrote:
>>> When I installed PIL, it added the file PIL.pth to the sitepackages
>>> directory, which adds the pil directory to the python path, and so
>>> ``import Image`` works in the standard install (I'm on Windows).
>>>>>> Can you check if you have a PIL.pth? the content is just the word PIL
>>> unless it works differently with your operating system.
>>>> FWIW, I think "import Image" is deprecated, in favor of "from PIL import
>> Image", which removes the need for the pth file. The PIL packge has a
>> LOT of stuff in it, you really don't want all of it on your sys.path.
>>>>>> "Namespaces are one honking great idea -- let's do more of those!"
>>>> (which isn't an exact fit to the topic at hand, but it's close)
>>>> +1
> When I looked this up, I also found a numpy.pth in sitepackages, but I
> don't know which installer put it there, or if I put it there myself.
> Is numpy.pth necessary for anything?
What's inside it?
--
Robert Kern
"I have come to believe that the whole world is an enigma, a harmless
enigma that is made terrible by our own mad attempt to interpret it as
though it had an underlying truth."
-- Umberto Eco