➜

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 rhettinger
Recipients ezio.melotti, mark.dickinson, rhettinger, skrah, ubershmekel
Date 2010-07-02.01:04:39
SpamBayes Score 0.025033921
Marked as misclassified No
Message-id <1278032682.23.0.95110487935.issue9136@psf.upfronthosting.co.za>
In-reply-to
Content 
> I also don't think that the 2.x-to-3.x maintenance issue 
> is that big a deal any more;  it would be surprising if 
> the 2.x version of Decimal sees anything more than minor 
> changes (doc fixes, etc.) from this point on.  So perhaps 
> the 3.x version of the decimal module should be free to 
> make full use of 3.x syntax?

I would like to still leave us at 2.5 compatible.
The internal comments promise that spec updates
will be treated as bug fixes.  This is all the
more likely if 2.7 is the last, but long lived
version in the 2.x series.

Besides, I don't think the set comprehension
notation was a big win in readability over
what is there now :-)
History
Date User Action Args
2010-07-02 01:04:43rhettingersetrecipients: + rhettinger, mark.dickinson, ezio.melotti, ubershmekel, skrah
2010-07-02 01:04:42rhettingersetmessageid: <1278032682.23.0.95110487935.issue9136@psf.upfronthosting.co.za>
2010-07-02 01:04:40rhettingerlinkissue9136 messages
2010-07-02 01:04:39rhettingercreate