Re: Inconsistency producing constant for float "infinity"

2006-08-12 Thread Alex Martelli
Tim Peters <[EMAIL PROTECTED]> wrote: [snip] thanks for an exhaustively satisfying explanation! Alex -- http://mail.python.org/mailman/listinfo/python-list

Re: Inconsistency producing constant for float "infinity"

2006-08-12 Thread Tim Peters
[Tim Peters] >... >> It has a much better chance of working from .pyc in Python 2.5. >> Michael Hudson put considerable effort into figuring out whether the >> platform uses a recognizable IEEE double storage format, and, if so, >> marshal and pickle take different paths that preserve infinitie

Re: Inconsistency producing constant for float "infinity"

2006-08-12 Thread Alex Martelli
Tim Peters <[EMAIL PROTECTED]> wrote: ... > It has a much better chance of working from .pyc in Python 2.5. > Michael Hudson put considerable effort into figuring out whether the > platform uses a recognizable IEEE double storage format, and, if so, > marshal and pickle take different paths that

Re: Inconsistency producing constant for float "infinity"

2006-08-11 Thread Tim Peters
[Peter Hansen] >> I'm investigating a puzzling problem involving an attempt to >> generate a constant containing an (IEEE 754) "infinity" value. (I >> understand that special float values are a "platform-dependent >> accident" etc...) [also Peter] > ... > My guess about marshal was correct. Yup.

Re: Inconsistency producing constant for float "infinity"

2006-08-11 Thread Peter Hansen
Sybren Stuvel wrote: > Peter Hansen enlightened us with: > >>I'm investigating a puzzling problem involving an attempt to >>generate a constant containing an (IEEE 754) "infinity" value. (I >>understand that special float values are a "platform-dependent >>accident" etc...) > > Why aren't you si

Inconsistency producing constant for float "infinity"

2006-08-11 Thread Peter Hansen
I'm investigating a puzzling problem involving an attempt to generate a constant containing an (IEEE 754) "infinity" value. (I understand that special float values are a "platform-dependent accident" etc...) The issue appears possibly to point to a bug in the Python compiler, with it producing