Re: Right place for third party modules (here: fixedpoint)

2005-01-25 Thread Sibylle Koczian
Fredrik Lundh schrieb: ah, forget what I said. you need to put the fixedpoint.py *file* under site-packages, not the entire directory. as that "python -v -v" would have told you: Thank you (and Steve Holden), that did it. more out ... # trying C:\python24\lib\site-packages\fixedpoint.pyd # tryi

Re: Right place for third party modules (here: fixedpoint)

2005-01-24 Thread Fredrik Lundh
>> I suppose fixedpoint is no package as described in the tutorial and so >> "site-packages" might not >> be the right place for it. > > site-packages sure works on my windows xp / python 2.4 configuration. ah, forget what I said. you need to put the fixedpoint.py *file* under site-packages, n

Re: Right place for third party modules (here: fixedpoint)

2005-01-24 Thread Fredrik Lundh
Sibylle Koczian wrote: > for the first time since getting Python I can't get a third party module to > work. > > I got fixedpoint.0.1.2.tar.gz from SourceForge for use with KinterbasDB. > After unpacking I had a > directory called "fixedpoint" which I put under my site-packages directory. > Th

Re: Right place for third party modules (here: fixedpoint)

2005-01-24 Thread Steve Holden
Sibylle Koczian wrote: Hello, for the first time since getting Python I can't get a third party module to work. I got fixedpoint.0.1.2.tar.gz from SourceForge for use with KinterbasDB. After unpacking I had a directory called "fixedpoint" which I put under my site-packages directory. There are