docutils roman

[GoogleCodeExporter]

import roman causes an error No module named roman.

occurs in docutils/parsers/rst/states.py

include roman for importing.

Original issue reported on code.google.com by kylecovi...@gmail.com on 9 Feb 2011 at 7:32

[GoogleCodeExporter]

trying to add everything that docutils depends on into out repository is not a 
good idea. then we would have to include everything those dependencies require 
and so on...

the os specific installer should handle the dependencies. which os has this 
error? 

Original comment by anup.parikh on 9 Feb 2011 at 7:44

• Added labels: Milestone-Release1.85

[GoogleCodeExporter]

I thought that was the idea of putting everything on the svn.  If this is the 
thinking then we should take docutils out of svn and make the user install that 
independently.

The error is in linux64.  I could get docutils myself using sudo apt-get but 
then it might not be in the right place per the settings of Red-R.

If you want to make this an exception then we should make the importing of 
docutils an os specific procedure.

Original comment by kylecovi...@gmail.com on 9 Feb 2011 at 7:56

[GoogleCodeExporter]

for reports to work  we need docutils snapshot 2010-07-21, r6380. the
docutils from apt-get is different from the one we have coded for, so
reports will fail.

I make the windows and mac installers internally consistent, so I can
manually include the correct docutils.  It does not have to be part of the
svn. Its up to you how you want to handle this on linux.

Original comment by anup.parikh on 9 Feb 2011 at 8:35

[GoogleCodeExporter]

Original comment by anup.parikh on 9 Feb 2011 at 11:02

• Changed state: Fixed