Message 211106 - Python tracker

➜

This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author	vstinner
Recipients	pitrou, python-dev, serhiy.storchaka, vstinner
Date	2014-02-12.17:31:43
SpamBayes Score	-1.0
Marked as misclassified	Yes
Message-id	<[email protected]>
In-reply-to

Content
> Sorry, issue20599_ascii_ioencoding.patch doesn't fix the issue. Sorry again, I didn't read issue20599_ascii_ioencoding.patch carefully: it doesn't make sense to use the isolated mode and to set a Python environment variable (PYTHONIOENCODING). The purpose of the isolated mode is to ignore all Python environment variables... I (hope I) fixed the test, but in fact, the test showed another bug: print() cannot be used during Python exit in destructor. It means for example that Python may not be able to display errors at exit. I don't know if this issue should be closed. Maybe a new issue should be opened to address the codec issue at exit?

> Sorry, issue20599_ascii_ioencoding.patch doesn't fix the issue.

Sorry again, I didn't read issue20599_ascii_ioencoding.patch carefully: it doesn't make sense to use the isolated mode and to set a Python environment variable (PYTHONIOENCODING). The purpose of the isolated mode is to ignore all Python environment variables...

I (hope I) fixed the test, but in fact, the test showed another bug: print() cannot be used during Python exit in destructor. It means for example that Python may not be able to display errors at exit.

I don't know if this issue should be closed. Maybe a new issue should be opened to address the codec issue at exit?

History
Date	User	Action	Args
2014-02-12 17:31:43	vstinner	set	recipients: + vstinner, pitrou, python-dev, serhiy.storchaka
2014-02-12 17:31:43	vstinner	set	messageid: <[email protected]>
2014-02-12 17:31:43	vstinner	link	issue20599 messages
2014-02-12 17:31:43	vstinner	create