<div dir="ltr"><br><br><div class="gmail_quote"><div dir="ltr">On Thu, 3 Mar 2016 at 06:26 Victor Stinner <<a href="mailto:victor.stinner@gmail.com">victor.stinner@gmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">2016-03-03 13:40 GMT+01:00 Nick Coghlan <<a href="mailto:ncoghlan@gmail.com" target="_blank">ncoghlan@gmail.com</a>>:<br>
> Adding cffi (including its dependencies) to the standard library was<br>
> approved-in-principle a couple of years ago, and I believe the one<br>
> technical issue with a lack of support for ahead-of-time compilation<br>
> of the extension module has since been addressed, (...)<br>
<br>
Hum, I also recall vaguely a discussion about pycparser dependency of cffi.<br></blockquote><div><br></div><div>Yep, the issue was pycparser which depended on PLY. At the time Alex Gaynor said he and David Beazley were planning to fix a bunch of things in PLY and that it would be best to hold off until PLY was cleaned up enough to go into the stdlib. That obviously didn't happen. :) </div></div></div>