Le vendredi 03 octobre 2008 à 15:57 +1300, Greg Ewing a écrit : > On Thu, Oct 02, 2008 at 01:20:45PM +0200, Josselin Mouette wrote: > > Sorry, but things don’t work this way. Anything that is *not* a .py file > > should not land in the python module directories. > > So where *should* they go, on platforms where there is > no defined place for such things?
If there is no standard place, you can simply define one.
> And how can the code
> that uses them find them without platform-specific
> knowledge?
With a simple API to locate them. In fact, you don’t even need an API.
If you distribute a python program using autoconf, you can simply say:
mydata = file (@datadir@ "/blah/blahblah.dat",'r')
call the file blah.py.in, and add it to AC_CONFIG_FILES. Autoconf will
detect the correct directory depending on the platform.
Cheers,
--
.''`.
: :' : We are debian.org. Lower your prices, surrender your code.
`. `' We will add your hardware and software distinctiveness to
`- our own. Resistance is futile.
signature.asc
Description: Ceci est une partie de message numériquement signée
_______________________________________________ Distutils-SIG maillist - [email protected] http://mail.python.org/mailman/listinfo/distutils-sig
