Message177647
| Author |
skrah |
| Recipients |
Trundle, benjamin.peterson, dmalcolm, jcea, meador.inge, ncoghlan, neologix, pitrou, python-dev, skrah, techtonik, tim.peters, vstinner |
| Date |
2012年12月17日.13:08:19 |
| SpamBayes Score |
-1.0 |
| Marked as misclassified |
Yes |
| Message-id |
<20121217130821.GA31529@sleipnir.bytereef.org> |
| In-reply-to |
<1355732128.3319.1.camel@localhost.localdomain> |
| Content |
Antoine Pitrou <report@bugs.python.org> wrote:
> Hmm, interesting. When built --without-pymalloc, we could make
> sys.getallocatedblocks() always return 0, or we could not define it all
> (which would make like a bit harder for regrtest). What do you think?
Given the name getallocatedblocks(), it would seem reasonable to return
0 in this case and document the fact. I don't think many people use
--without-pymalloc anyhow.
I'm using the option only for Valgrind testing, that's how I found
the build error. |
|
History
|
|---|
| Date |
User |
Action |
Args |
| 2012年12月17日 13:08:19 | skrah | set | recipients:
+ skrah, tim.peters, jcea, ncoghlan, pitrou, vstinner, techtonik, benjamin.peterson, Trundle, dmalcolm, meador.inge, neologix, python-dev |
| 2012年12月17日 13:08:19 | skrah | link | issue13390 messages |
| 2012年12月17日 13:08:19 | skrah | create |
|