On 2018-11-16, Nathaniel Smith wrote:
> [..] it seems like you should investigate (a) whether you can make
> Py_LIMITED_API *be* that API, instead of having two different
> ifdefs
That might be a good idea. One problem is that we might like to
make backwards incompatible changes to
On Fri, Nov 16, 2018 at 3:12 PM Neil Schemenauer wrote:
> Also, the extension module should not take a big performance hit.
> So, you can't change all APIs that were macros into non-inlined
> functions. People are not going to accept that and rightly so.
> However, it could be that we introduce
On 2018-11-16, Brett Cannon wrote:
> I think part of the challenge here (and I believe it has been
> brought up elsewhere) is no one knows what kind of API is
> necessary for some faster VM other than PyPy.
I think we have some pretty good ideas as to what are the
problematic parts of the current
On Fri, 16 Nov 2018 at 17:49, Brett Cannon wrote:
> And Just to be clear, I totally support coming up with a totally
> stripped-down C API as I have outlined above as that shouldn't be
> controversial for any VM that wants to have a C-level API.
If a stripped down API like this is intended as
Brett:
> But otherwise I think we are making assumptions here. For me, unless we are
> trying to trim the C API down to just what is syntactically supported in
> Python and in such a way that it hides all C-level details I feel like we are
> guessing at what's best for other VMs, both today and
On Wed, 14 Nov 2018 at 16:09, Gregory P. Smith wrote:
> It seems like the discussion so far is:
>>
>> Victor: "I know people when people hear 'new API' they get scared and
>> think we're going to do a Python-3-like breaking transition, but don't
>> worry, we're never going to do that."
>>
On Sun, 4 Nov 2018 at 14:49, Steven D'Aprano wrote:
> On Sun, Nov 04, 2018 at 05:05:07PM +0100, Stephane Wirtel wrote:
>
> > >If I am making doc patches, shouldn't I be doing that *before* I
> > >submit the PR? How else will I know that my changes haven't broken the
> > >docs?
> >
> > You can
ACTIVITY SUMMARY (2018-11-09 - 2018-11-16)
Python tracker at https://bugs.python.org/
To view or respond to any of the issues listed below, click on the issue.
Do NOT respond to this message.
Issues counts and deltas:
open6863 (+29)
closed 40154 (+36)
total 47017 (+65)
Open issues
