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 terry.reedy
Recipients christian.heimes, georg.brandl, ldeller, rhettinger, terry.reedy, tim.peters
Date 2009-03-20.23:14:59
SpamBayes Score 2.729199e-10
Marked as misclassified No
Message-id <1237590902.35.0.407817158541.issue4024@psf.upfronthosting.co.za>
In-reply-to
Content
I have 3 comments for future readers who might want to reopen.

1) This would have little effect on calculation with numpy.

2) According to sys.getrefcount, when '>>>' appears, 3.0.1 has 1200
duplicate references to 0 and 1 alone, and about 2000 to all of them. 
So so small int caching really needs to be done by the interpreter.  Are
there *any* duplicate internal references to 0.0 that would help justify
this proposal?

3) It is? (certainly was) standard in certain Fortran circles to NAME
constants as Raymond suggested.  One reason given was to ease conversion
between single and double precision.  In Python, named constants in
functions would ease conversion between, for instance, float and decimal.
History
Date User Action Args
2009-03-20 23:15:02terry.reedysetrecipients: + terry.reedy, tim.peters, georg.brandl, rhettinger, ldeller, christian.heimes
2009-03-20 23:15:02terry.reedysetmessageid: <1237590902.35.0.407817158541.issue4024@psf.upfronthosting.co.za>
2009-03-20 23:15:00terry.reedylinkissue4024 messages
2009-03-20 23:14:59terry.reedycreate