Results

• Known bugs in Python 2.2.1

  ...pow() no longer allows a third non-None argument if either of the first two arguments is a float, or if both are of integer types and the second argument is negative (in which latter case the arguments are converted to float, so this is really the same restriction). <p><li>An old tokenizer bug allowed floating point literals with an incomplete exponent, such as 1e and 3.1e-. Such literals now raise SyntaxError. <p><li>Nested scopes are standard in 2.2 (they were enabled ...

• Incompatibilities between Python 2.1[.x] and 2.2[.x]

  ...pow() no longer allows a third non-None argument if either of the first two arguments is a float, or if both are of integer types and the second argument is negative (in which latter case the arguments are converted to float, so this is really the same restriction). <p><li>An old tokenizer bug allowed floating point literals with an incomplete exponent, such as 1e and 3.1e-. Such literals now raise SyntaxError. <p><li>Nested scopes are standard in 2.2 (they were enabled ...

• Incompatibilities between Python 2.1[.x] and 2.2[.x]

  ...pow() no longer allows a third non-None argument if either of the first two arguments is a float, or if both are of integer types and the second argument is negative (in which latter case the arguments are converted to float, so this is really the same restriction). <p><li>An old tokenizer bug allowed floating point literals with an incomplete exponent, such as 1e and 3.1e-. Such literals now raise SyntaxError. <p><li>Nested scopes are standard in 2.2 (they were enabled ...

• Known bugs in Python 2.2

  ...pow() no longer allows a third non-None argument if either of the first two arguments is a float, or if both are of integer types and the second argument is negative (in which latter case the arguments are converted to float, so this is really the same restriction). <p><li>An old tokenizer bug allowed floating point literals with an incomplete exponent, such as 1e and 3.1e-. Such literals now raise SyntaxError. <p><li>Nested scopes are standard in 2.2 (they were enabled ...

• Notes

  ...pow() no longer lets the platform C pow() raise -1.0 to integer powers, because (at least) glibc gets it wrong in some cases. The result should be -1.0 if the power is odd and 1.0 if the power is even, and any float with a sufficiently large exponent is (mathematically) an exact even integer. SF bug 759227: A new-style class that implements __nonzero__() must return a bool or int (but not an int subclass) from that method. This matches the restriction on classic classes. The encoding attribute...

• Python 2.4.1 - Release Notes

  ...pow() no longer lets the platform C pow() raise -1.0 to integer powers, because (at least) glibc gets it wrong in some cases. The result should be -1.0 if the power is odd and 1.0 if the power is even, and any float with a sufficiently large exponent is (mathematically) an exact even integer. SF bug 759227: A new-style class that implements __nonzero__() must return a bool or int (but not an int subclass) from that method. This matches the restriction on classic classes. The encoding attribute...

Python language documentation

If you didn't find what you need, try your search in the Python language documentation.