On Fri, Nov 29, 2019 at 9:48 PM Abdur-Rahmaan Janhangeer <arj.pyt...@gmail.com> wrote: > > One of them can maybe be deprectated > > json.load(<string here>) > > for file: > > json.load(file=<file obj>) >
Deprecation is not a solution. You're still going to have stuff out there using the old name (Stack Overflow posts, blogs, articles, books, etc etc etc etc), and people *will* have to learn the meaning of both. Additionally, churn like this - renaming things for no reason other than "the new name is somehow better" - tends to create the sense that the language is constantly in flux, and that today's code is going to be broken tomorrow. Imagine a Stack Overflow answer that has to be edited to say "For Python versions up to 3.8, use json.loads; for versions 3.9 and up, use json.load_string", and then if it uses a couple of other APIs that have been renamed, it needs to multiply that out exponentially... no thanks. I get enough of that from React.js. -1 on renaming. -1 on deprecating. -1 on creating an unnecessary alias. ChrisA _______________________________________________ Python-ideas mailing list -- python-ideas@python.org To unsubscribe send an email to python-ideas-le...@python.org https://mail.python.org/mailman3/lists/python-ideas.python.org/ Message archived at https://mail.python.org/archives/list/python-ideas@python.org/message/DKH4DKBKH7JRM4SC7VZSDVBTL3YW6TQO/ Code of Conduct: http://python.org/psf/codeofconduct/
