ACTIVITY SUMMARY (2020-05-29 - 2020-06-05)
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:
open7444 (-43)
closed 45180 (+100)
total 52624 (+57)
Open issues w
On Wed, Jun 3, 2020 at 7:12 AM Mark Shannon wrote:
> The size of the C API, as measured by `git grep PyAPI_FUNC | wc -l` has
> been steadily increasing over the last few releases.
>
> 3.5 1237
> 3.6 1304
> 3.7 1408
> 3.8 1478
> 3.9 1518
>
>
> For reference the 2.7 branch has "o
On 6/5/2020 11:11 AM, Edwin Zimmerman wrote:
Advantages of the one-to-one model
--
1. It's less bug prone. It is much easier to reason about code working
in a single address space. Most code assumes
I'm curious where reasoning about address spaces comes into writ
On 06/05/2020 07:32 AM, Mark Shannon wrote:
3. It can be implemented on top of the multiprocessing module, for testing. A
more efficient implementation can be developed once sub-interpreters prove
useful.
Isn't part of the impetus for in-process sub-interpreters the
Python-embedded-in-langu
On Fri, May 29, 2020 at 12:16 PM Python tracker wrote:
> ACTIVITY SUMMARY (2020-05-22 - 2020-05-29)
> 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:
> open
> Hi,
>
> There have been a lot of changes both to the C API and to internal
> implementations to allow multiple interpreters in a single O/S process.
>
> These changes cause backwards compatibility changes, have a negative
> performance impact, and cause a lot of churn.
>
> While I'm in favour
Hi,
There have been a lot of changes both to the C API and to internal
implementations to allow multiple interpreters in a single O/S process.
These changes cause backwards compatibility changes, have a negative
performance impact, and cause a lot of churn.
While I'm in favour of PEP 554, o
On 03/06/2020 8:49 pm, Pablo Galindo Salgado wrote:
Just some comments on the GC stuff as I added them myself.
Shouldn't GC track *all* objects?
No, extension types need to opt-in to the garbage collector and if so,
implement the interface.
When you say "GC" I think you mean the backup cy
