Re: [Python-Dev] Discussion related to memory leaks requested

On 15 January 2016 at 05:25, Matthew Paulson wrote: > Hi All: > > I've created a simple program to make sure I wasn't lying to you all ;-> > > Here it is: > > for (ii = 0; ii < 100; ii++) > { > Py_Initialize(); > > if ((code = Py_CompileString(p, "foo", Py_file_inp

Re: [Python-Dev] PEP 509

Terry Reedy writes: > While I understand the rationale against __version__, it strikes me as a > better description of what it is, and easier on the brain than > __cache_token__. Maybe there is something even better, such as > __seqnum__. Or __generation__, as in "generational garbage col

Re: [Python-Dev] Discussion related to memory leaks requested

Hi All: I've created a simple program to make sure I wasn't lying to you all ;-> Here it is: for (ii = 0; ii < 100; ii++) { Py_Initialize(); if ((code = Py_CompileString(p, "foo", Py_file_input)) == NULL) printf("PyRun_SimpleString() failed\n");

Re: [Python-Dev] PEP 506 secrets module

I think the discussion petered out and nobody asked me to approve it yet (or I lost track of it). I'm almost happy to approve it in the current state. My only quibble is with some naming -- I'm not sure that a super-generic name like 'equal' is better than the original ('compare_digest'), and I wou

Re: [Python-Dev] PEP 506 secrets module

I noticed an article about default rand usage in Go from the Go Weekly newsletter and it reminded me about PEP 506 and the secrets module. That's when I noticed that the PEP is still open. What is the current blocker on the P

Re: [Python-Dev] Discussion related to memory leaks requested

Petr Viktorin gmail.com> writes: > The hairy details on why the global variables haven't yet gone away are > on import-sig [0]. Nick suggested a workable solution there that I > really need to go back to and implement. > > [0] https://mail.python.org/pipermail/import-sig/2015-July/001022.html I

Re: [Python-Dev] Discussion related to memory leaks requested

On 01/14/2016 10:45 AM, Nick Coghlan wrote: > On 14 January 2016 at 15:42, Benjamin Peterson wrote: >> This is a "well-known" issue. Parts of the interpreter (and especially, >> extension modules) cheerfully stash objects in global variables with no >> way to clean them up. Fixing this is a large

Re: [Python-Dev] Discussion related to memory leaks requested

On 14 January 2016 at 15:42, Benjamin Peterson wrote: > This is a "well-known" issue. Parts of the interpreter (and especially, > extension modules) cheerfully stash objects in global variables with no > way to clean them up. Fixing this is a large project, which probably > involves implementing P