+1 My understanding is this is a documentation change, marking it as deprecated in 3.6.2 and a Misc News entry. No actual code change. Correct?
Mariatta Wijaya On Tue, May 23, 2017 at 8:28 AM, Antoine Pitrou <solip...@pitrou.net> wrote: > On Mon, 22 May 2017 11:17:18 -0700 > Steve Dower <steve.do...@python.org> wrote: > > > > I'd like to propose a highly-accelerated deprecation period for this > > specific feature, starting in CPython 3.6.2 and being "completed" in > > 3.7.0, when we will hopefully move onto a newer libffi. > > > > In general, the "feature" is a misfeature anyway, since calling a native > > function with incorrect arguments is unsupported and a very easy way to > > cause information leakage or code execution vulnerabilities. > > Agreed. > > > Does anyone have any reasons to oppose this? It already has votes from > > another Windows expert and the 3.6/3.7 Release Manager, but we wanted to > > see if anyone has a concern we haven't thought of. > > +1 from me. > > Regards > > Antoine. > > > _______________________________________________ > Python-Dev mailing list > Python-Dev@python.org > https://mail.python.org/mailman/listinfo/python-dev > Unsubscribe: https://mail.python.org/mailman/options/python-dev/ > mariatta.wijaya%40gmail.com >
_______________________________________________ Python-Dev mailing list Python-Dev@python.org https://mail.python.org/mailman/listinfo/python-dev Unsubscribe: https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
