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 serge.stroobandt
Recipients Keith.Brafford, eric.smith, ezio.melotti, facundobatista, mark.dickinson, rhettinger, serge.stroobandt, skrah, tim.peters
Date 2016-01-27.20:46:33
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1453927593.78.0.776270157819.issue26223@psf.upfronthosting.co.za>
In-reply-to
Content
@rhettinger
I completely agree with not creating a backward incompatibility at this point in time.

The real issue is that decimal.to_eng_string() was written to a (unfortunately chosen) proprietary specification which does not entirely correspond to the engineering notation.

A quick web search shows that a lot of people are in search of a *true* engineering notation implementation. In the phylosophy of "batteries included" it is a pity this useful and very common notation is currently missing in Python.

I would therefore suggest adding a decimal.to_true_eng_string() with the true engineering notation.

Hence, this bug could be reclassified as asuggestion for enhancement.
History
Date User Action Args
2016-01-27 20:46:33serge.stroobandtsetrecipients: + serge.stroobandt, tim.peters, rhettinger, facundobatista, mark.dickinson, eric.smith, ezio.melotti, skrah, Keith.Brafford
2016-01-27 20:46:33serge.stroobandtsetmessageid: <1453927593.78.0.776270157819.issue26223@psf.upfronthosting.co.za>
2016-01-27 20:46:33serge.stroobandtlinkissue26223 messages
2016-01-27 20:46:33serge.stroobandtcreate