Mailman 3 April 2002 - Distutils-SIG

Re: [Distutils] Non-typical scenario
by Johannes L. Gijsbers April 9, 2002

April 9, 2002

> I'm trying to write a setup.py, but I'm having a few > problems because of the following a-typical requirements: > > 1) I want all my extension modules ('e.so'), python > scripts ('s1.py', 's2.py') and data files in a separate > directory 'MyProject' under site-packages, but I want them > to be available from the root package, so that I can type > 'from e import *', rather than 'from MyProject.e import > *'. Is there any way to do this with distutils? I don't think that's a distutils problem, it's just the way packages are set up. Would 'from MyProject import *' also be okay? Then you could write a __init__.py which imports everything from the 'e' module: 'from e import *', and place it in the package directory. Johannes Gijsbers _____________________________________________________________________ // free anonymous email || forums \\ subZINE || anonymous browsing subDIMENSION -- http://www.subdimension.com

1 0

Non-typical scenario
by Peter Bienstman April 8, 2002

April 8, 2002

I'm trying to write a setup.py, but I'm having a few problems because of the following a-typical requirements: 1) I want all my extension modules ('e.so'), python scripts ('s1.py', 's2.py') and data files in a separate directory 'MyProject' under site-packages, but I want them to be available from the root package, so that I can type 'from e import *', rather than 'from MyProject.e import *'. Is there any way to do this with distutils? 2) the development versions of s1.py and s2.py live in completely different directories, but I still want distutils to copy them over to the same 'MyProject' directory, where they would be avaible from the root package. I haven't found a way to do this. 3) using data_files = [("MyProjects"), ...] copies the data files over to /usr/local/MyProjects, however, I want them to end up in /usr/local/lib/python-x.x/site-packages/MyProjects, where all my other stuff lives. If I have to explicitly specify a Python version number, my code won't be portable. Thanks for any help you can provide. Kind regards, Peter

1 0

Adding compiler-options during build
by Albert Chin April 5, 2002

April 5, 2002

How do I add options for the compiler in setup.py? I'd like to add the -qlanglvl=extended option on AIX for a particular Python extension. -- albert chin (china(a)thewrittenword.com)

1 0

RE: [Fwd: [Distutils] Automatic creation of .pyc files]
by Andrew MacIntyre April 1, 2002

April 1, 2002

> -----Original Message----- > From: Andy Todd [mailto:andy47@halfcooked.com] > Sent: Tuesday, 26 March 2002 2:29 PM {...} > When packaging a Python module is it possible to stop the automatic > creation of .pyc on installation? > > I ask because in PythonCard we currently store our > configuration data in > files that are imported but never executed (i.e. they just contain a > list). When I package up the prototype and make it available I would > like to be able to stop .pyc versions of these files being created. Perhaps I'm missing something, but just importing the module will force recompilation and creation of the .pyc file anyway (unless the directory containing it is not writeable) so I don't see what the real issue is. If the .py file gets updated, the .pyc file will then get updated (file/directory permissions permitting) on the next import. If this really bugs you, perhaps eval() is a more attractive solution. ----------------------------------------------------------------------- Andrew MacIntyre \ E-mail: andrew.macintyre(a)aba.gov.au Planning & Licensing Branch \ Tel: +61 2 6256 2812 Australian Broadcasting Authority \ Fax: +61 2 6253 3277 -> "These thoughts are mine alone!" <----------------------------------

1 0