PEP 572 at the Language Summit next week
Sorry, I choose to reply to python-committers rather than python-dev because I have been annoyed by the PEP 572 traffic on python-dev.
2018-04-29 22:45 GMT+02:00 Larry Hastings <larry@hastings.org>:
In case it helps, we're planning on presentations on / a discussion of PEP 572 at the 2018 Python Language Summit next Wednesday. (I'm assuming it won't be pronounced upon before then--after all, what's the rush?) Naturally the discussion isn't going to escape the room until it gets reported on by Jake Edge, but delegates at the Summit will hopefully emerge well-informed and comfortable with the result of the discussion.
Who is going to lead this discussion? Will we have at least one developer in favor of the PEP to give a summary of the advantages? I would like to make sure that we can get a fair summary of the past PEP discussion.
I'm not worried for the "dislike" part which may be correctly represented :-D
Note: I just got a notice of a strike at Air France next Tuesday, the day I'm flighting to the US, and my 3rd and last flight of this trip is cancelled. Oh oh.
Victor
It looks like I am going to try and present a balanced summary and then open the floor for discussion. I also want to use the opportunity to start brainstorming about a better way to make decisions.
On Fri, May 4, 2018 at 9:10 AM, Victor Stinner <vstinner@redhat.com> wrote:
Sorry, I choose to reply to python-committers rather than python-dev because I have been annoyed by the PEP 572 traffic on python-dev.
2018-04-29 22:45 GMT+02:00 Larry Hastings <larry@hastings.org>:
In case it helps, we're planning on presentations on / a discussion of PEP 572 at the 2018 Python Language Summit next Wednesday. (I'm assuming it won't be pronounced upon before then--after all, what's the rush?) Naturally the discussion isn't going to escape the room until it gets reported on by Jake Edge, but delegates at the Summit will hopefully emerge well-informed and comfortable with the result of the discussion.
Who is going to lead this discussion? Will we have at least one developer in favor of the PEP to give a summary of the advantages? I would like to make sure that we can get a fair summary of the past PEP discussion.
I'm not worried for the "dislike" part which may be correctly represented :-D
Note: I just got a notice of a strike at Air France next Tuesday, the day I'm flighting to the US, and my 3rd and last flight of this trip is cancelled. Oh oh.
Victor
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)
2018-05-04 19:04 GMT+02:00 Guido van Rossum <guido@python.org>:
It looks like I am going to try and present a balanced summary and then open the floor for discussion.
Oh ok, thanks!
I'm not sure that the discussion on python-dev was really efficient (I didn't follow the discussion on python-ideas). It seems like many people said the same thing. I'm not sure that arguments of the supporters of the PEP have been heard. Likely lost in the high number of emails...
Victor
[Victor Stinner <vstinner@redhat.com>]
I'm not sure that the discussion on python-dev was really efficient (I didn't follow the discussion on python-ideas). It seems like many people said the same thing.
Only hundreds of times ;-)
I'm not sure that arguments of the supporters of the PEP have been heard. Likely lost in the high number of emails...
It's really the PEP's job to lay out the pros and cons - you shouldn't have to read emails at all for that, unless you want to follow the development in real time. I think moving the PEP from python-ideas to python-dev was premature, because even among proponents there wasn't yet consensus that the then-current state of the PEP was sufficiently focused.
The simpler the PEP has gotten, the more I've warmed to it. My current +1 isn't really about the PEP as it stands, but about what I _assume_ Guido will be talking about (plain-name "binding expressions" alone, and not also, e.g., about changing some corner case scope behaviors, but also about tightening the language spec with respect to guaranteeing a specific order-of-operation (OOO) in some currently fuzzy cases - although, to be fair, both scope behaviors and OOO guarantees are issues on their own quite independent of this PEP).
And, frankly, everyone else should be +1 too on whatever it is Guido is privately thinking ;-)
participants (4)
-
Guido van Rossum -
Steve Dower -
Tim Peters -
Victor Stinner