[issue12516] imghdr.what should take one argument

Change by Irit Katriel : -- resolution: rejected -> wont fix ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue12516] imghdr.what should take one argument

Irit Katriel added the comment: imghdr is deprecated as per PEP 594, so there won't be more enhancements to it. -- nosy: +iritkatriel resolution: -> rejected stage: -> resolved status: open -> closed ___ Python tracker

[issue12516] imghdr.what should take one argument

Changes by Claudiu Popa pcmantic...@gmail.com: -- nosy: +Claudiu.Popa versions: +Python 3.5 -Python 3.3 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue12516 ___

[issue12516] imghdr.what should take one argument

Claudiu Popa added the comment: imghdr got a test file in 94813eab5a58. Your patch also needs documentation updates. Besides that, +1 from me. Maybe it would be okay to add a deprecation warning for the second argument? -- ___ Python tracker

[issue12516] imghdr.what should take one argument

SilentGhost ghost@gmail.com added the comment: This seems like a change suitable for 3.3 -- nosy: +SilentGhost versions: +Python 3.3 -Python 3.4 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue12516

[issue12516] imghdr.what should take one argument

New submission from Jeffrey Finkelstein jeffrey.finkelst...@gmail.com: Currently imghdr.what() accepts two parameters. The first is a file or filename and the second is a byte stream. If the second is not None, the first is ignored. This is clunky. It would be simpler to accept just one