Re: Tool support for private modules

2007-10-01 Thread Josselin Mouette
Le lundi 01 octobre 2007 à 14:42 +1000, Ben Finney a écrit : 3.1.1 Programs Shipping Private Modules A program using /usr/bin/python as interpreter can come up with private Python modules. These modules should be installed in /usr/share/module, or /usr/lib/module if the

Re: Tool support for private modules

2007-10-01 Thread Ben Finney
Josselin Mouette [EMAIL PROTECTED] writes: Le lundi 01 octobre 2007 à 14:42 +1000, Ben Finney a écrit : But the Python distutils and setuptools will install the modules to /usr/lib/site-python/. Hrm, they shouldn't. With a default setup, public modules are shipped to

Re: Tool support for private modules

2007-10-01 Thread Bernd Zeimetz
That's where the distutils and setuptools place them by default, yes. I don't know what magic is required to put them elsewhere; that may be part of the answer, if someone can instruct me on how to do it. You shoul dupload your work somewhere, teaching you is almost impossible if one can't

Re: Tool support for private modules

2007-10-01 Thread Ben Finney
Bernd Zeimetz [EMAIL PROTECTED] writes: You shoul dupload your work somewhere, teaching you is almost impossible if one can't see what's wrong. I'm not presenting something as wrong. I'm asking for guidance on how to do things right. If the policy recommends that packages be set up a

Re: Tool support for private modules

2007-10-01 Thread Bernd Zeimetz
If the policy recommends that packages be set up a particular way (put package-specific modules in '/usr/share/package/'), but the standard tools behave differently (put all modules by default in '/usr/lib/pythonX.Y/site-packages/'), then there's a step that needs to be taken to get from the

Re: Tool support for private modules

2007-10-01 Thread Josselin Mouette
Le lundi 01 octobre 2007 à 18:37 +1000, Ben Finney a écrit : That would work if the files were shipped in /usr/lib/python2.X/site-packages. That's where the distutils and setuptools place them by default, yes. I don't know what magic is required to put them elsewhere; that may be part of

Re: Tool support for private modules

2007-10-01 Thread Ben Finney
Josselin Mouette [EMAIL PROTECTED] writes: Le lundi 01 octobre 2007 à 18:37 +1000, Ben Finney a écrit : How can I use the tools available — distutils, setuptools, debhelper — to install these package-specific modules to a package-specific location, such that all the programs in the

cheap sluts

2007-10-01 Thread Bernardo
best wh0res list www spellonme dot com silvery neologize Venezuela carnifying impregnate drivelling Parisianizations ironback -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: Tool support for private modules

2007-10-01 Thread Ben Finney
Ben Finney [EMAIL PROTECTED] writes: How can I best conform to the [Debian policy for Python modules specific to a single package]? As an example, here's a Python package I'm trying to get packaged for Debian. (I am the upstream author of this one, but I'm interested in a solution that

Re: Tool support for private modules

2007-10-01 Thread Bernd Zeimetz
As an example, here's a Python package I'm trying to get packaged for Debian. (I am the upstream author of this one, but I'm interested in a solution that *doesn't* involve significant changes to the upstream code.) URL:http://cheeseshop.python.org/pypi/gracie/ The first thing I'd do