[issue22819] Python3.4: xml.sax.saxutils.XMLGenerator.__init__ fails with pythonw.exe

2015-02-10 Thread Serhiy Storchaka
Changes by Serhiy Storchaka storch...@gmail.com: -- resolution: - not a bug status: pending - closed ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue22819 ___

[issue22819] Python3.4: xml.sax.saxutils.XMLGenerator.__init__ fails with pythonw.exe

2014-11-27 Thread Serhiy Storchaka
Changes by Serhiy Storchaka storch...@gmail.com: -- status: open - pending ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue22819 ___ ___

[issue22819] Python3.4: xml.sax.saxutils.XMLGenerator.__init__ fails with pythonw.exe

2014-11-08 Thread Edward K. Ream
New submission from Edward K. Ream: In Python3.2 xml.sax.saxutils.XMLGenerator.__init__ succeeds if the out keyword argument is not given and sys.stdout is None, which will typically be the case when using pythonw.exe. Alas, on Python3.4, the ctor throws an exception in this case. This is a

[issue22819] Python3.4: xml.sax.saxutils.XMLGenerator.__init__ fails with pythonw.exe

2014-11-08 Thread Serhiy Storchaka
Serhiy Storchaka added the comment: In any case XMLGenerator is not usable if the out keyword argument is not given and sys.stdout is None. Just the exception will be raised later. I consider early failure as a feature, not a bug. -- nosy: +serhiy.storchaka

[issue22819] Python3.4: xml.sax.saxutils.XMLGenerator.__init__ fails with pythonw.exe

2014-11-08 Thread R. David Murray
R. David Murray added the comment: Agreed. I was going to ask what it was that 3.2 did that was useful. -- nosy: +r.david.murray ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue22819 ___

[issue22819] Python3.4: xml.sax.saxutils.XMLGenerator.__init__ fails with pythonw.exe

2014-11-08 Thread Serhiy Storchaka
Serhiy Storchaka added the comment: FYI the code was changed in issue1470548. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue22819 ___ ___