[issue30206] data parameter for binascii.b2a_base64 is not positional-only

2017-04-30 Thread Xiang Zhang
Changes by Xiang Zhang : -- resolution: -> fixed stage: -> resolved status: open -> closed versions: -Python 3.6 ___ Python tracker

[issue30206] data parameter for binascii.b2a_base64 is not positional-only

2017-04-29 Thread STINNER Victor
STINNER Victor added the comment: Right, my API change was unintentional. -- ___ Python tracker ___ ___

[issue30206] data parameter for binascii.b2a_base64 is not positional-only

2017-04-29 Thread Xiang Zhang
Changes by Xiang Zhang : -- pull_requests: +1464 ___ Python tracker ___ ___

[issue30206] data parameter for binascii.b2a_base64 is not positional-only

2017-04-29 Thread Serhiy Storchaka
Serhiy Storchaka added the comment: Because this change looks unintentional (no one of reviewers even noticed it) and was not documented, I think it is better to make the data parameter positional-only in 3.7. The chance of breaking a user code is very low, and even if this breaks some code,

[issue30206] data parameter for binascii.b2a_base64 is not positional-only

2017-04-29 Thread Xiang Zhang
New submission from Xiang Zhang: Before functions in binascii having *data* parameter all accept it as positionaly-only. But after #25357, binascii.b2a_base64 changed it to accept keyword argument also but it looks unintentional. -- components: Library (Lib) messages: 292585 nosy: