On 20 Nov 2013 10:48, "Victor Stinner" wrote:
>
> 2013/11/20 Guido van Rossum :
> > I'm guessing CF is the PEP-BDFL?
>
> Yes, you delegated him this PEP :-)
>
> > So he should approve it (the period for
> > final comments is long over) and then you can merge.
>
> I'm asking if the code *must* be m
2013/11/20 Guido van Rossum :
> I'm guessing CF is the PEP-BDFL?
Yes, you delegated him this PEP :-)
> So he should approve it (the period for
> final comments is long over) and then you can merge.
I'm asking if the code *must* be merged before the beta1, or if it can
be merged later. Charles-Fr
I'm guessing CF is the PEP-BDFL? So he should approve it (the period for
final comments is long over) and then you can merge.
On Tue, Nov 19, 2013 at 4:09 PM, Victor Stinner wrote:
> 2013/11/11 Charles-François Natali :
> > After several exchanges with Victor, PEP 454 has reached a status
> > wh
2013/11/11 Charles-François Natali :
> After several exchanges with Victor, PEP 454 has reached a status
> which I consider ready for pronuncement [1]: so if you have any last
> minute comment, now is the time!
So, what's going on? The deadline is Saturday, in 5 days.
If the PEP is accepted (I ho
2013/11/11 Charles-François Natali :
> After several exchanges with Victor, PEP 454 has reached a status
> which I consider ready for pronuncement [1]: so if you have any last
> minute comment, now is the time!
Because the PEP has a long history, 49 mercurial revisions between
september and novemb
I'm happy with the latest PEP because it is minimal but core features are
still present:
- get the traceback where an object was allocated,
- get traces of memory blocks,
- compute statistics on memory usage per line, file or traceback,
- compute differences between two snapshots.
We now have an
Hi,
After several exchanges with Victor, PEP 454 has reached a status
which I consider ready for pronuncement [1]: so if you have any last
minute comment, now is the time!
Cheers,
cf
[1] http://www.python.org/dev/peps/pep-0454/
___
Python-Dev mailing
