Re: [Python-Dev] PEP 454 - tracemalloc - accepted

2013-11-23 Thread Victor Stinner
Hi, 2013/11/21 Charles-François Natali : > I'm happy to officially accept PEP 454 aka tracemalloc. > The API has substantially improved over the past weeks, and is now > both easy to use and suitable as a fundation for high-level tools for > memory-profiling. I pushed the implementation of he PEP

Re: [Python-Dev] PEP 454 - tracemalloc - accepted

2013-11-22 Thread Stefan Krah
Victor Stinner wrote: > 2013/11/21 Nick Coghlan : > > Huzzah! Thanks to you both for getting this ready for inclusion :) > > I now hope that someone will use it :-) Congratulations! I hope pyfailmalloc can go into 3.4, too. Stefan Krah ___ Python

Re: [Python-Dev] PEP 454 - tracemalloc - accepted

2013-11-21 Thread Eric Snow
On Thu, Nov 21, 2013 at 4:17 PM, Nick Coghlan wrote: > Skipping saving _source under -OO would probably be a good thing, but > otherwise it's a public API with the usual backwards compatibility > guarantees. One alternative might be to make it a property that re-generates the source (you just nee

Re: [Python-Dev] PEP 454 - tracemalloc - accepted

2013-11-21 Thread Antoine Pitrou
On Fri, 22 Nov 2013 09:17:14 +1000 Nick Coghlan wrote: > > Skipping saving _source under -OO would probably be a good thing, but > otherwise it's a public API with the usual backwards compatibility > guarantees. I think skipping saving _source under -OO should be a bugfix. It's terribly weird an

Re: [Python-Dev] PEP 454 - tracemalloc - accepted

2013-11-21 Thread Nick Coghlan
On 22 Nov 2013 09:02, "Victor Stinner" wrote: > > 2013/11/21 Nick Coghlan : > > Huzzah! Thanks to you both for getting this ready for inclusion :) > > I now hope that someone will use it :-) > > > By the way, collections.namedtuple has a private _source attribute. > This attributes uses something

Re: [Python-Dev] PEP 454 - tracemalloc - accepted

2013-11-21 Thread Victor Stinner
2013/11/21 Nick Coghlan : > Huzzah! Thanks to you both for getting this ready for inclusion :) I now hope that someone will use it :-) By the way, collections.namedtuple has a private _source attribute. This attributes uses something like 676.2 kB in the Python test suite, it the 5th biggest use

Re: [Python-Dev] PEP 454 - tracemalloc - accepted

2013-11-21 Thread Nick Coghlan
On 22 Nov 2013 07:43, "Charles-François Natali" wrote: > > Hi, > > I'm happy to officially accept PEP 454 aka tracemalloc. > The API has substantially improved over the past weeks, and is now > both easy to use and suitable as a fundation for high-level tools for > memory-profiling. > > Thanks to

Re: [Python-Dev] PEP 454 - tracemalloc - accepted

2013-11-21 Thread Victor Stinner
2013/11/21 Charles-François Natali : > I'm happy to officially accept PEP 454 aka tracemalloc. > The API has substantially improved over the past weeks, and is now > both easy to use and suitable as a fundation for high-level tools for > memory-profiling. > > Thanks to Victor for his work! Thanks

[Python-Dev] PEP 454 - tracemalloc - accepted

2013-11-21 Thread Charles-François Natali
Hi, I'm happy to officially accept PEP 454 aka tracemalloc. The API has substantially improved over the past weeks, and is now both easy to use and suitable as a fundation for high-level tools for memory-profiling. Thanks to Victor for his work! Charles-François