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 mark.dickinson
Recipients belopolsky, mark.dickinson, mcherm, rhettinger, stutzbach, tim.peters, vstinner
Date 2010-06-01.06:59:35
SpamBayes Score 0.07921209
Marked as misclassified No
Message-id <1275375577.66.0.214035966135.issue8860@psf.upfronthosting.co.za>
In-reply-to
Content
The accumulated error doesn't need to exceed 1;  it just needs to be enough to make (e.g.) leftover appear to be >= 0.5 when it's actually just less than 0.5.  It shouldn't be too hard to find examples where this happens, but I haven't thought about it.

> I wonder if it would be justified to expose something like
> int _PyLong_IsOdd(PyObject *self) {...}

Yes, that could work.  I'd be happier with this if there are other uses (even within longobject.c);  there might well be, but I haven't looked.  I also have a mild preference for _PyLong_IsEven over _PyLong_IsOdd.  :)
History
Date User Action Args
2010-06-01 06:59:37mark.dickinsonsetrecipients: + mark.dickinson, tim.peters, mcherm, rhettinger, belopolsky, vstinner, stutzbach
2010-06-01 06:59:37mark.dickinsonsetmessageid: <1275375577.66.0.214035966135.issue8860@psf.upfronthosting.co.za>
2010-06-01 06:59:35mark.dickinsonlinkissue8860 messages
2010-06-01 06:59:35mark.dickinsoncreate