Hi Petr,
On 27/03/2019 1:50 pm, Petr Viktorin wrote:
On Sun, Mar 24, 2019 at 4:22 PM Mark Shannon wrote:
Hi Petr,
Regarding PEPs 576 and 580.
Over the new year, I did a thorough analysis of possible approaches to
possible calling conventions for use in the CPython ecosystems and came
up
On Mon, 25 Mar 2019 at 20:34, Cameron Simpson wrote:
> Clearly the above needs to accomodate this, possibly with a fallback
> guess. Is sniffing the end components of __file__ at all sane? ending in
> idlelib/pyshell.py or pyshell.py? Or is that just getting baroque?
>
> I don't think these are
On 2019-03-27 14:50, Petr Viktorin wrote:
The pre-PEP claims speedups of 2% in initial experiments, with
expected overall performance gain of 4% for the standard benchmark
suite. That's pretty big.
I re-did my earlier benchmarks for PEP 580 and these are the results:
On Sun, Mar 24, 2019 at 4:22 PM Mark Shannon wrote:
>
> Hi Petr,
>
> Regarding PEPs 576 and 580.
> Over the new year, I did a thorough analysis of possible approaches to
> possible calling conventions for use in the CPython ecosystems and came
> up with a new PEP.
> The draft can be found here:
>
On Sun, Mar 24, 2019 at 2:03 PM Terry Reedy wrote:
> On 3/24/2019 8:21 AM, Nick Coghlan wrote:
>
> > We'll be announcing those appointments as we go, so I'm happy to
> > report that I will be handling the BDFL-Delegate responsibilities for
> > the following PEPs:
>
> Where do we discuss these?
>
On 25Mar2019 03:52, Terry Reedy wrote:
On 3/25/2019 12:27 AM, Cameron Simpson wrote:
I was thinking about IDLE and its tangled web of circular inports,
but I am now convinced that this change will not affect it. Indeed,
idlelib/pyshell.py already implements idea of the proposal, ending
with
On 3/25/2019 12:27 AM, Cameron Simpson wrote:
On 24Mar2019 23:22, Terry Reedy wrote:
On 3/24/2019 10:01 PM, Terry Reedy wrote:
On 3/24/2019 7:00 PM, Cameron Simpson wrote:
Did you have a specific scenario in mind?
I was thinking about IDLE and its tangled web of circular inports,
but I am
On 3/24/2019 10:01 PM, Terry Reedy wrote:
On 3/24/2019 7:00 PM, Cameron Simpson wrote:
Did you have a specific scenario in mind?
I was thinking about IDLE and its tangled web of circular inports, but I
am now convinced that this change will not affect it. Indeed,
idlelib/pyshell.py
On 3/24/2019 7:00 PM, Cameron Simpson wrote:
On 24Mar2019 17:02, Terry Reedy wrote:
On 3/24/2019 8:21 AM, Nick Coghlan wrote:
* PEP 499: Binding "-m" executed modules under their module name as
well as `__main__`
My brief response: +1 unless there is a good reason not.
There turn out to
On 24Mar2019 17:02, Terry Reedy wrote:
On 3/24/2019 8:21 AM, Nick Coghlan wrote:
* PEP 499: Binding "-m" executed modules under their module name as
well as `__main__`
My brief response: +1 unless there is a good reason not.
There turn out to be some subtle side effects. The test suite
On 3/24/2019 8:21 AM, Nick Coghlan wrote:
We'll be announcing those appointments as we go, so I'm happy to
report that I will be handling the BDFL-Delegate responsibilities for
the following PEPs:
Where do we discuss these?
If a delegate has a provisional view, it might help focus discussion
On 2019-03-24 16:22, Mark Shannon wrote:
The draft can be found here:
https://github.com/markshannon/peps/blob/new-calling-convention/pep-.rst
I think that this is basically a better version of PEP 576. The idea is
the same as PEP 576, but the details are better. Since it's not
On 2019-03-24 16:22, Mark Shannon wrote:
Hi Petr,
Regarding PEPs 576 and 580.
Over the new year, I did a thorough analysis of possible approaches to
possible calling conventions for use in the CPython ecosystems and came
up with a new PEP.
The draft can be found here:
Hi Petr,
Regarding PEPs 576 and 580.
Over the new year, I did a thorough analysis of possible approaches to
possible calling conventions for use in the CPython ecosystems and came
up with a new PEP.
The draft can be found here:
14 matches
Mail list logo