2009/9/19 Wolfgang Schnerring w...@wosc.de:
The idea of this *not* being a setup() argument was to keep
compatibility with setuptools (since it will complain about arguments it
doesn't understand). This would enable a package to use setuptools or
distribute (or whatever ;) for python2, and
Gerry Reno wrote:
Ok, I got the __file__ problem solved but now I want to do this whole
deb pkg create as just a single command in my own setup.py. How can I
do this?
I'm thinking something like:
# my setup.py
import stdeb
Command(mycmd):
initialize_option...
finalize_option...
Ok, I got the __file__ problem solved but now I want to do this whole
deb pkg create as just a single command in my own setup.py. How can I
do this?
I'm thinking something like:
# my setup.py
import stdeb
Command(mycmd):
initialize_option...
finalize_option...
run
On Fri, Sep 18, 2009 at 8:13 PM, Sridhar Ratnakumar
sridh...@activestate.com wrote:
On Tue, 15 Sep 2009 17:42:24 -0700, exar...@twistedmatrix.com wrote:
What use cases do we have? There's the one described above, which lots of
people have been talking about. I think there's another one
Hi Chris,
You can have a look to minitage (http://minitage.org/).
Minitage have 3 main parts:
* package and dependencies management and isolation (minitage.core)
- construct and manage softwares in total isolation from the host and
thus, platform independant (unix) (libxml,
The way setuptools (and thus buildout) does namespace packages doesn't work
with how Django looks for management commands. Django only looks in the
first package in the namespace on the system path and ignores the rest.
Pip deals with namespace packages differently (with those .pth files I
On Sat, Sep 19, 2009 at 2:48 PM, Kyle MacFarlane
kylemacfarl...@gmail.com wrote:
The way setuptools (and thus buildout) does namespace packages doesn't work
with how Django looks for management commands. Django only looks in the
first package in the namespace on the system path and ignores the
At 01:48 PM 9/19/2009 +0100, Kyle MacFarlane wrote:
The way setuptools (and thus buildout) does namespace packages
doesn't work with how Django looks for management commands. Django
only looks in the first package in the namespace on the system path
and ignores the rest.
If they use the
Gerry Reno wrote:
What you want to do is probably possible, but I don't have the
motivation to do it myself. I guess it could allow a bdist_deb option,
but IMO that's not particularly desirable -- the Debian source package
emitted by stdeb can be compiled for any Debian derivative for any
Andrew Straw wrote:
Gerry Reno wrote:
Ok, I got the __file__ problem solved but now I want to do this whole
deb pkg create as just a single command in my own setup.py. How can I
do this?
I'm thinking something like:
# my setup.py
import stdeb
Command(mycmd):
initialize_option...
Andrew Straw wrote:
Gerry Reno wrote:
What you want to do is probably possible, but I don't have the
motivation to do it myself. I guess it could allow a bdist_deb option,
but IMO that's not particularly desirable -- the Debian source package
emitted by stdeb can be compiled for any Debian
Ok, I have a setup.py that imports stdeb and creates a 'bdist_deb' command.
The entire thing is working except for the last subcommand for
dpkg-buildpackage is trying to build for python2.4 and failing.
dpkg-buildpackage fails in the fakeroot...
...
debian/rules build
python2.4 -c import
Gerry Reno wrote:
Ok, I have a setup.py that imports stdeb and creates a 'bdist_deb'
command.
Great.
The entire thing is working except for the last subcommand for
dpkg-buildpackage is trying to build for python2.4 and failing.
dpkg-buildpackage fails in the fakeroot...
...
debian/rules
Ok, I found how to control the python version: XS-Python-Version
So now it is using python2.5 but dpkg-buildpackage hits an error:
error: option --single-version-externally-managed not recognized
What is this option?
I've been searching but I don't find how to solve this.
Is there a way to fix
14 matches
Mail list logo
