This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author pitrou
Recipients Mark.Shannon, ag6502, amaury.forgeotdarc, benjamin.peterson, francismb, ggenellina, ncoghlan, pitrou, serhiy.storchaka, terry.reedy
Date 2012-11-04.10:51:36
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1352026269.3394.1.camel@localhost.localdomain>
In-reply-to <1352021825.95.0.66102577565.issue5765@psf.upfronthosting.co.za>
Content
> Autogenerated code could easily hit the 1000 term limit - if anything,
> I'd be inclined to set it *higher* than 4 rather than lower, as
> breaking previously working code in a maintenance release is a bad
> thing, regardless of our opinion of the sanity of that code.

We can simply apply the 1000 limit in Python 3.4 and mark the bug as
won't fix in other versions.

I don't think adding a scaling factor just to cope with hypothetical
silly code is a good thing in the long term.
History
Date User Action Args
2012-11-04 10:51:37pitrousetrecipients: + pitrou, terry.reedy, amaury.forgeotdarc, ncoghlan, ggenellina, ag6502, benjamin.peterson, Mark.Shannon, francismb, serhiy.storchaka
2012-11-04 10:51:37pitroulinkissue5765 messages
2012-11-04 10:51:36pitroucreate