Mailman 3 March 2004 - Distutils-SIG

build subcommand order
by Dan Schult 26 Mar '04

26 Mar '04

Thanks for the help--- I put in the cmdclass only {build: my_build} since I don't have a my_build_py. It works great! Still it seems that everyone using Swig to create packages will either have to run setup twice, or put this code in. Thanks again, Dan Schult

4 3

Encrypted document
by jose＠sferacarta.com 26 Mar '04

26 Mar '04

1 0

Cash in with Google
by Terry Abernathy 25 Mar '04

25 Mar '04

1 0

[ANN] pkgdata
by Bob Ippolito 25 Mar '04

25 Mar '04

As per the BOF last night, here is the pkgdata module that I mentioned. Currently the only project using it is pygame. The "sys.datapath" mechanism that I talked about *could actually be implemented* on top of this system, supposing an appropriate adapter was written to support it! Remember: pkgdata is *just a hook*. It doesn't do anything other give the eventual option of doing something smarter than os.path.join(os.path.basedir(__file__), data). When you figure out what something smarter is, or you change your mind about what the smarter solution is (inside of an app bundle vs. system wide install, etc.), you don't have to refactor any of the code that uses pkgdata. The current implementation, and documentation, is here: http://undefined.org/python/pkgdata-0.1.tgz """ pkgdata is a simple, extensible way for a package to acquire data file resources. The implementation is lightweight, and is intended to be included *inside* your Python packages. """ It's based on PyProtocols (but the implementation doesn't require it unless you want to override the default mechanism). Basically, it's useful for py2exe and OS X bundlebuilder type situations. It's a simple and flexible alternative to os.path.join(os.path.dirname(__file__), "myresource"). The source is simple, and has lots of examples. Read if you're interested. If you would like to see additional examples of its use, here are the interesting things to look at if you check out pygame CVS: pygame/lib/pkgdata.py (this is the pkgdata "client") pygame/lib/macosx.py (usage from python) pygame/src/font.c (usage from C) pygame/src/display.c (more usage from C) pygame/examples/macosx/aliens_app_example/ (this has the pkgdata "host adapter" for bundlebuilder type situations) The fact that it uses PyProtocols is just personal preference. It could work on top of any sort of global registry, but PyProtocols is a really nice global registry that made my implementation extremely terse. -bob

3 6

Re: build subcommand order
by Dan Schult 25 Mar '04

25 Mar '04

M.-A. Lemburg wrote: >Dan Schult wrote: >> I propose a simple change of the order of the build commands >> so that build_py is last. > >No. That would break other people's scripts. Can you think of one possible way that would break someone's script? A careful reading of build_py.py tells me it is just copying files... That should't affect build_ext, build_clibs or build_scripts... > >You can however, have distutils rerun the build_py script by >calling: > >build_py = self.distribution.reinitialize('build_py') >build_py.ensure_finalized() >build_py.run() > >-- >Marc-Andre Lemburg >eGenix.com I think I'm confused.... What is "self" supposed to refer to here? Where am I supposed to put these commands? Thanks for your quick response, Dan Schult

1 0

build subcommand order
by Dan Schult 25 Mar '04

25 Mar '04

I have been using swig 1.3 along with distutils to make a package and I'm having trouble with the subcommand order for "build". The order is set at the bottom of command.build.py to be: build_py build_clibs build_ext build_scripts My problem is that swig gets run during build_ext and creates a class definition in a new *.py file. That python file needs to be moved into the staging area, but build_py doesn't find it because it is created AFTER build_py is run. I propose a simple change of the order of the build commands so that build_py is last. It is unlikely that build_py would make any actions that affect the other command, but quite likely (especially given the nature of Swig) that other actions may create python files. I know one can always use: python setup.py build_ext build_py but I don't think every person that is packaging (or unpackaging) a swig distribution should have to document that --or figure it out. If there is a better place to submit changes/improvements please le me know. Thanks for a Great Package!! Dan Schult

3 2

Content violation
by postmaster＠anoto.com 25 Mar '04

25 Mar '04

Content violation found in email message. From: distutils-sig(a)python.org To: support(a)cpen.com File(s): message.scr Matching filename: *.scr

1 0

Re: Delivery Server
by House IMSMail System01 24 Mar '04

24 Mar '04

Message contains prohibited attachment; message rejected. Contact the intended recipient for an alternative method to transmit attachment.

1 0

This is a VERY different affiliate program
by Alexis Sands 23 Mar '04

23 Mar '04

1 0

Help (python module)
by jfern＠cng.fr 23 Mar '04

23 Mar '04

Hello, I'm trying to install the biopython module on our lab computer: (biopython-1.24). I do this: > tar -xzvpf biopython-1.24.tgz > cd biopython-1.24 > python setup.py install And..... running install running build running build_py running build_ext building 'Bio.PDB.mmCIF.MMCIFlex' extension gcc -pthread -shared build/temp.linux-i686-2.3/Bio/PDB/mmCIF/lex.yy.o build/temp.linux-i686-2.3/Bio/PDB/mmCIF/MMCIFlexmodule.o -lfl -o build/lib.linux-i686-2.3/Bio/PDB/mmCIF/MMCIFlex.so /usr/bin/ld: cannot find -lfl collect2: ld returned 1 exit status error: command 'gcc' failed with exit status 1 What can I do? Thanks, FERNANDEZ Julien INSERM E0223 - FRANCE Molecular Neurogenetic Laboratory

2 1