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 scoder
Recipients georg.brandl, mark.dickinson, python-dev, rhettinger, scoder, serhiy.storchaka
Date 2014-09-25.21:06:12
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
Sorry for reopening this, but I found one more thing. Division is pretty heavy on PyLong objects and there doesn't seem to be an internal optimisation for division by 1 and -1. Since many Fraction input values can already be normalised for some reason, the following change shaves off almost 30% of the calls to PyNumber_InPlaceFloorDivide() in the telco benchmark during Fraction instantiation according to callgrind, thus saving 20% of the CPU instructions that go into tp_new().

Instead of always executing

            numerator //= g
            denominator //= g

this avoids unnecessary divisions:

            if g is not 1:
                if g is -1:
                    numerator = -numerator
                    denominator = -denominator
                    numerator //= g
                    denominator //= g

Using the "is" operator here is CPythonish, but doing the same with != and == should also be an improvement already, although not as cheap. Now, given that CPython caches small integers internally, I would suggest actually not adding these two special cases to the fractions module but more generally to the division routines in longobject.c.
Date User Action Args
2014-09-25 21:06:12scodersetrecipients: + scoder, georg.brandl, rhettinger, mark.dickinson, python-dev, serhiy.storchaka
2014-09-25 21:06:12scodersetmessageid: <>
2014-09-25 21:06:12scoderlinkissue22464 messages
2014-09-25 21:06:12scodercreate