Re: [Distutils] Problem upgrading docutils with setuptools
At 06:46 PM 1/25/2006 +0100, Maciek Starzyk wrote:
Is there a way to tell setup.py to do the equivalent of easy_install -m while upgrading its dependencies ?
No, not really. You could always just bundle the "roman" module in your project, I suppose, or create a package for it on PyPI and make it a requirement of your project. These approaches wouldn't change docutils' behavior, but it'd ensure that *your* projects using docutils would work.
On Jan 25, 2006, at 10:14 AM, Phillip J. Eby wrote:
At 06:46 PM 1/25/2006 +0100, Maciek Starzyk wrote:
Is there a way to tell setup.py to do the equivalent of easy_install -m while upgrading its dependencies ?
No, not really. You could always just bundle the "roman" module in your project, I suppose, or create a package for it on PyPI and make it a requirement of your project. These approaches wouldn't change docutils' behavior, but it'd ensure that *your* projects using docutils would work.
Would setuptools notice the conflict between the roman module in both eggs? -bob
At 10:26 AM 1/25/2006 -0800, Bob Ippolito wrote:
On Jan 25, 2006, at 10:14 AM, Phillip J. Eby wrote:
At 06:46 PM 1/25/2006 +0100, Maciek Starzyk wrote:
Is there a way to tell setup.py to do the equivalent of easy_install -m while upgrading its dependencies ?
No, not really. You could always just bundle the "roman" module in your project, I suppose, or create a package for it on PyPI and make it a requirement of your project. These approaches wouldn't change docutils' behavior, but it'd ensure that *your* projects using docutils would work.
Would setuptools notice the conflict between the roman module in both eggs?
Not as long as docutils is installed via EasyInstall. Setuptools doesn't care about duplication *inside* eggs, only with stuff installed *outside* of eggs. (Unfortunately, there's a bit of an issue with .egg-info eggs, in that you still get conflict warnings for them at the moment.)
Hi, Bob Ippolito:
Would setuptools notice the conflict between the roman module in both eggs?
There is no conflict -- your module would be called "whatever.roman". -- Matthias Urlichs | {M:U} IT Design @ m-u-it.de | smurf@smurf.noris.de Disclaimer: The quote was selected randomly. Really. | http://smurf.noris.de - - "You can't find a hermit to teach you herming, because of course that rather spoils the whole thing." -- Terry Pratchett (Small Gods)
On Jan 25, 2006, at 10:44 AM, Matthias Urlichs wrote:
Bob Ippolito:
Would setuptools notice the conflict between the roman module in both eggs?
There is no conflict -- your module would be called "whatever.roman".
No, there is. Including roman was suggested as a way to satisfy a docutils dependency. Docutils expects roman to be a top-level module, and it will install it -- but only if roman can't be imported at the time setup.py is run. This behavior is problematic for packaging software (eggs and any other bdist command). Basically, if the person packaging docutils happens to have docutils installed at the time of packaging, the resultant package will be missing a required component. In the case of eggs, the detected roman module will disappear as soon as the new egg is activated, so you have to easy_install it twice (or equivalent) in order to get something that works. -bob
participants (3)
-
Bob Ippolito -
Matthias Urlichs -
Phillip J. Eby