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.
