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 hac.man, mark.dickinson, rhettinger, skrah
Date 2012-09-08.10:51:08
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1347101469.55.0.975090293256.issue15882@psf.upfronthosting.co.za>
In-reply-to
Content
> So, I'd really like to deprecate the whole interface in favor of either a
> read-only interface:
>
>     x.sign   -> 0 or 1 (perhaps even 1 or -1)
>     x.coeff  -> Python integer
>     x.exp    -> Python integer
> 
> If x is special, raise InvalidOperation. People usually need to check for
> specials anyhow.

Sure;  that works for me.  I don't like the current interface any more than you do, and I've always found it unnecessarily awkward to turn finite decimals into triples and back again.

But I think that's a different issue.  What we have here is a real regression that seems likely to break existing code, and I think that should be fixed.
History
Date User Action Args
2012-09-08 10:51:09mark.dickinsonsetrecipients: + mark.dickinson, rhettinger, skrah, hac.man
2012-09-08 10:51:09mark.dickinsonsetmessageid: <1347101469.55.0.975090293256.issue15882@psf.upfronthosting.co.za>
2012-09-08 10:51:09mark.dickinsonlinkissue15882 messages
2012-09-08 10:51:08mark.dickinsoncreate