2016 Python Language Summit: Can we get volunteers to talk about pathlib?
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.
Based on Jake Edge's summary of the conversation from LWN.net we've boiled down the debate to these six basic positions.
- We should keep pathlib in the standard library.
- We should remove pathlib from the standard library.
- The Path object should inherit from str.
- The Path object shouldn't inherit from str; it should continue to be its own unrelated type.
- We need a new "fspath" protocol.
- We don't need an "fspath" protocol.
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.
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 /you.)/
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.
Thanks,
[BL]arry
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.
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.
The primary debate should be about fspath or not. Inheriting from str is off the table while I'm BDFL. Removing pathlib from the stdlib would only be on the table if we can't reach agreement on fspath.
On Fri, Apr 29, 2016 at 3:46 PM, Larry Hastings larry@hastings.org wrote:
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.
Based on Jake Edge's summary of the conversation from LWN.net we've boiled down the debate to these six basic positions.
- We should keep pathlib in the standard library.
- We should remove pathlib from the standard library.
- The Path object should inherit from str.
- The Path object shouldn't inherit from str; it should continue to be its own unrelated type.
- We need a new "fspath" protocol.
- We don't need an "fspath" protocol.
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.
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 *you.)*
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.
Thanks,
[BL]arry
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.
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.
python-committers mailing list python-committers@python.org https://mail.python.org/mailman/listinfo/python-committers Code of Conduct: https://www.python.org/psf/codeofconduct/
-- --Guido van Rossum (python.org/~guido)
On 04/29/2016 03:53 PM, Guido van Rossum wrote:
The primary debate should be about fspath or not. Inheriting from str is off the table while I'm BDFL. Removing pathlib from the stdlib would only be on the table if we can't reach agreement on fspath.
WFM. Are there competing proposals for how fspath should work, or is there just one proposal and the debate is whether or not to add it?
//arry/
Wait for Brett.
On Friday, April 29, 2016, Larry Hastings larry@hastings.org wrote:
On 04/29/2016 03:53 PM, Guido van Rossum wrote:
The primary debate should be about fspath or not. Inheriting from str is off the table while I'm BDFL. Removing pathlib from the stdlib would only be on the table if we can't reach agreement on fspath.
WFM. Are there competing proposals for how fspath should work, or is there just one proposal and the debate is whether or not to add it?
*/arry*
-- --Guido (mobile)
PEP has first draft done. Giving Koos and Stephen to comment on it before I post it (I'll give them until Monday).
On Fri, Apr 29, 2016, 15:46 Larry Hastings larry@hastings.org wrote:
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.
Based on Jake Edge's summary of the conversation from LWN.net we've boiled down the debate to these six basic positions.
- We should keep pathlib in the standard library.
- We should remove pathlib from the standard library.
- The Path object should inherit from str.
- The Path object shouldn't inherit from str; it should continue to be its own unrelated type.
- We need a new "fspath" protocol.
- We don't need an "fspath" protocol.
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.
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 *you.)*
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.
Thanks,
[BL]arry
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.
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.
python-committers mailing list python-committers@python.org https://mail.python.org/mailman/listinfo/python-committers Code of Conduct: https://www.python.org/psf/codeofconduct/
On Fri, Apr 29, 2016 at 10:55:14PM +0000, Brett Cannon wrote:
PEP has first draft done. Giving Koos and Stephen to comment on it before I post it (I'll give them until Monday).
Brett, thanks for this! I've looked at the size of the threads on pathlib and my brain started making "whib whib whib" noises and tried to hide, so I really appreciate the work you're doing.
-- Steve
On Sat, Apr 30, 2016, 20:26 Steven D'Aprano steve@pearwood.info wrote:
On Fri, Apr 29, 2016 at 10:55:14PM +0000, Brett Cannon wrote:
PEP has first draft done. Giving Koos and Stephen to comment on it before I post it (I'll give them until Monday).
Brett, thanks for this! I've looked at the size of the threads on pathlib and my brain started making "whib whib whib" noises and tried to hide, so I really appreciate the work you're doing.
Welcome! And the PEP will be coming Friday as it's holidays in Finland and so Koos won't get a stab at it until later in the week.
-brett
-- Steve
python-committers mailing list python-committers@python.org https://mail.python.org/mailman/listinfo/python-committers Code of Conduct: https://www.python.org/psf/codeofconduct/
participants (4)
-
Brett Cannon -
Guido van Rossum -
Larry Hastings -
Steven D'Aprano