Re: confused with so many python package locations for imports

2009-04-26 Thread Ben Finney
Scott David Daniels writes: > Ben Finney wrote: > > Thank you for the correction. Please mentally substitute into my > > argument the files that *are* compiled C extension modules; it > > remains otherwise unchanged. > > But the compiled C extension modules are called ".pyd" files and > they are

Re: confused with so many python package locations for imports

2009-04-26 Thread Scott David Daniels
Ben Finney wrote: Chris Rebert writes: Erm, .pyo-s aren't platform-specific. […] It's not like .pyo-s are compiled C extension modules. Thank you for the correction. Please mentally substitute into my argument the files that *are* compiled C extension modules; it remains otherwise unchanged

Re: confused with so many python package locations for imports

2009-04-25 Thread Ben Finney
Chris Rebert writes: > Erm, .pyo-s aren't platform-specific. […] > It's not like .pyo-s are compiled C extension modules. Thank you for the correction. Please mentally substitute into my argument the files that *are* compiled C extension modules; it remains otherwise unchanged. -- \“

Re: confused with so many python package locations for imports

2009-04-25 Thread Chris Rebert
On Sat, Apr 25, 2009 at 1:31 AM, Ben Finney wrote: > Krishnakant writes: > >> My Basic question is that, what package directory is Standard as far >> as all gnu/linux distros are concerned? > > Python has a habit of generating, and expecting to find, > platform-specific files (‘foo.pyo’ extension

Re: confused with so many python package locations for imports

2009-04-25 Thread Ben Finney
Krishnakant writes: > So now if I say for example choose ubuntu and debian for my testing > purpose, should I put all the packages I make into > /usr/local/lib/python2.6/site-packages? Will this be a safe choice for > at least debian and Ubuntu? No, for Debian and/or Ubuntu, you should avoid mov

Re: confused with so many python package locations for imports

2009-04-25 Thread Krishnakant
On Sat, 2009-04-25 at 18:31 +1000, Ben Finney wrote: > Python has a habit of generating, and expecting to find, > platform-specific files (‘foo.pyo’ extension modules), compiled bytecode > files (‘foo.pyc’), and module source files (‘foo.py’) necessarily in the > same directory for purpose of locat

Re: confused with so many python package locations for imports

2009-04-25 Thread Ben Finney
Krishnakant writes: > My Basic question is that, what package directory is Standard as far > as all gnu/linux distros are concerned? Python has a habit of generating, and expecting to find, platform-specific files (‘foo.pyo’ extension modules), compiled bytecode files (‘foo.pyc’), and module sou

Re: confused with so many python package locations for imports

2009-04-25 Thread Krishnakant
On Sat, 2009-04-25 at 14:16 +0900, David Cournapeau wrote: > Some of those locations are OS specific - pyshare is specific to > debian I think, for example. > My Basic question is that, what package directory is Standard as far as all gnu/linux distros are concerned? In other words I would like to

Re: confused with so many python package locations for imports

2009-04-24 Thread David Cournapeau
On Sat, Apr 25, 2009 at 2:36 AM, Krishnakant wrote: > > hello all, > I was doing my first complete python packaging for my software and I am > totally confused. > I see, /usr/local/lib/python-2.6/site-packages and also dist-packages. > Then I also see a directory called pyshare, then again site-pa

Re: confused with so many python package locations for imports

2009-04-24 Thread Ben Finney
Krishnakant writes: > Now my question is, which the perfect place? Your question is unrelated to the message to which you're replying. To start a new discussion, do not reply to an existing message (causing your message to be incorrectly associated with that existing message). Instead, compose

confused with so many python package locations for imports

2009-04-24 Thread Krishnakant
hello all, I was doing my first complete python packaging for my software and I am totally confused. I see, /usr/local/lib/python-2.6/site-packages and also dist-packages. Then I also see a directory called pyshare, then again site-packages in usr/lib/python (I am not even remembering correct path