-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Hi,
I have a problem that I'm not able to solve on my own. I'm using python2.2 that comes with Mandrake Linux distribution 8.2.
I have a tree of python sources that I'd like to package in more or less the same tree, which would be installed in site-packages under subdirectories pyortal and pyortal-modules.
If I understand python documentation correctly, if I want those modules to be easily accessible for everyone, I need to have .pth file in site-packages that points to all subdirectories (and right, if I create it manually, it works). The problem I have is that if I run bdist_rpm, I can see a message that is telling me that .pth is being build, but the file is missing in the created rpm.
If I build with bdist only, it creates and includes pyortal.pth (but it only lists pyortal directory in it without any subdirectory). So, what am I doing wrong?
While I'm at it...is there an easy way to include normal text files in module distribution? Again, if I'm not mistaken, the current way to achieve this is to list every one of them in MANIFEST.in.
Thank you for your help. Kind regards,
Marko - -- HP: http://elite.org/~markos PGP:http://elite.org/~markos/markos.key Jabber: markos@aufbix.org
Marko Samastur wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Hi,
I have a problem that I'm not able to solve on my own. I'm using python2.2 that comes with Mandrake Linux distribution 8.2.
I have a tree of python sources that I'd like to package in more or less the same tree, which would be installed in site-packages under subdirectories pyortal and pyortal-modules.
If I understand python documentation correctly, if I want those modules to be easily accessible for everyone, I need to have .pth file in site-packages that points to all subdirectories (and right, if I create it manually, it works). The problem I have is that if I run bdist_rpm, I can see a message that is telling me that .pth is being build, but the file is missing in the created rpm.
Why .pth files ? Why not simply *copy* the code to site-packages ?
If I build with bdist only, it creates and includes pyortal.pth (but it only lists pyortal directory in it without any subdirectory). So, what am I doing wrong?
While I'm at it...is there an easy way to include normal text files in module distribution? Again, if I'm not mistaken, the current way to achieve this is to list every one of them in MANIFEST.in.
I think you only need to put *.txt into MANIFEST.in (provided your text files use that extension).
On Wednesday 10 April 2002 11:15, M.-A. Lemburg wrote:
I can see a message that is telling me that .pth is being build, but the file is missing in the created rpm.
Why .pth files ? Why not simply *copy* the code to site-packages ?
Mainly, but not only, because of estetic reasons. My project already has 26 .py files and this number will only rise.
Dumping them all in one directory (and other authors doing the same), would just make that directory look like a trashcan and could also result in filename conflicts (which can be otherwise avoided if certain modules in subdirectories are never directly imported).
Kind regards,
Marko
Marko Samastur wrote:
On Wednesday 10 April 2002 11:15, M.-A. Lemburg wrote:
I can see a message that is telling me that .pth is being build, but the file is missing in the created rpm.
Why .pth files ? Why not simply *copy* the code to site-packages ?
Mainly, but not only, because of estetic reasons. My project already has 26 .py files and this number will only rise.
Dumping them all in one directory (and other authors doing the same), would just make that directory look like a trashcan and could also result in filename conflicts (which can be otherwise avoided if certain modules in subdirectories are never directly imported).
Why not wrap them up as one or more Python packages ?
participants (2)
-
M.-A. Lemburg -
Marko Samastur