> It would not help the quadratic behaviour - and is orthogonal to your
> proposal -
> , but at least avoid calling the GC too often when lots of small objects are
> allocated (as opposed to lots of large objects).
I'd like to see in an experiment whether this is really true. Current GC
only tak
Michael Abbott wrote:
Please CC me in any replies: I am quite literally unable to cope with the
volume of traffic that a subscription to python-dev will give me.
You can read python-dev (and 1000s of other mail lists, with a
newsreader, like I do, for the same reason, via the free list to n
On Mon, 23 Jun 2008, Aahz wrote:
> Then don't bother posting code to the list. Please post a patch; up to
> you whether you send a notice to python-dev.
Very well. Issue 3180 created. I hope I'm doing it right...
___
Python-Dev mailing list
Python-D
On Mon, Jun 23, 2008, Michael Abbott wrote:
>
> Please CC me in any replies: I am quite literally unable to cope with the
> volume of traffic that a subscription to python-dev will give me.
Then don't bother posting code to the list. Please post a patch; up to
you whether you send a notice to py
Martin v. Löwis v.loewis.de> writes:
> Currently, only youngest collections are triggered by allocation
> rate; middle and old are triggered by frequency of youngest collection.
> So would you now specify that the youngest collection should occur
> if-and-only-if a new arena is allocated? Or disco
I have a problem with the PyOS_InputHook() API as implemented by
Modules/readline.c: there is no way to communicate any interruption seen
while waiting at the keyboard back to the process actually reading the
line.
I have solved this in my own application by creating a new module which
reimple
