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 amaury.forgeotdarc, eric.araujo, pitrou, rhettinger, scott_daniels, tshepang
Date 2012-06-26.02:40:20
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1340678421.72.0.430209251882.issue6422@psf.upfronthosting.co.za>
In-reply-to
Content
Looking at this again after more time has passes, I still think exposing autoranging is a good idea but I don't like the patch as it stands.  It "infects" the API in a number of places and makes the overall module harder to use and learn.   

Ideally, there should be a cleaner interface, or more limited API change, or a separate high level function that can autorange existing functions without changing their API.

Anyone care to propose a cleaner API?
History
Date User Action Args
2012-06-26 02:40:22rhettingersetrecipients: + rhettinger, scott_daniels, amaury.forgeotdarc, pitrou, eric.araujo, tshepang
2012-06-26 02:40:21rhettingersetmessageid: <1340678421.72.0.430209251882.issue6422@psf.upfronthosting.co.za>
2012-06-26 02:40:21rhettingerlinkissue6422 messages
2012-06-26 02:40:20rhettingercreate