Hello,
How can I convince distribute to install a module in a different root directory, without also switching to the ~/.local/ scheme?
I was surprised to find that the following doesn't work:
$ python setup.py install --single-version-externally-managed --root staging/ running install running build running build_py creating build creating build/lib.linux-i686-2.6 creating build/lib.linux-i686-2.6/mymodule copying mymodule/mymodule.py -> build/lib.linux-i686-2.6/mymodule copying mymodule/__init__.py -> build/lib.linux-i686-2.6/mymodule running install_lib creating staging creating staging/home creating staging/home/nikratio creating staging/home/nikratio/.local creating staging/home/nikratio/.local/lib creating staging/home/nikratio/.local/lib/python2.6 creating staging/home/nikratio/.local/lib/python2.6/site-packages creating staging/home/nikratio/.local/lib/python2.6/site-packages/mymodule copying build/lib.linux-i686-2.6/mymodule/mymodule.py -> staging/home/nikratio/.local/lib/python2.6/site-packages/mymodule copying build/lib.linux-i686-2.6/mymodule/__init__.py -> staging/home/nikratio/.local/lib/python2.6/site-packages/mymodule [...]
I want mymodule to end up somewhere in staging/usr/lib/*.
Thanks,
-Nikolaus
On Sun, May 9, 2010 at 9:30 PM, Nikolaus Rath Nikolaus@rath.org wrote:
Hello,
How can I convince distribute to install a module in a different root directory, without also switching to the ~/.local/ scheme?
I was surprised to find that the following doesn't work:
$ python setup.py install --single-version-externally-managed --root staging/
...
[...]
I want mymodule to end up somewhere in staging/usr/lib/*.
Having .local here looks like a bug to me. Could you create an issue with details ?
- Name of the package you are installing (in case the setup.py has something special) - version of distribute - your OS
Thanks ! Tarek
On May 9, 2010, at 5:47 PM, Tarek Ziadé wrote:
Having .local here looks like a bug to me. Could you create an issue with details ?
For what it's worth, I have had similar things happen when I had forogtten that I created a ~/.pydistutils.cfg. Have you made sure that there isn't one there?
On Mon, May 10, 2010 at 1:41 AM, Glyph Lefkowitz glyph@twistedmatrix.com wrote:
On May 9, 2010, at 5:47 PM, Tarek Ziadé wrote:
Having .local here looks like a bug to me. Could you create an issue with details ?
For what it's worth, I have had similar things happen when I had forogtten that I created a ~/.pydistutils.cfg. Have you made sure that there isn't one there?
Great reflex, thanks :)
Glyph Lefkowitz glyph@twistedmatrix.com writes:
On May 9, 2010, at 5:47 PM, Tarek Ziadé wrote:
Having .local here looks like a bug to me. Could you create an issue with details ?
For what it's worth, I have had similar things happen when I had forogtten that I created a ~/.pydistutils.cfg. Have you made sure that there isn't one there?
No, that was it. And I certainly don't remember ever touching or creating that file either. Thanks!
Best,
-Nikolaus
On May 10, 2010, at 9:14 AM, Nikolaus Rath wrote:
Glyph Lefkowitz glyph@twistedmatrix.com writes:
On May 9, 2010, at 5:47 PM, Tarek Ziadé wrote:
Having .local here looks like a bug to me. Could you create an issue with details ?
For what it's worth, I have had similar things happen when I had forogtten that I created a ~/.pydistutils.cfg. Have you made sure that there isn't one there?
No, that was it. And I certainly don't remember ever touching or creating that file either. Thanks!
Does distutils have a flag for ignoring ~/.pydistutils.cfg, by the way? I hit this fairly often and it's always a nasty surprise *right* at the end of a build process. It would be nice to have all official-release scripts specify an option that specifically overrides per-user configuration.
On Mon, May 10, 2010 at 8:30 PM, Glyph Lefkowitz glyph@twistedmatrix.com wrote:
On May 10, 2010, at 9:14 AM, Nikolaus Rath wrote:
Glyph Lefkowitz glyph@twistedmatrix.com writes:
On May 9, 2010, at 5:47 PM, Tarek Ziadé wrote:
Having .local here looks like a bug to me. Could you create an issue with details ?
For what it's worth, I have had similar things happen when I had forogtten that I created a ~/.pydistutils.cfg. Have you made sure that there isn't one there?
No, that was it. And I certainly don't remember ever touching or creating that file either. Thanks!
Does distutils have a flag for ignoring ~/.pydistutils.cfg, by the way? I hit this fairly often and it's always a nasty surprise *right* at the end of a build process. It would be nice to have all official-release scripts specify an option that specifically overrides per-user configuration.
Yes, someone provided this patch a while ago and I've added it (it's "--no-user-cfg" in 2.6).
We should ask people to run this option to get a pseudo-similar execution context when we track a bug
Distutils-SIG maillist - Distutils-SIG@python.org http://mail.python.org/mailman/listinfo/distutils-sig
On May 10, 2010, at 4:05 PM, Tarek Ziadé wrote:
Yes, someone provided this patch a while ago and I've added it (it's "--no-user-cfg" in 2.6).
Do you mean in 2.7? I see it documented here: http://docs.python.org/dev/distutils/builtdist.html, but not here: http://docs.python.org/distutils/builtdist.html.
-
Glyph Lefkowitz -
Nikolaus Rath -
Tarek Ziadé