Re: [Python-Dev] [PEP 576/580] Comparing PEP 576 and 580
On 2018-07-31 11:12, INADA Naoki wrote:
Any PEP won't be accepted in few month, because we don't have flow to accept PEPs for now.
Is that certain? I haven't been following the process discussions, so I'm just asking the question. For example, given that you are already looking at PEP 580, would it be possible for you to handle PEP 580 as official BDFL-Delegate (even if there is no BDFL)?
So it's worthless that waiting PEP accepted before start PoC.
First of all, it's too early for a proof-of-concept of native C calling. We first have to design the theory before we can start implementing anything. But even if we could start to write a proof of concept, I would really prefer doing that on top of PEP 580. There are two reasons for this: 1. If PEP 580 is rejected, I very much doubt that the native C calling protocol will be accepted. 2. I would be good to use PEP 580 as a framework for the implementation. Otherwise we have to implement it twice: once before PEP 580 with the proof-of-concept and then again after PEP 580 with the "real" implementation. Jeroen.
On 8/1/2018 6:17 AM, Jeroen Demeyer wrote:
On 2018-07-31 11:12, INADA Naoki wrote:
Any PEP won't be accepted in few month, because we don't have flow to accept PEPs for now.
Is that certain? I haven't been following the process discussions, so I'm just asking the question. For example, given that you are already looking at PEP 580, would it be possible for you to handle PEP 580 as official BDFL-Delegate (even if there is no BDFL)?
I think this would be a reasonable thing to discuss either here or on the committers list or both. -- Terry Jan Reedy
On Wed, 1 Aug 2018 at 07:47 Terry Reedy <tjreedy@udel.edu> wrote:
On 8/1/2018 6:17 AM, Jeroen Demeyer wrote:
On 2018-07-31 11:12, INADA Naoki wrote:
Any PEP won't be accepted in few month, because we don't have flow to accept PEPs for now.
Is that certain? I haven't been following the process discussions, so I'm just asking the question. For example, given that you are already looking at PEP 580, would it be possible for you to handle PEP 580 as official BDFL-Delegate (even if there is no BDFL)?
I think this would be a reasonable thing to discuss either here or on the committers list or both.
If there was an absolute certainty of who the BDFL delegate would be then we might be able to not wait, but without that I don't know if enough core devs will feel comfortable choosing one right now.
On Wed, 1 Aug 2018 09:05:52 -0700 Brett Cannon <brett@python.org> wrote:
On Wed, 1 Aug 2018 at 07:47 Terry Reedy <tjreedy@udel.edu> wrote:
On 8/1/2018 6:17 AM, Jeroen Demeyer wrote:
On 2018-07-31 11:12, INADA Naoki wrote:
Any PEP won't be accepted in few month, because we don't have flow to accept PEPs for now.
Is that certain? I haven't been following the process discussions, so I'm just asking the question. For example, given that you are already looking at PEP 580, would it be possible for you to handle PEP 580 as official BDFL-Delegate (even if there is no BDFL)?
I think this would be a reasonable thing to discuss either here or on the committers list or both.
If there was an absolute certainty of who the BDFL delegate would be then we might be able to not wait, but without that I don't know if enough core devs will feel comfortable choosing one right now.
We could proceed by consensus: the PEP author publicly proposes a PEP delegate, and if no core developer opposes, that person is officially accepted as delegate. Often PEP authors have a pretty good idea of who can be a delegate for a PEP. This is especially true on specialized topics which only a couple core devs are interested in discussing actively. Regards Antoine.
Antoine Pitrou writes:
We could proceed by consensus: the PEP author publicly proposes a PEP delegate, and if no core developer opposes, that person is officially accepted as delegate.
I think this is too decentralized. I think there should be enthusiasm for the delegate, say two "seconds" (with discussion of why they think the delegate is appropriate) besides the PEP proponent(s).
Often PEP authors have a pretty good idea of who can be a delegate for a PEP. This is especially true on specialized topics which only a couple core devs are interested in discussing actively.
I agree that this is an important point. I think you (disclaimer: I'm a social scientist, but not a committer) should be careful that delegates be broadly respected, and where possible have interests in other areas of Python development besides the one they're delegate for.
participants (5)
-
Antoine Pitrou -
Brett Cannon -
Jeroen Demeyer -
Stephen J. Turnbull -
Terry Reedy