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 Alexander.Belopolsky
Recipients Alexander.Belopolsky, akitada, christian.heimes, josm, loewis, mark.dickinson, rhettinger, robertwb, zanella
Date 2010-05-01.15:35:54
SpamBayes Score 2.2976552e-05
Marked as misclassified No
Message-id <t2qd38f5331005010835ha12e03faj7ab77293edd5f7f7@mail.gmail.com>
In-reply-to <1272725979.06.0.46983638581.issue1533@psf.upfronthosting.co.za>
Content
On Sat, May 1, 2010 at 10:59 AM, Mark Dickinson <report@bugs.python.org> wrote:
>
> Mark Dickinson <dickinsm@gmail.com> added the comment:
>
> Decimal is behaving in exactly the same way as MyInt, isn't it?
> What do you get for range(MyInt(20), MyInt(20))?
>

Hmm, maybe there is a 2.7 bug here after all:

[20, 21, 22]
>>> range(MyInt(2**64), MyInt(2**64+3))
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
TypeError: range() integer start argument expected, got instance.

Same with Decimal:

Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
TypeError: range() integer start argument expected, got Decimal.
History
Date User Action Args
2010-05-01 15:35:56Alexander.Belopolskysetrecipients: + Alexander.Belopolsky, loewis, rhettinger, mark.dickinson, christian.heimes, josm, robertwb, zanella, akitada
2010-05-01 15:35:55Alexander.Belopolskylinkissue1533 messages
2010-05-01 15:35:54Alexander.Belopolskycreate