Re: [Docutils-users] docutils Causing Python 2.7.3 Dumps Under Cgywin?

[Guenter M. <mi...@us...>]

Dear Tim,

On 2013-03-17, Tim Daneliuk wrote:
> I have a standard makefile I use to create a variety of output media from
> a given rst file.  This recently stopped working on the Cygwin system
> I use for this task.

> Upon further review, I found that that when the rst2* programs
> run, they produce proper output, but when they complete,
> Python aborts.  This is causing the makefile to terminate
> prematurely.

> I am also see this error when I attempt to produce html:

><stdin>:: (ERROR/3) Cannot embed stylesheet '/home/luser/Docs/myproject/html4css1.css': No such file or directory

> Any ideas what's going on here?  Cygwin is up-to-date and seems to otherwise
> be OK.  The same rst file works fine on native Linux and FreeBSD systems.

Thanks for the report. As already said, it is difficult to find the reason
without further info. I have some guesses, though:

* A common problem (and a nightmare for parallel Py2x and Py3x development)
  are the encoding issues. It may well be that Cygwin adds to them in a way
  that cannot be tested otherwhere.
  
  The biggest problem was encoding errors preventing sensible error messages
  --- errors when reporting an error. I thought to have them solved but
  maybe some resurfaces in your case.
  
  If you run one of the aborting commands from the command line and add the
  --traceback command line option, do you get a traceback?
  
  If yes, this would be an immense help, if no, the actuall error message
  would still be valuable info.
  
* It may be that Cygwin uses a newer Python version than your alternatives.
  There are several bugreports regarding Python beta versions that are not
  handled yet because 
  
  + we cannot reproduce them with the stable Python release (here on
    Debian/testing).
  + some seem to be rather Python bugs than Docutils bugs and we prefer to
    concentrate our scare recourses on the problems with stable releases.
    (patches that anticipate problems with upcoming changes are welcome,
    of course).

Could your try whether using an older Python version solves the problem?
Could you try with Python 3?

Thanks,

Günter