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 Doug.Shea, mark.dickinson, mhenriq
Date 2010-11-22.18:55:57
SpamBayes Score 1.4301726e-07
Marked as misclassified No
Message-id <1290452159.78.0.533428019471.issue9742@psf.upfronthosting.co.za>
In-reply-to
Content
Thanks.  I'm still stuck, though.  Since I'm pretty much at the wild guesses stage, here's one:

<wild idea> Perhaps the pymath.o object file isn't being included in the Python executable at all, because none of its functions are needed.  Now that doesn't seem to make sense, since the round function is needed, and used, in Objects/floatobject.c (that is, if PY_NO_SHORT_FLOAT_REPR is *not* defined;  I'm still not clear on whether that's the case or not---if you can get as far as launching an interpreter, then the result of sys.float_repr_style would be 'short' in that case).  But gcc (depending on the version, I guess) has builtin versions of some standard C library functions, including 'round'.  So if it were using the builtin then there would be no need to link to the pymath.o file, so it might be left out of the python executable.  But I'm not sure why the same doesn't happen when compiling the math module.

Neither am I sure how one might go about testing the above hypothesis.
History
Date User Action Args
2010-11-22 18:55:59mark.dickinsonsetrecipients: + mark.dickinson, mhenriq, Doug.Shea
2010-11-22 18:55:59mark.dickinsonsetmessageid: <1290452159.78.0.533428019471.issue9742@psf.upfronthosting.co.za>
2010-11-22 18:55:57mark.dickinsonlinkissue9742 messages
2010-11-22 18:55:57mark.dickinsoncreate