Notice: While JavaScript is not essential for this website, your interaction with the content will be limited. Please turn JavaScript on for the full experience.
...interface (the "re" module). You can explicitly invoke the old engine by import pre, or the SRE engine by importing sre. SRE is faster than pre, and supports Unicode (which was the main reason to put effort in yet another new regular expression engine -- this is at least the fourth!). Other Changes Other changes that won't break code but are nice to know about: Deleting objects is now safe even for deeply nested data structures. Long/int unifications: long integers ...
...int" <p><li>Overflowing int operations return the corresponding long value rather than raising the OverflowError exception. <p><li>Conversion of long to float now raises OverflowError if the long is too big to represent as a C double. This used to return an "infinity" value on most platforms. <p><li> The 3-argument builtin 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...
Version: None
Released: Nov. 27, 2010
Note: It is recommended that you use the latest bug fix release of the 3.1 series, 3.1.4. Python 3.1.3 was released on November 27th, 2010. The Python 3.1 version series is a continuation of the work started by Python 3.0, the new backwards-incompatible series of Python. For ongoing …
View Release Notes
Released: June 11, 2025
This is the fifth maintenance release of Python 3.13 Python 3.13 is the newest major release of the Python programming language, and it contains many new features and optimizations compared to Python 3.12. 3.13.5 is the fifth maintenance release of 3.13. 3.13.5 is an expedited release to fix a couple …
...intenance releases, please see the Python 3.2 series. Improvements in this release include: An ordered dictionary type Various optimizations to the int type New unittest features including test skipping and new assert methods. A much faster io module Tile support for Tkinter A pure Python reference implementation of the import statement New syntax for nested with statements See these resources for further information: What's New in 3.1? What's new in Python 3000? Python 3.1.3 Change Log Onli...
Released: June 11, 2011
Note: It is recommended that you use the latest bug fix release of the 3.1 series, 3.1.5. Python 3.1.4 was released on June 11th, 2011. The Python 3.1 version series is a continuation of the work started by Python 3.0, the new backwards-incompatible series of Python. For ongoing …
...intenance releases, please see the Python 3.2 series. Improvements in the the 3.1 series release include: An ordered dictionary type Various optimizations to the int type New unittest features including test skipping and new assert methods. A much faster io module Tile support for Tkinter A pure Python reference implementation of the import statement New syntax for nested with statements See these resources for further information: What's New in 3.1? What's new in Python 3000? Python 3.1.4 C...
...int x" in a 3 >>> print a.keys() ['__builtins__', 1, 2, 'x'] >>> print a['x'] 3 >>> However, our __getitem__() method is not used for variable access by the interpreter: >>> exec "print foo" in a Traceback (most recent call last): File "<stdin>", line 1, in ? File "<string>", line 1, in ? NameError: name 'foo' is not defined >>> Why doesn't this print 0.0? The interpreter uses an internal function to access ...
...int a.keys() [1, 2] >>> exec "x = 3; print x" in a 3 >>> print a.keys() ['__builtins__', 1, 2, 'x'] >>> print a['x'] 3 >>> However, our __getitem__() method is not used for variable access by the interpreter: >>> exec "print foo" in a Traceback (most recent call last): File "<stdin>", line 1, in ? File "<string>", line 1, in ? NameError: name 'foo' is not defined >>> Why doesn't this print 0.0? The interpreter uses an internal function to access the dic...
...interface (the "re" module). You can explicitly invoke the old engine by import pre, or the SRE engine by importing sre. SRE is faster than pre, and supports Unicode (which was the main reason to put effort in yet another new regular expression engine -- this is at least the fourth!). Other Changes Other changes that won't break code but are nice to know about: Deleting objects is now safe even for deeply nested data structures. Long/int unifications: long integers can be used in ...
...Int, PyArg_NoArgs, _PyObject_Del. Removed these typedefs: intargfunc, intintargfunc, intobjargproc, intintobjargproc, getreadbufferproc, getwritebufferproc, getsegcountproc, getcharbufferproc, memberlist. Tests Removed test.testall as test.regrtest replaces it. Documentation Mac The cfmfile module was removed. Platforms Support for BeOS and AtheOS was removed (according to PEP 11). Support for RiscOS, Irix, Tru64 was removed (alledgedly). Tools/Demos (For information about older...
...inter to the default encoded string data instead of to the raw UTF-16. Py_BuildValue accepts B format (for bgen-generated code). Internals On Unix, fix code for finding Python installation directory so that it works when argv[0] is a relative path. Added a true tnicode_internal_encode() function and fixed the unicode_internal_decode function() to support Unicode objects directly rather than by generating a copy of the object. Several of the internal Unicode ...
...InternalCall(). It is still the case that the returned code object might be entirely insane. Subclasses of string can no longer be interned. The semantics of interning were not clear here -- a subclass could be mutable, for example -- and had bugs. Explicitly interning a subclass of string via intern() will raise a TypeError. Internal operations that attempt to intern a string subclass will have no effect. Bug 1003935: xrange() could report bogus OverflowErrors. Documented what xrange() in...
...int $"The area of a $x by $y rectangle is $z" is very questionable, but none of the alternatives I've seen proposed (e.g. i"...") look very good either. We can't just always turn on string interpolation in literals because that would break existing code. Maybe "from __future__ import interpolation" would enable interpolation in string literals? (Only in literals!) There's also the question whether to allow arbitrary expressions like print "The area is ${x*y}" PEP 2...
...integers, ok? Her: Okay. Me : So, you can add them, subtract them, and multiply them in a program, right? Her: Um. Sure. Me : Now let's say that you divide them-- Her: But that makes no sense! Integers form a ring, not a field. You did say you were taking these numbers from Z, right? Me : Uh, yeah. So there you have it. The non-programmer viewpoint. (With which I conveniently agree.) "Integer division" is hokey and shouldn't be spelled "/", even if C wants to....
If you didn't find what you need, try your search in the Python language documentation.