On 2011-05-24, John Arbash Meinel wrote: > I just tried upgrading all of my python packages using "easy_install - > U -Z1 -O $PACKAGES". And that upgraded me from docutils-0.6 to > docutils-0.7 (and a bunch of other packages). However after doing so, > sphinx-build failed saying that it could not find "roman" which came > with docutils. I checked, and docutils-0.6*.egg/ has roman.py but > docutils-0.7*.egg/ does not.
The original distribution (provided on sourceforge) contains a copy of the external module "roman". However, it is only used as fallback, if no "roman" is found in the PYTHONPATH. The removal from the egg might be related to: http://sourceforge.net/tracker/?func=detail&aid=2971827&group_id=38414&atid=422030 > Should sphinx be getting roman from somewhere else? Is this a real > failure? Distutils allows specifying a dependency since version 2.5 (http://docs.python.org/release/2.5/whatsnew/pep-314.html) while Docutils supports >= 2.3. If Sphinx depends on >= 2.5 anyway, it should specify "roman" as a dependency in the setup.py file. > For now, I just edited easy_install.pth to go back to docutils-0.6, > but it would be nice to use the latest versions of things. You can install "roman" independently of Docutils/Sphinx. This should solve your problem. Günter -- You received this message because you are subscribed to the Google Groups "sphinx-dev" group. To post to this group, send email to sphinx-dev@googlegroups.com. To unsubscribe from this group, send email to sphinx-dev+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/sphinx-dev?hl=en.
