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 ebfe
Recipients ebfe, lemburg, pitrou, vstinner
Date 2009-01-05.06:44:08
SpamBayes Score 0.046594072
Marked as misclassified No
Message-id <1231137850.19.0.539138296604.issue4757@psf.upfronthosting.co.za>
In-reply-to
Content
The current behaviour may help the majority by ignorance and cause weird
errors for others. We tell people that Python distincts between Text and
Data but actually treat it all the same by implicit encoding.

Modules that only operate on Bytes should reject Unicode-objects in
Python3; it's a matter of 3 lines to display a warning in Python 2.
Those modules that usually operate on Text but have single functions
that operate on Bytes should display a warning but not enforce explicit
encoding.

Also see #4821 and #4818 where unicode already got rejected by the
openssl-driven classes but silently accepted by the build-in ones.
History
Date User Action Args
2009-01-05 06:44:10ebfesetrecipients: + ebfe, lemburg, pitrou, vstinner
2009-01-05 06:44:10ebfesetmessageid: <1231137850.19.0.539138296604.issue4757@psf.upfronthosting.co.za>
2009-01-05 06:44:09ebfelinkissue4757 messages
2009-01-05 06:44:08ebfecreate