On 21/05/14 11:32 -0400, Doug Hellmann wrote:
On Thu, May 15, 2014 at 11:41 AM, Victor Stinner
victor.stin...@enovance.com wrote:
Hi,
The functions safe_decode() and safe_encode() have been ported to Python 3,
and changed more than once. IMO we can still improve these functions to make
them
On Thu, May 15, 2014 at 11:41 AM, Victor Stinner
victor.stin...@enovance.com wrote:
Hi,
The functions safe_decode() and safe_encode() have been ported to Python 3,
and changed more than once. IMO we can still improve these functions to make
them more reliable and easier to use.
(1) My
On 05/15/2014 11:41 AM, Victor Stinner wrote:
Hi,
The functions safe_decode() and safe_encode() have been ported to Python 3,
and changed more than once. IMO we can still improve these functions to make
them more reliable and easier to use.
(1) My first concern is that these functions
On Wed, May 21, 2014 at 12:30 PM, John Dennis jden...@redhat.com wrote:
On 05/15/2014 11:41 AM, Victor Stinner wrote:
Hi,
The functions safe_decode() and safe_encode() have been ported to Python 3,
and changed more than once. IMO we can still improve these functions to make
them more
Hi,
The functions safe_decode() and safe_encode() have been ported to Python 3,
and changed more than once. IMO we can still improve these functions to make
them more reliable and easier to use.
(1) My first concern is that these functions try to guess user expectation
about encodings. They
