Showing content from http://mail.python.org/pipermail/python-dev/attachments/20140410/bd250d3a/attachment.html below:
<div dir="ltr">On Thu, Apr 10, 2014 at 12:30 PM, Antoine Pitrou <span dir="ltr"><<a href="mailto:solipsis@pitrou.net" target="_blank">solipsis@pitrou.net</a>></span> wrote:<br><div class="gmail_extra"><div class="gmail_quote">
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Le 10/04/2014 20:58, Guido van Rossum a écrit :<div class=""><br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
Huh, I totally missed this (and I just gave Kushal a confused answer<br>
when he asked me about it in person). Can someone please post here what<br>
the plan is exactly? I don't want to press for a PEP, but I would at<br>
least like to understand the plan for CFFI and PLY before it is<br>
executed, since I have never had to use either one, and it feels like<br>
each of these will require some commitment to maintenance once they are<br>
in, in addition to cleanup before they go in.<br>
</blockquote>
<br></div>
FWIW, I do hope there would be a PEP before including CFFI... Actually I don't understand what would justify an exemption</blockquote><div><br></div><div>There's absolutely no reason to exempt CFFI, IMHO. On the contrary -- the dependence on other 3rd party modules (PLY and pycparesr), and the related dilemma of whether to expose each/both as stdlib modules or hide as internal implementation details -- makes a PEP even more important here.<br>
<br></div><div>Eli<br></div></div></div></div>
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