Re: [Docutils-users] FileInput exiting on IOError

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

Dear David,

I am still waiting for a consensus regarding the IOError handling.

On 2012-01-22, Guenter Milde wrote:
> On 2012-01-20, David Goodger wrote:
>> On Fri, Jan 20, 2012 at 05:01, Guenter Milde <mi...@us...> wrote:
>>> On 2010-12-28, Eli Bendersky wrote:

Maybe we can start with the simpler decisions:

>>>> I'm using docutils programmatically for converting ReST to HTML
>>>> (specifically docutils.core.publish_from_doctree). Since the usage is
>>>> programmatic (controlled by my application) I must have full control of
>>>> exceptions for logging. However, I noticed that the FileInput class
>>>> used by docutils for various purposes exits the application (sys.exit)
>>>> when it can't find a file.

IMO this is a valid bug report. There should be an option to suppress the
conversion of IOError into sys.exit() (especially for programmatic use).

...

>> Instead, how about adding a command-line/config option to control
>> this? Then programmatic users can handle any exceptions themselves,
>> and regular users won't see any change.

> I don't think that an additional config setting is necessary. The
> "traceback" setting already switches between passing exceptions to the
> caller or catching and reporting exceptions by
> core.Publisher.report_Exceptions.

Could you agree on using the "traceback" setting for IOErrors, too?

Regular users would only see a change, if they use the --traceback
option. Tey get a traceback instead of the short error message, e.g.

  Traceback (most recent call last):
    File "/home/milde/.bin/rst2html", line 23, in <module>
      ...
  docutils.io.InputError: [Errno 2] Datei oder Verzeichnis nicht gefunden: u'foffy'

I hope you can agree on these two points and look forward to discussing the
implementation.

Günter