On Sat, 28 Sep 2019 at 12:56, Victor Stinner wrote:
>
> Hi,
>
> I dislike having to do that, but I had to make a last minute change in
> my PEP 587 "Python Initialization Configuration" to allow to modify
> the structure in the future without breaking the backward
> compatibility. I added a "struc
On Tue., 24 Sep. 2019, 10:29 am Nathaniel Smith, wrote:
> On Mon, Sep 23, 2019 at 1:30 PM Vinay Sajip via Python-Dev
> wrote:
> >
> > OK - but that's just one I picked at random. There are others like it -
> what would be the process for deciding which ones need to be made private
> and moved? S
Short course: a replacement for malloc for use in contexts that can't
"move memory" after an address is passed out, but want/need the
benefits of compactification anyway.
Key idea: if the allocator dedicates each OS page to requests of a
specific class, then consider two pages devoted to the sam
Here's a video about memory fragmentation and compaction that you might
find interesting:
"Compacting the Uncompactable" by Bobby Powers
https://www.youtube.com/watch?v=c1UBJbfR-H0
___
Python-Dev mailing list -- python-dev@python.org
To unsubscribe sen
2019-09-28 Update: we are still awaiting resolution of some release blockers
but I am hopeful we will be unblocked very shortly. I have rescheduled the
cutoff for 3.7.5rc1 for this coming Monday (2019-09-30) and, assuming no
showstopper problems are identified in the release candidate, 3.7.5 fi
