[issue18570] OverflowError in division: wrong message

2013-08-04 Thread Mark Dickinson
Changes by Mark Dickinson : -- resolution: -> postponed status: open -> closed ___ Python tracker ___ ___ Python-bugs-list mailing li

[issue18570] OverflowError in division: wrong message

2013-08-04 Thread Mark Dickinson
Mark Dickinson added the comment: > With that fixed, I am inclined to close this. Agreed. I'll try to find some time for a PEP at some point in the next few weeks. > I had thought of a set-mode function (method), but anticipate objection > to such modal action-at-distance behavior. Yes; I'm

[issue18570] OverflowError in division: wrong message

2013-08-03 Thread Terry J. Reedy
Terry J. Reedy added the comment: With that fixed, I am inclined to close this. -- ___ Python tracker ___ ___ Python-bugs-list mailing

[issue18570] OverflowError in division: wrong message

2013-08-03 Thread Mark Dickinson
Mark Dickinson added the comment: Exception message fixed in revision dab7d6f33b87 -- ___ Python tracker ___ ___ Python-bugs-list mail

[issue18570] OverflowError in division: wrong message

2013-07-30 Thread Terry J. Reedy
Terry J. Reedy added the comment: I would prefer one type too, if it can be done gracefully enough. I had thought of a set-mode function (method), but anticipate objection to such modal action-at-distance behavior. A context manager, which I had not thought of, somewhat alleviates that objecti

[issue18570] OverflowError in division: wrong message

2013-07-30 Thread Mark Dickinson
Mark Dickinson added the comment: > I think we might be better with two consistently behaving float classes That sounds a bit extreme. Personally, I'd look for a solution involving only one float class and a "with float.nonstopmode: ..." setting under which we get infinities and nans as presc

[issue18570] OverflowError in division: wrong message

2013-07-29 Thread Terry J. Reedy
Terry J. Reedy added the comment: +-infinity and nans were created for reasons that do not apply to standard python. In Fortran, C, etcetera, float arrays can only contain floats (hence calling a non-number a float) and continuing a computation after numerical error is more difficult or imposs

[issue18570] OverflowError in division: wrong message

2013-07-29 Thread Mark Dickinson
Mark Dickinson added the comment: I'd prefer to keep the current behaviour for int / int with an out-of-range result (i.e., raise OverflowError). As far as possible, I believe Python should raise an exception rather than return an infinity or nan whenever possible (with exceptions when one or

[issue18570] OverflowError in division: wrong message

2013-07-27 Thread Terry J. Reedy
Terry J. Reedy added the comment: Yes, 'long int' should just be 'int' in 3.x. However, int/int (integer division) is *not* the same thing as int/float. In the latter case, the int is converted to float first and if that conversion fails, there is no result. Now that int/int is always convert

[issue18570] OverflowError in division: wrong message

2013-07-27 Thread Marco Buttu
Changes by Marco Buttu : -- title: OverflowError during division: wrong message -> OverflowError in division: wrong message ___ Python tracker ___ __