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 ncoghlan
Recipients Mark.Shannon, ag6502, amaury.forgeotdarc, benjamin.peterson, francismb, ggenellina, ncoghlan, pitrou, python-dev, serhiy.storchaka, terry.reedy
Date 2012-11-04.14:00:51
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1352037652.04.0.299238816115.issue5765@psf.upfronthosting.co.za>
In-reply-to
Content
Note: if you do take the scaling factor out, don't forget to track down the reasons behind the original commit that added the test that broke *without* the scaling factor.

For me, "the test suite fails without it" is reason enough for me to say its needed - someone decided at some point to ensure that level of nesting worked, so if we're going to go back on that, we need to know the original reason why the test was added.

I think it's easier just to keep that code working, since we have a solution that *doesn't* break it and really isn't that complicated.
History
Date User Action Args
2012-11-04 14:00:52ncoghlansetrecipients: + ncoghlan, terry.reedy, amaury.forgeotdarc, ggenellina, pitrou, ag6502, benjamin.peterson, Mark.Shannon, python-dev, francismb, serhiy.storchaka
2012-11-04 14:00:52ncoghlansetmessageid: <1352037652.04.0.299238816115.issue5765@psf.upfronthosting.co.za>
2012-11-04 14:00:52ncoghlanlinkissue5765 messages
2012-11-04 14:00:51ncoghlancreate