Well then, maybe you can propose some specific set of changes? (I'm about to go on vacation and I'd like to focus on other things for the next two weeks though, so don't count on me too much.) On Sat, Dec 16, 2017 at 3:49 PM, Antoine Pitrou <solipsis at pitrou.net> wrote: > On Sat, 16 Dec 2017 11:42:15 -0800 > Guido van Rossum <guido at python.org> wrote: > > > > If it's only a warning, I worry that if we stop checking the flag bits it > > can cause wild pointer following. This sounds like it would be a > potential > > security issue (load a module, ignore the warning, try to use a certain > API > > on a class it defines, boom). Also, could there still be 3rd party > modules > > out there that haven't been recompiled in a really long time and use some > > older backwards compatible module initialization API? (I guess we could > > stop supporting that and let them fail hard.) > > As far as I can tell, all the legacy APIs were removed when PEP 3121 > was implemented (Python 3 allowed us to do a clean break here). > > Regards > > Antoine. > _______________________________________________ > Python-Dev mailing list > Python-Dev at python.org > https://mail.python.org/mailman/listinfo/python-dev > Unsubscribe: https://mail.python.org/mailman/options/python-dev/ > guido%40python.org > -- --Guido van Rossum (python.org/~guido) -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://mail.python.org/pipermail/python-dev/attachments/20171216/6866905e/attachment.html>
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4