[Python-Dev] PEP 467: Minor API improvements for bytes & bytearray

Devin Jeanpierre jeanpierreda at gmail.com
Mon Aug 18 05:50:40 CEST 2014

On Sun, Aug 17, 2014 at 7:14 PM, Alex Gaynor <alex.gaynor at gmail.com> wrote:
> I've hit basically every problem everyone here has stated, and in no uncertain
> terms am I completely opposed to deprecating anything. The Python 2 to 3
> migration is already hard enough, and already proceeding far too slowly for
> many of our tastes. Making that migration even more complex would drive me to
> the point of giving up.

Could you elaborate what problems you are thinking this will cause for you?

It seems to me that avoiding a bug-prone API is not particularly
complex, and moving it back to its 2.x semantics or making it not work
entirely, rather than making it work differently, would make porting
applications easier. If, during porting to 3.x, you find a deprecation
warning for bytes(n), then rather than being annoying code churny
extra changes, this is actually a bug that's been identified. So it's
helpful even during the deprecation period.

-- Devin

More information about the Python-Dev mailing list