On Thu, Jun 21, 2018 at 2:57 PM Jeroen Demeyer wrote:
> On 2018-06-20 17:42, INADA Naoki wrote:
> > I don't have any idea about changing METH_FASTCALL more.
> > If Victor and Serhiy think so, and PyPy maintainers like it too, I want
> > to make it public
> > as soon as possible.
>
> There are
On 2018-06-20 17:42, INADA Naoki wrote:
I don't have any idea about changing METH_FASTCALL more.
If Victor and Serhiy think so, and PyPy maintainers like it too, I want
to make it public
as soon as possible.
There are two different things here:
The first is documenting METH_FASTCALL such that
>
>
>> Even though it's private at 3.7, extension authors can start using it at
>> their risk if we decide METH_FASTCALL is public in 3.8 without any change
>> from 3.7.
>>
>
> People can still wait for 3.8. Waiting 1.5 years for a feature is nothing
> when the software you're talking about is
On Wed, 20 Jun 2018 at 09:49 INADA Naoki wrote:
>
> 2018年6月21日(木) 1:17 Antoine Pitrou :
>
>> On Wed, 20 Jun 2018 18:09:00 +0200
>> Victor Stinner wrote:
>> >
>> > > If we can't at Python 3.7, I think we should do it at 3.8.
>> >
>> > What's the rationale to make it public in 3.7? Can't it wait
Serhiy Storchaka schrieb am 20.06.2018 um 18:56:
> 20.06.18 18:42, INADA Naoki пише:
>> I don't have any idea about changing METH_FASTCALL more.
>> If Victor and Serhiy think so, and PyPy maintainers like it too, I want
>> to make it public as soon as possible.
>
> I don't have objections against
2018年6月21日(木) 1:59 Serhiy Storchaka :
> 20.06.18 18:42, INADA Naoki пише:
> > First of all, thank you Jeroen for writing nice PEPs.
> >
> > When I read PEP 579, I think "6. METH_FASTCALL is private and
> undocumented"
> > should be solved first.
> >
> > I don't have any idea about changing
20.06.18 18:42, INADA Naoki пише:
First of all, thank you Jeroen for writing nice PEPs.
When I read PEP 579, I think "6. METH_FASTCALL is private and undocumented"
should be solved first.
I don't have any idea about changing METH_FASTCALL more.
If Victor and Serhiy think so, and PyPy
2018年6月21日(木) 1:17 Antoine Pitrou :
> On Wed, 20 Jun 2018 18:09:00 +0200
> Victor Stinner wrote:
> >
> > > If we can't at Python 3.7, I think we should do it at 3.8.
> >
> > What's the rationale to make it public in 3.7? Can't it wait for 3.8?
> > The new PEPs target 3.8 anyway, no?
> >
> > IMHO
On Wed, 20 Jun 2018 18:09:00 +0200
Victor Stinner wrote:
>
> > If we can't at Python 3.7, I think we should do it at 3.8.
>
> What's the rationale to make it public in 3.7? Can't it wait for 3.8?
> The new PEPs target 3.8 anyway, no?
>
> IMHO it's too late for 3.7.
Agreed with Victor. Also
Hi,
I chose to make it private because I wasn't sure about the API. I was
right: Serhiy removed keyword arguments from METH_FASTCALL, you now
have to use METH_FASTCALL | METH_KEYWORDS to also pass keyword
arguments ;-) I don't recall if this change was done in 3.7 or also in
3.6. FASTCALL has
Hi, All.
First of all, thank you Jeroen for writing nice PEPs.
When I read PEP 579, I think "6. METH_FASTCALL is private and undocumented"
should be solved first.
I don't have any idea about changing METH_FASTCALL more.
If Victor and Serhiy think so, and PyPy maintainers like it too, I want to
11 matches
Mail list logo
