3.1 -> 3.2: base64 lost deprecation warning

Robert sigzero at gmail.com
Mon Feb 28 23:01:44 CET 2011


On 2011-02-28 15:51:32 -0500, Ethan Furman said:

> Python 3.1.2 (r312:79149, Mar 21 2010, 00:41:52) [MSC v.1500 32 bit
> (Intel)] on win32
> Type "help", "copyright", "credits" or "license" for more information.
> --> import base64
> --> base64.encodestring(b'this is a test')
> __main__:1: DeprecationWarning: encodestring() is a deprecated alias,
> use encodebytes()
> b'dGhpcyBpcyBhIHRlc3Q=\n'
> 
> 
> Python 3.2 (r32:88445, Feb 20 2011, 21:29:02) [MSC v.1500 32 bit
> (Intel)] on win
> 32
> Type "help", "copyright", "credits" or "license" for more information.
> --> import base64
> --> base64.encodestring(b'another test')
> b'dGhpcyBpcyBhIHRlc3Q=\n'
> 
> 
> The deprecation warning has gone away in 3.2, but the function
> remains... does anyone know if this was intentional?
> 
> ~Ethan~

I only found this:

Issue #3613: base64.{encode,decode}string are now called
  base64.{encode,decode}bytes which reflects what type they accept and return.
  The old names are still there as deprecated aliases.

Doesn't exlain the "no warning" though.

-- 
Robert





More information about the Python-list mailing list