<div dir="ltr">PEP has first draft done. Giving Koos and Stephen to comment on it before I post it (I'll give them until Monday).<br>
</div><span>
</span><br><div class="gmail_quote"><div dir="ltr">On Fri, Apr 29, 2016, 15:46 Larry Hastings <<a href="mailto:larry@hastings.org">larry@hastings.org</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div bgcolor="#FFFFFF" text="#000000">
<br>
<br>
This month there were over 350 emails in python-dev with the word
"pathlib" in the title. Yet, despite this massive online debate,
nobody volunteered to present about pathlib at the language summit.<br>
<br>
Based on Jake Edge's summary of the conversation from LWN.net we've
boiled down the debate to these six basic positions.<br>
<ol>
<li>We should keep pathlib in the standard library.</li>
<li>We should remove pathlib from the standard library.</li>
<li>The Path object should inherit from str.</li>
<li>The Path object shouldn't inherit from str; it should continue
to be its own unrelated type.</li>
<li>We need a new "fspath" protocol.</li>
<li>We don't need an "fspath" protocol.<br>
</li>
</ol>
We'd like some volunteers to speak on each of these positions.
Speakers should plan for a maximum of 2 minutes per position. After
the six positions are presented at the summit we'll open the floor
for debate.<br>
<br>
You're encouraged to volunteer to present more than one! For
example, if you think we need the protocol, you're probably pro-
keeping the object and anti-inherit from str. (Brett, we're looking
at <i>you.)</i><br>
<br>
Please note, volunteers should be people who are *already invited to
the summit*. We can't invite additional people just for this--and
we're basically full anyway.<br>
<br>
<br>
Thanks,<br>
<br>
<br>
[BL]arry<br>
<br>
p.s. In case you're thinking "That's not fair! I can't make it to
the summit, I don't want to get left out of the decision!" We don't
propose to make any binding decisions at the summit--unless the BDFL
makes pronouncements there of course. This discussion is intended
as a quick face-to-face debate on the topic, both to inform the
delegates at the summit, and to possibly find a rough consensus.<br>
<br>
p.p.s. If we mischaracterized the debate, and the positions above
aren't a good distillation, by all means follow up and make a
counter-proposal! We're listening.<br>
</div>
_______________________________________________<br>
python-committers mailing list<br>
<a href="mailto:python-committers@python.org" target="_blank">python-committers@python.org</a><br>
<a href="https://mail.python.org/mailman/listinfo/python-committers" rel="noreferrer" target="_blank">https://mail.python.org/mailman/listinfo/python-committers</a><br>
Code of Conduct: <a href="https://www.python.org/psf/codeofconduct/" rel="noreferrer" target="_blank">https://www.python.org/psf/codeofconduct/</a></blockquote></div>