traverseda
/
cpython
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity
cpython/Misc/NEWS

4368 lines
177 KiB
Plaintext
Raw Normal View History

ReST-ification of the NEWS file. While the total number of changes are fairly large, most are caused by reformatting section and subsection headings. The changes fall into the following categories: * reformatted section and subsection headers. * escaped isolated asterisks which would be interpreted as starting bold or italic text (e.g. "void (*)(PyObject \*)"). * quoted stuff that looks like internal references but isn't (e.g. ``PyCmp_``). * changed visually balanced quotes to just use apostrophes (e.g. "'string'" instead of "`string'"). * introduced and indenting multiline chunks of code. * created one table (search for "New codecs").
2002-09-20 11:16:59 -03:00
+++++++++++
Python News
+++++++++++
reference the new NEWS.help file
2002-09-20 14:08:52 -03:00
(editors: check NEWS.help for information about editing NEWS using ReST.)
add skeletal "what's new" for 2.4a1 and mention a couple python-mode tweaks.
2003-08-01 02:01:54 -03:00
What's New in Python 2.4 alpha 1?
=================================
*Release date: DD-MMM-YYYY*
Core and builtins
-----------------
Fix the grammar a bit more. (Adjusted by Tony Meyer)
2004-06-03 08:10:58 -03:00
- Unicode objects received two new methods: iswide() and width().
These query East Asian width information, as specified in Unicode
TR11.
- SF #962502: Add two more methods for unicode type; width() and iswide() for east asian width manipulation. (Inspired by David Goodger, Reviewed by Martin v. Loewis) - Move _PyUnicode_TypeRecord.flags to the end of the struct so that no padding is added for UCS-4 builds. (Suggested by Martin v. Loewis)
2004-06-02 13:49:17 -03:00
SF bug #942952: Weakness in tuple hash (Basic approach and test concept by Tim Peters.) * Improved the hash to reduce collisions. * Added the torture test to the test suite.
2004-06-01 03:36:24 -03:00
- Improved the tuple hashing algorithm to give fewer collisions in
common cases. Fixes bug #942952.
SF patch #872326: Generator expression implementation (Code contributed by Jiwon Seo.) The documentation portion of the patch is being re-worked and will be checked-in soon. Likewise, PEP 289 will be updated to reflect Guido's rationale for the design decisions on binding behavior (as described in in his patch comments and in discussions on python-dev). The test file, test_genexps.py, is written in doctest format and is meant to exercise all aspects of the the patch. Further additions are welcome from everyone. Please stress test this new feature as much as possible before the alpha release.
2004-05-19 05:20:33 -03:00
- Implemented generator expressions (PEP 289). Coded by Jiwon Seo.
Enable the profiling of C functions (builtins and extensions)
2004-03-24 17:57:10 -04:00
- Enabled the profiling of C extension functions (and builtins) - check
new documentation and modified profiler and bdb modules for more details
Changed file.name to be the object passed as the 'name' argument to file() Fixes SF Bug #773356
2004-03-21 16:24:07 -04:00
- Set file.name to the object passed to open (instead of a new string)
Moved tracebackobject to traceback.h, Closes SF Bug #497067
2004-03-21 14:37:23 -04:00
- Moved tracebackobject into traceback.h and renamed to PyTracebackObject
Improve byte coding for multiple assignments. Gives 30% speedup on "a,b=1,2" and 25% on "a,b,c=1,2,3".
2004-03-21 11:12:00 -04:00
- Optimized the byte coding for multiple assignments like "a,b=b,a" and
"a,b,c=1,2,3". Improves their speed by 25% to 30%.
Limit the nesting depth of a tuple passed as the second argument to isinstance() or issubclass() to the recursion limit of the interpreter.
2004-03-20 18:52:14 -04:00
- Limit the nested depth of a tuple for the second argument to isinstance()
and issubclass() to the recursion limit of the interpreter.
Fixes bug #858016 .
Add news entries for the dictionary optimizations.
2004-03-18 05:48:12 -04:00
- Optimized dict iterators, creating separate types for each
and having them reveal their length. Also optimized the
methods: keys(), values(), and items().
SF patch #910929: Optimize list comprehensions Add a new opcode, LIST_APPEND, and apply it to the code generation for list comprehensions. Reduces the per-loop overhead by about a third.
2004-03-07 03:31:06 -04:00
- Implemented a newcode opcode, LIST_APPEND, that simplifies
the generated bytecode for list comprehensions and further
improves their performance (about 35%).
"Fix" (for certain configurations of the planets, including recent gcc on Linux/x86) [ 899109 ] 1==float('nan') by implementing rich comparisons for floats. Seems to make comparisons involving NaNs somewhat less surprising when the underlying C compiler actually implements C99 semantics.
2004-02-19 15:35:22 -04:00
- Implemented rich comparisons for floats, which seems to make
comparisons involving NaNs somewhat less surprising when the
underlying C compiler actually implements C99 semantics.
* Moved the responsibility for emptying the previous list from list_fill to list_init. * Replaced the code in list_extend with the superior code from list_fill. * Eliminated list_fill. Results: * list.extend() no longer creates an intermediate tuple except to handle the special case of x.extend(x). The saves memory and time. * list.extend(x) runs about the same x is a list or tuple, a little faster when x is an iterable not defining __len__, and twice as fast when x is an iterable defining __len__. * the code is about 15 lines shorter and no longer duplicates functionality.
2004-02-15 00:06:39 -04:00
- Optimized list.extend() to save memory and no longer create
intermediate sequences. Also, extend() now pre-allocates the
needed memory whenever the length of the iterable is known in
advance -- this halves the time to extend the list.
* Optimized list appends and pops by making fewer calls the underlying system realloc(). This is achieved by tracking the overallocation size in a new field and using that information to skip calls to realloc() whenever possible. * Simplified and tightened the amount of overallocation. For larger lists, this overallocates by 1/8th (compared to the previous scheme which ranged between 1/4th to 1/32nd over-allocation). For smaller lists (n<6), the maximum overallocation is one byte (formerly it could be upto eight bytes). This saves memory in applications with large numbers of small lists. * Eliminated the NRESIZE macro in favor of a new, static list_resize function that encapsulates the resizing logic. Coverting this back to macro would give a small (under 1%) speed-up. This was too small to warrant the loss of readability, maintainability, and de-coupling. * Some functions using NRESIZE had grown unnecessarily complex in their efforts to bend to the macro's calling pattern. With the new list_resize function in place, those other functions could be simplified. That is being saved for a separate patch. * The ob_item==NULL check could be eliminated from the new list_resize function. This would entail finding each piece of code that sets ob_item to NULL and adding a new line to invalidate the overallocation tracking field. Rather than impose a new requirement on other pieces of list code, it was preferred to leave the NULL check in place and retain the benefits of decoupling, maintainability and information hiding (only PyList_New() and list_sort() need to know about the new field). This approach also reduces the odds of breaking an extension module. (Collaborative effort by Raymond Hettinger, Hye-Shik Chang, Tim Peters, and Armin Rigo.)
2004-02-13 07:36:39 -04:00
- Optimized list resize operations to make fewer calls to the system
realloc(). Significantly speeds up list appends, list pops,
list comprehensions, and the list contructor (when the input iterable
length is not known).
- Changed the internal list over-allocation scheme. For larger lists,
overallocation ranged between 3% and 25%. Now, it is a constant 12%.
Fine tune the speed/space trade-off for overallocating small lists. The Py2.3 approach overallocated small lists by up to 8 elements. The last checkin would limited this to one but slowed down (by 20 to 30%) the creation of small lists between 3 to 8 elements. This tune-up balances the two, limiting overallocation to 3 elements (significantly reducing space consumption from Py2.3) and running faster than the previous checkin. The first part of the growth pattern (0, 4, 8, 16) neatly meshes with allocators that trigger data movement only when crossing a power of two boundary. Also, then even numbers mesh well with common data alignments.
2004-02-14 14:34:46 -04:00
For smaller lists (n<8), overallocation was upto eight elements. Now,
the overallocation is no more than three elements -- this improves space
* Optimized list appends and pops by making fewer calls the underlying system realloc(). This is achieved by tracking the overallocation size in a new field and using that information to skip calls to realloc() whenever possible. * Simplified and tightened the amount of overallocation. For larger lists, this overallocates by 1/8th (compared to the previous scheme which ranged between 1/4th to 1/32nd over-allocation). For smaller lists (n<6), the maximum overallocation is one byte (formerly it could be upto eight bytes). This saves memory in applications with large numbers of small lists. * Eliminated the NRESIZE macro in favor of a new, static list_resize function that encapsulates the resizing logic. Coverting this back to macro would give a small (under 1%) speed-up. This was too small to warrant the loss of readability, maintainability, and de-coupling. * Some functions using NRESIZE had grown unnecessarily complex in their efforts to bend to the macro's calling pattern. With the new list_resize function in place, those other functions could be simplified. That is being saved for a separate patch. * The ob_item==NULL check could be eliminated from the new list_resize function. This would entail finding each piece of code that sets ob_item to NULL and adding a new line to invalidate the overallocation tracking field. Rather than impose a new requirement on other pieces of list code, it was preferred to leave the NULL check in place and retain the benefits of decoupling, maintainability and information hiding (only PyList_New() and list_sort() need to know about the new field). This approach also reduces the odds of breaking an extension module. (Collaborative effort by Raymond Hettinger, Hye-Shik Chang, Tim Peters, and Armin Rigo.)
2004-02-13 07:36:39 -04:00
utilization for applications that have large numbers of small lists.
SF patch #947476: Apply freelist technique to lists Re-use list object bodies. Saves calls to malloc() and free() for faster list instantiation and deallocation.
2004-05-05 02:37:53 -03:00
- Most list bodies now get re-used rather than freed. Speeds up list
instantiation and deletion by saving calls to malloc() and free().
SF #904720: dict.update should take a 2-tuple sequence like dict.__init_ (Championed by Bob Ippolito.) The update() method for mappings now accepts all the same argument forms as the dict() constructor. This includes item lists and/or keyword arguments.
2004-03-04 04:25:44 -04:00
- The dict.update() method now accepts all the same argument forms
as the dict() constructor. This now includes item lists and/or
keyword arguments.
This is my patch #876198 plus a NEWS entry and a header frob. Remove the ability to use (from C) arbitrary objects supporting the read buffer interface as the co_code member of code objects.
2004-02-12 11:28:27 -04:00
- Support for arbitrary objects supporting the read-only buffer
interface as the co_code field of code objects (something that was
only possible to create from C code) has been removed.
added notes about weakref changes
2004-02-06 00:15:22 -04:00
- Made omitted callback and None equivalent for weakref.ref() and
weakref.proxy(); the None case wasn't handled correctly in all
cases.
- Fixed problem where PyWeakref_NewRef() and PyWeakref_NewProxy()
assumed that initial existing entries in an object's weakref list
would not be removed while allocating a new weakref object. Since
GC could be invoked at that time, however, that assumption was
invalid. In a truly obscure case of GC being triggered during
creation for a new weakref object for an referent which already
has a weakref without a callback which is only referenced from
cyclic trash, a memory error can occur. This consistently created a
segfault in a debug build, but provided less predictable behavior in
a release build.
Fix input() builtin function to respect compiler flags. (SF patch 876178, patch by mwh, unittest by perky)
2004-02-02 09:39:01 -04:00
- input() builtin function now respects compiler flags such as
__future__ statements. SF patch 876178.
Add news about removal of the PendingDeprecationWarning from apply().
2003-12-05 13:43:47 -04:00
- Removed PendingDeprecationWarning from apply(). apply() remains
Fix typo and improve wording a bit.
2003-12-15 15:24:34 -04:00
deprecated, but the nuisance warning will not be issued.
Add news about removal of the PendingDeprecationWarning from apply().
2003-12-05 13:43:47 -04:00
Py_Finalize(): disabled the second call of cyclic gc, and added extensive comments about why both calls to cyclic gc here can cause problems. I'll backport to 2.3 maint. Since the calls were introduced in 2.3, that will be the end of it.
2003-12-01 17:35:27 -04:00
- At Python shutdown time (Py_Finalize()), 2.3 called cyclic garbage
collection twice, both before and after tearing down modules. The
call after tearing down modules has been disabled, because too much
of Python has been torn down then for __del__ methods and weakref
callbacks to execute sanely. The most common symptom was a sequence
of uninformative messages on stderr when Python shut down, produced
by threads trying to raise exceptions, but unable to report the nature
of their problems because too much of the sys module had already been
destroyed.
- Removed FutureWarnings related to hex/oct literals and conversions and left shifts. (Thanks to Kalle Svensson for SF patch 849227.) This addresses most of the remaining semantic changes promised by PEP 237, except for repr() of a long, which still shows the trailing 'L'. The PEP appears to promise warnings for operations that changed semantics compared to Python 2.3, but this is not implemented; we've suffered through enough warnings related to hex/oct literals and I think it's best to be silent now.
2003-11-29 19:52:13 -04:00
- Removed FutureWarnings related to hex/oct literals and conversions
and left shifts. (Thanks to Kalle Svensson for SF patch 849227.)
This addresses most of the remaining semantic changes promised by
PEP 237, except for repr() of a long, which still shows the trailing
'L'. The PEP appears to promise warnings for operations that
changed semantics compared to Python 2.3, but this is not
implemented; we've suffered through enough warnings related to
hex/oct literals and I think it's best to be silent now.
Add optional fillchar argument to ljust(), rjust(), and center() string methods.
2003-11-26 04:21:35 -04:00
- For str and unicode objects, the ljust(), center(), and rjust()
methods now accept an optional argument specifying a fill
character other than a space.
- When method objects have an attribute that can be satisfied either by the function object or by the method object, the function object's attribute usually wins. Christian Tismer pointed out that that this is really a mistake, because this only happens for special methods (like __reduce__) where the method object's version is really more appropriate than the function's attribute. So from now on, all method attributes will have precedence over function attributes with the same name.
2003-11-22 19:55:50 -04:00
- When method objects have an attribute that can be satisfied either
by the function object or by the method object, the function
object's attribute usually wins. Christian Tismer pointed out that
that this is really a mistake, because this only happens for special
methods (like __reduce__) where the method object's version is
really more appropriate than the function's attribute. So from now
on, all method attributes will have precedence over function
attributes with the same name.
SF bug 839548: Bug in type's GC handling causes segfaults. Also SF patch 843455. This is a critical bugfix. I'll backport to 2.3 maint, but not beyond that. The bugs this fixes have been there since weakrefs were introduced.
2003-11-20 17:21:46 -04:00
- Critical bugfix, for SF bug 839548: if a weakref with a callback,
its callback, and its weakly referenced object, all became part of
cyclic garbage during a single run of garbage collection, the order
in which they were torn down was unpredictable. It was possible for
the callback to see partially-torn-down objects, leading to immediate
segfaults, or, if the callback resurrected garbage objects, to
resurrect insane objects that caused segfaults (or other surprises)
later. In one sense this wasn't surprising, because Python's cyclic gc
had no knowledge of Python's weakref objects. It does now. When
weakrefs with callbacks become part of cyclic garbage now, those
weakrefs are cleared first. The callbacks don't trigger then,
preventing the problems. If you need callbacks to trigger, then just
as when cyclic gc is not involved, you need to write your code so
that weakref objects outlive the objects they weakly reference.
* Migrate set() and frozenset() from the sandbox. * Install the unittests, docs, newsitem, include file, and makefile update. * Exercise the new functions whereever sets.py was being used. Includes the docs for libfuncs.tex. Separate docs for the types are forthcoming.
2003-11-16 12:17:49 -04:00
SF bug 840829: weakref callbacks and gc corrupt memory. subtype_dealloc(): This left the dying object exposed to gc, so that if cyclic gc triggered during the weakref callback, gc tried to delete the dying object a second time. That's a disaster. subtype_dealloc() had a (I hope!) unique problem here, as every normal dealloc routine untracks the object (from gc) before fiddling with weakrefs etc. But subtype_dealloc has obscure technical reasons for re-registering the dying object with gc (already explained in a large comment block at the bottom of the function). The fix amounts to simply refraining from reregistering the dying object with gc until after the weakref callback (if any) has been called. This is a critical bug (hard to predict, and causes seemingly random memory corruption when it occurs). I'll backport it to 2.3 later.
2003-11-12 16:43:28 -04:00
- Critical bugfix, for SF bug 840829: if cyclic garbage collection
happened to occur during a weakref callback for a new-style class
instance, subtle memory corruption was the result (in a release build;
in a debug build, a segfault occurred reliably very soon after).
This has been repaired.
SF bug 839548: Bug in type's GC handling causes segfaults. Also SF patch 843455. This is a critical bugfix. I'll backport to 2.3 maint, but not beyond that. The bugs this fixes have been there since weakrefs were introduced.
2003-11-20 17:21:46 -04:00
- Compiler flags set in PYTHONSTARTUP are now active in __main__.
- Added two builtin types, set() and frozenset().
Implement and apply PEP 322, reverse iteration
2003-11-06 10:06:48 -04:00
- Added a reversed() builtin function that returns a reverse iterator
over a sequence.
Guido grants a Christmas wish: sorted() becomes a regular function instead of a classmethod.
2003-12-17 16:43:33 -04:00
- Added a sorted() builtin function that returns a new sorted list
SF patch 959726: sdist versus SVN The disutils sdist command now ignores .svn directories.
2004-05-31 16:27:59 -03:00
from any iterable.
Guido grants a Christmas wish: sorted() becomes a regular function instead of a classmethod.
2003-12-17 16:43:33 -04:00
Make CObjects mutable. Fixes #477441.
2003-10-19 15:30:01 -03:00
- CObjects are now mutable (on the C level) through PyCObject_SetVoidPtr.
* list.sort() now supports three keyword arguments: cmp, key, and reverse. key provides C support for the decorate-sort-undecorate pattern. reverse provide a stable sort of the list with the comparisions reversed. * Amended the docs to guarantee sort stability.
2003-10-16 00:41:09 -03:00
- list.sort() now supports three keyword arguments: cmp, key, and reverse.
The key argument can be a function of one argument that extracts a
comparison key from the original record: mylist.sort(key=str.lower).
The reverse argument is a boolean value and if True will change the
sort order as if the comparison arguments were reversed. In addition,
the documentation has been amended to provide a guarantee that all sorts
starting with Py2.3 are guaranteed to be stable (the relative order of
records with equal keys is unchanged).
Added test whether wchar_t is signed or not. A signed wchar_t is not usable as internal unicode type base for Py_UNICODE since the unicode implementation assumes an unsigned type.
2003-09-22 08:14:40 -03:00
- Added test whether wchar_t is signed or not. A signed wchar_t is not
usable as internal unicode type base for Py_UNICODE since the
unicode implementation assumes an unsigned type.
Double-fix of crash in Unicode freelist handling. If a length-1 Unicode string was in the freelist and it was uninitialized or pointed to a very large (magnitude) negative number, the check unicode_latin1[unicode->str[0]] == unicode could cause a segmentation violation, e.g. unicode->str[0] is 0xcbcbcbcb. Fix this in two ways: 1. Change guard befor unicode_latin1[] to test against 256U. If I understand correctly, the unsigned long used to store UCS4 on my box was getting converted to a signed long to compare with the signed constant 256. 2. Change _PyUnicode_New() to make sure the first element of str is always initialized to zero. There are several places in the code where the caller can exit with an error before initializing any of str, which would leave junk in str[0]. Also, silence a compiler warning on pointer vs. int arithmetic. Bug fix candidate.
2003-09-16 16:41:39 -03:00
- Fixed a bug in the cache of length-one Unicode strings that could
lead to a seg fault. The specific problem occurred when an earlier,
non-fatal error left an uninitialized Unicode object in the
freelist.
SF bug #795506: Wrong handling of string format code for float values. Adding missing support for '%F'. Will backport to 2.3.1.
2003-08-27 01:55:52 -03:00
- The % formatting operator now supports '%F' which is equivalent to
'%f'. This has always been documented but never implemented.
complex_new(): This could leak when the argument was neither string nor number. This accounts for the 2 refcount leaks per test_complex run Michael Hudson discovered (I figured only I would have the stomach to look for leaks in floating-point code <wink>).
2003-08-14 22:16:37 -03:00
- complex(obj) could leak a little memory if obj wasn't a string or
number.
As discussed on python-dev, changed builtin.zip() to handle zero arguments by returning an empty list instead of raising a TypeError.
2003-08-02 04:42:57 -03:00
- zip() with no arguments now returns an empty list instead of raising
a TypeError exception.
SF patch #820195 by Wojtek Walczak (gminick at users.sourceforge.net): make obj.__contains__() returns True/False instead of 1/0.
2003-10-08 18:08:29 -03:00
- obj.__contains__() now returns True/False instead of 1/0. SF patch
820195.
Deleting cyclic object comparison. SF patch 825639 http://mail.python.org/pipermail/python-dev/2003-October/039445.html
2003-10-28 08:05:48 -04:00
- Python no longer tries to be smart about recursive comparisons.
When comparing containers with cyclic references to themselves it
will now just hit the recursion limit. See SF patch 825639.
Fix typo and improve wording a bit.
2003-12-15 15:24:34 -04:00
- str and unicode builtin types now have rsplit() method that is
same as split() except that it scans the string from the end
working towards the beginning. See SF feature request 801847.
Add an entry for addition of {str,unicode}.rsplit.
2003-12-15 14:51:19 -04:00
Fixed a bug in object.__reduce_ex__ (reduce_2) when using protocol 2. Failure to clear the error when attempts to get the __getstate__ attribute fail caused intermittent errors and odd behavior.
2004-02-08 00:21:26 -04:00
- Fixed a bug in object.__reduce_ex__ when using protocol 2. Failure
to clear the error when attempts to get the __getstate__ attribute
fail caused intermittent errors and odd behavior.
Make buffer objects based on mutable objects (like array) safe.
2004-03-10 22:42:45 -04:00
- buffer objects based on other objects no longer cache a pointer to
the data and the data length. Instead, the appropriate tp_as_buffer
SF patch 959726: sdist versus SVN The disutils sdist command now ignores .svn directories.
2004-05-31 16:27:59 -03:00
method is called as necessary.
Make buffer objects based on mutable objects (like array) safe.
2004-03-10 22:42:45 -04:00
SF patch 959726: sdist versus SVN The disutils sdist command now ignores .svn directories.
2004-05-31 16:27:59 -03:00
- fixed: if a file is opened with an explicit buffer size >= 1, repeated
If a file is opened with an explicit buffer size >= 1, repeated close() calls would attempt to free() the buffer already free()ed on the first close(). [bug introduced with patch #788249] Making sure that the buffer is free()ed in file object deallocation is a belt-n-braces bit of insurance against a memory leak.
2004-04-04 04:01:35 -03:00
close() calls would attempt to free() the buffer already free()ed on
the first call.
Make buffer objects based on mutable objects (like array) safe.
2004-03-10 22:42:45 -04:00
add skeletal "what's new" for 2.4a1 and mention a couple python-mode tweaks.
2003-08-01 02:01:54 -03:00
Extension modules
-----------------
Warn abou missing mutate flag to ioctl. Fixes #696535.
2004-06-03 09:47:26 -03:00
- fcntl.ioctl now warns if the mutate flag is not specified.
Patch #954115: Fix os.stat handling of UNC roots. Will backport to 2.3.
2004-06-02 06:57:56 -03:00
- nt now properly allows to refer to UNC roots, e.g. in nt.stat().
Add weakref support to sockets and re pattern objects.
2004-05-31 00:09:25 -03:00
- the weakref module now supports additional objects: array.array,
sre.pattern_objects, file objects, and sockets.
Improve accuracy of sequence and mapping checks.
2004-04-04 05:51:41 -03:00
- operator.isMappingType() and operator.isSequenceType() now give
fewer false positives.
Make socket.sslerror a subclass of socket.error . Added socket.error to the socket module's C API.
2004-03-23 19:16:54 -04:00
- socket.sslerror is now a subclass of socket.error . Also added
socket.error to the socket module's C API.
Bug #920575: Add a workaround for GNU libc nl_langinfo()'s returning NULL. (Reported by Matthias Klose)
2004-03-21 15:34:30 -04:00
- Bug #920575: A problem that _locale module segfaults on
nl_langinfo(ERA) caused by GNU libc's illegal NULL return is fixed.
Update the array overallocation scheme to match the approach used for lists. Speeds append() operations and reduces memory requirements (because of more conservative overallocation). Paves the way for the feature request for array.extend() to support arbitrary iterable arguments.
2004-03-14 00:37:50 -04:00
- array objects now support the copy module. Also, their resizing
scheme has been updated the same as for list objects. The improves
SF feature request #686323: Minor array module enhancements array.extend() now accepts iterable arguments implements as a series of appends. Besides being a user convenience and matching the behavior for lists, this the saves memory and cycles that would be used to create a temporary array object.
2004-03-14 01:43:59 -04:00
the performance (speed and memory usage) of append() operations.
Also, array.extend() now accepts any iterable argument for repeated
appends without needing to create another temporary array.
SF bug #910986: copy.copy fails for array.array Added support for the copy module.
2004-03-13 14:18:51 -04:00
SF patch #907403: Improvements to cStringIO.writelines() The writelines() method now accepts any iterable argument and writes the lines one at a time rather than using ''.join(lines) followed by a single write. Results in considerable memory savings and makes the method suitable for use with generator expressions.
2004-03-08 14:22:35 -04:00
- cStringIO.writelines() now accepts any iterable argument and writes
the lines one at a time rather than joining them and writing once.
Made a parallel change to StringIO.writelines(). Saves memory and
makes suitable for use with generator expressions.
Have strftime() check its time tuple argument to make sure the tuple's values are within proper boundaries as specified in the docs. This can break possible code (datetime module needed changing, for instance) that uses 0 for values that need to be greater 1 or greater (month, day, and day of year). Fixes bug #897625.
2004-03-02 00:38:10 -04:00
- time.strftime() now checks that the values in its time tuple argument
are within the proper boundaries to prevent possible crashes from the
platform's C library implementation of strftime(). Can possibly
break code that uses values outside the range that didn't cause
problems previously (such as sitting day of year to 0). Fixes bug
#897625.
Patch #874083: Bluetooth support for socket module.
2004-01-31 08:34:17 -04:00
- The socket module now supports Bluetooth sockets, if the
system has <bluetooth/bluetooth.h>
* Move collections.deque() in from the sandbox * Add unittests, newsitem, and whatsnew * Apply to Queue.py mutex.py threading.py pydoc.py and shlex.py * Docs are forthcoming
2004-01-29 02:37:52 -04:00
- Added a collections module containing a new datatype, deque(),
offering high-performance, thread-safe, memory friendly appends
and pops on either side of the deque.
- Several modules now take advantage of collections.deque() for
improved performance: Queue, mutex, shlex, threading, and pydoc.
As discussed on python-dev, added two extractor functions to the operator module.
2003-12-01 09:18:39 -04:00
- The operator module has two new functions, attrgetter() and
itemgetter() which are useful for creating fast data extractor
functions for map(), list.sort(), itertools.groupby(), and
other functions that expect a function argument.
Patch #849595: Add socket.shutdown() constants.
2003-11-27 15:40:22 -04:00
- socket.SHUT_{RD,WR,RDWR} was added.
Patch #798297: Add IMAP THREAD command.
2003-11-10 02:44:44 -04:00
- os.getsid was added.
- The pwd module incorrectly advertised its struct type as struct_pwent; this has been renamed to struct_passwd. (The old name is still supported for backwards compatibility.)
2003-10-23 20:54:57 -03:00
- The pwd module incorrectly advertised its struct type as
struct_pwent; this has been renamed to struct_passwd. (The old name
is still supported for backwards compatibility.)
Note the update to Expat 1.95.7.
2003-10-21 12:41:59 -03:00
- The xml.parsers.expat module now provides Expat 1.95.7.
Patch #813445: Add IPPROTO_IPV6 option to the socketmodule.
2003-10-03 10:57:37 -03:00
- socket.IPPROTO_IPV6 was added.
Patch #800697: Add readline.clear_history.
2003-09-20 13:08:33 -03:00
- readline.clear_history was added.
select.select() now accepts a sequence (as defined by PySequence_Fast()) for its first three arguments. Closes RFE #798046 .
2003-09-10 16:37:42 -03:00
- select.select() now accepts sequences for its first three arguments.
SF bug #770485: cStringIO does not set closed attr
2003-08-08 09:20:03 -03:00
- cStringIO now supports the f.closed attribute.
forgot to commit this - note about the signal module SIGRT(MIN,MAX)
2003-08-05 03:33:56 -03:00
- The signal module now exposes SIGRTMIN and SIGRTMAX (if available).
[Patch #739124] Add use_default_colors() to curses module
2003-08-13 20:11:04 -03:00
- curses module now supports use_default_colors(). [patch #739124]
two bugfixes
2003-10-04 05:04:04 -03:00
- Bug #811028: ncurses.h breakage on FreeBSD/MacOS X
- Bug #814613: INET_ADDRSTRLEN fix needed for all compilers on SGI
Implemented non-recursive SRE matching.
2003-10-17 19:13:16 -03:00
- Implemented non-recursive SRE matching scheme (#757624).
- Implemented (?(id/name)yes|no) support in SRE (#572936).
Added itertools.tee() It works like the pure python verion except: * it stops storing data after of the iterators gets deallocated * the data queue is implemented with two stacks instead of one dictionary.
2003-10-24 05:45:23 -03:00
- random.seed() with no arguments or None uses time.time() as a default
seed. Modified to match Py2.2 behavior and use fractional seconds so
that successive runs are more likely to produce different sequences.
- random.Random has a new method, getrandbits(k), which returns an int
with k random bits. This method is now an optional part of the API
for user defined generators. Any generator that defines genrandbits()
can now use randrange() for ranges with a length >= 2**53. Formerly,
randrange would return only even numbers for ranges that large (see
SF bug #812202). Generators that do not define genrandbits() now
issue a warning when randrange() is called with a range that large.
Implement itertools.groupby() Original idea by Guido van Rossum. Idea for skipable inner iterators by Raymond Hettinger. Idea for argument order and identity function default by Alex Martelli. Implementation by Hye-Shik Chang (with tweaks by Raymond Hettinger).
2003-12-06 12:23:06 -04:00
- itertools has a new function, groupby() for aggregating iterables
into groups sharing the same key (as determined by a key function).
It offers some of functionality of SQL's groupby keyword and of
the Unix uniq filter.
Fixed a caching bug in platform.platform() where the argument of 'terse' was not taken into consideration when caching value.
2004-03-25 12:55:12 -04:00
Added itertools.tee() It works like the pure python verion except: * it stops storing data after of the iterators gets deallocated * the data queue is implemented with two stacks instead of one dictionary.
2003-10-24 05:45:23 -03:00
- itertools now has a new function, tee() which produces two independent
iterators from a single iterable.
- itertools.izip() with no arguments now returns an empty iterator instead
of raising a TypeError exception.
- Fixed #853061: allow BZ2Compressor.compress() to receive an empty string as parameter.
2004-02-13 20:02:45 -04:00
- Fixed #853061: allow BZ2Compressor.compress() to receive an empty string
as parameter.
add skeletal "what's new" for 2.4a1 and mention a couple python-mode tweaks.
2003-08-01 02:01:54 -03:00
Library
-------
SF #877165: Give an info about what C++ compiler command should be used in cygwin and mingw32. (Reported by Michael Droettboom)
2004-06-05 15:37:53 -03:00
- Fixed #877165: distutils now picks the right C++ compiler command
on cygwin and mingw32.
Fix a bug that robotparser starves memory when the server responses in HTTP/0.9 due to dissonance of httplib.LineAndFileWrapper and urllib.addbase.
2004-06-05 10:30:56 -03:00
- urllib.urlopen().readline() now handles HTTP/0.9 correctly.
Refactored site.py into functions. Also moved over to using sets. New regression test suite.
2004-06-04 22:12:51 -03:00
- refactored site.py into functions. Also wrote regression tests for the
module.
Patch #957240: Add count parameter to asyncore.loop.
2004-06-03 06:18:35 -03:00
- asyncore.loop now has repeat count parameter that defaults to infinity.
SF patch 959726: sdist versus SVN The disutils sdist command now ignores .svn directories.
2004-05-31 16:27:59 -03:00
- The distutils sdist command now ignores all .svn directories, in
addition to CVS and RCS directories. .svn directories hold
administrative files for the Subversion source control system.
Patch #963318: Add support for client-side cookie management.
2004-05-31 15:22:40 -03:00
- Added a new module: cookielib. Automatic cookie handling for HTTP
clients. Also, support for cookielib has been added to urllib2, so
urllib2.urlopen() can transparently handle cookies.
SF bug #949329: sets.Set() --> set()
2004-05-19 16:56:44 -03:00
- stringprep.py now uses built-in set() instead of sets.Set().
Fix SF item #876278: Unbounded recursion in modulefinder. Already backported to release23-maint.
2004-05-11 12:10:59 -03:00
- Bug #876278: Unbounded recursion in modulefinder
Swap public and system ID in start_doctype_decl. Fixes #780300.
2004-05-05 22:54:36 -03:00
- Bug #780300: Swap public and system ID in LexicalHandler.startDTD.
Applications relying on the wrong order need to be corrected.
SF #926075: Fixed the bug that returns a wrong pattern object for a string or unicode object in sre.compile() when a different type pattern with the same value exists.
2004-04-20 18:11:11 -03:00
- Bug #926075: Fixed a bug that returns a wrong pattern object
for a string or unicode object in sre.compile() when a different
type pattern with the same value exists.
note --trackcalls flag in trace module
2004-04-07 13:03:02 -03:00
- Added countcallers arg to trace.Trace class (--trackcalls command line arg
when run from the command prompt).
Fixed a caching bug in platform.platform() where the argument of 'terse' was not taken into consideration when caching value.
2004-03-25 12:55:12 -04:00
- Fixed a caching bug in platform.platform() where the argument of 'terse' was
not taken into consideration when caching value.
Added command line options for profile.py - one for stats output file and one for sort order when using stdout. Uses optparse.
2004-03-23 14:44:39 -04:00
- Added two new command-line arguments for profile (output file and
default sort).
Added global runctx function to profile to fix SF Bug #716587
2004-03-22 16:12:56 -04:00
- Added global runctx function to profile module
Patch #853488: Tix hlist missing entryconfigure and entrycget methods.
2004-03-21 11:29:41 -04:00
- Add hlist missing entryconfigure and entrycget methods.
Add an entry for addition of the ptcp154 codec.
2004-03-19 04:11:56 -04:00
- The ptcp154 codec was added for Kazakh character set support.
Patch #711838: Allow non-anonymous ftp urls in urllib2. Backported to 2.3.
2004-02-15 17:19:18 -04:00
- Support non-anonymous ftp URLs in urllib2.
Add news item about change in encodings search function.
2004-01-20 14:24:34 -04:00
- The encodings package will now applies codec name aliases
first before starting to try the import of the codec module.
This simplifies overriding built-in codecs with external
packages, e.g. the included CJK codecs with the JapaneseCodecs
package, by adjusting the aliases dictionary in encodings.aliases
accordingly.
Add note about new base64.py module support for RFC 3548.
2004-01-03 21:13:43 -04:00
- base64 now supports RFC 3548 Base16, Base32, and Base64 encoding and
decoding standards.
Add news item about processor support in urllib2.
2003-12-14 01:29:45 -04:00
- urllib2 now supports processors. A processor is a handler that
implements an xxx_request or xxx_response method. These methods are
called for all requests.
distutils compilers now compile source files in the same order as they are passed to the compiler.
2003-12-05 16:28:07 -04:00
- distutils compilers now compile source files in the same order as
they are passed to the compiler.
Add parameters indent, width and depth to pprint.pprint() and pprint.pformat() and pass them along to the PrettyPrinter constructor.
2003-12-03 16:26:05 -04:00
- pprint.pprint() and pprint.pformat() now have additional parameters
indent, width and depth.
Patch #750542: pprint now will pretty print subclasses of list, tuple and dict too, as long as they don't overwrite __repr__().
2003-12-03 16:15:28 -04:00
- Patch #750542: pprint now will pretty print subclasses of list, tuple
and dict too, as long as they don't overwrite __repr__().
See SF #848614: distutils' msvccompiler now tries to detect that MSVC6 is installed but the registry settings are incomplete because the gui has never been run. Already backported to release23-maint.
2003-11-28 15:42:56 -04:00
- Bug #848614: distutils' msvccompiler fails to find the MSVC6
compiler because of incomplete registry entries.
Patch #831747: Add skip_accept_encoding parameter to putrequest.
2003-11-19 15:51:55 -04:00
- httplib.HTTP.putrequest now offers to omit the implicit Accept-Encoding.
Mention patch #841977: modulefinder didn't find extension modules in packages Backported to release-maint23
2003-11-14 06:33:20 -04:00
- Patch #841977: modulefinder didn't find extension modules in packages
Patch #798297: Add IMAP THREAD command.
2003-11-10 02:44:44 -04:00
- imaplib.IMAP4.thread was added.
Plug tempfile.mktemp() hole (Iustin Pop).
2003-11-09 22:27:19 -04:00
- Plugged a minor hole in tempfile.mktemp() due to the use of
os.path.exists(), switched to using os.lstat() directly if possible.
SF Patch #864863: Bisect C implementation (Contributed by Dmitry Vasiliev.)
2004-01-05 06:13:35 -04:00
- bisect.py and heapq.py now have underlying C implementations
for better performance
Convert heapq.py to a C implementation.
2003-11-08 06:24:38 -04:00
Add traceback.format_exc().
2003-11-05 19:03:00 -04:00
- traceback.format_exc has been added (similar to print_exc but it returns
a string).
Patch #531629: Add multicall support.
2003-10-31 09:49:36 -04:00
- xmlrpclib.MultiCall has been added.
Patch #: Add POP3 over SSL support.
2003-10-31 08:52:35 -04:00
- poplib.POP3_SSL has been added.
Patch #810914: Return absolute path for mkstemp. Fixes #810408. This should not be backported to 2.3, as it might break backwards compatibility.
2003-10-12 14:37:01 -03:00
- tmpfile.mkstemp now returns an absolute path even if dir is relative.
Add mention of urlparse becoming RFC 2396 compliant.
2003-10-12 01:38:48 -03:00
- urlparse is RFC 2396 compliant.
forgot the NEWS blurb about the change to csv.DictReader
2003-10-03 11:07:07 -03:00
- The fieldnames argument to the csv module's DictReader constructor is now
optional. If omitted, the first row of the file will be used as the
list of fieldnames.
Added codec for bz2 compression.
2003-09-23 17:21:01 -03:00
- encodings.bz2_codec was added for access to bz2 compression
using "a long string".encode('bz2')
New for unittest.py.
2003-09-22 12:03:11 -03:00
- Various improvements to unittest.py, realigned with PyUnit CVS.
Patch #707167: Pass dircache exceptions to the caller. Fixes #682813. Not backported because of behaviour change.
2003-09-20 12:52:21 -03:00
- dircache now passes exceptions to the caller, instead of returning
empty lists.
SF #662923 Add support for the iterator and mapping protocols. For Py2.3, this was done for shelve, dumbdbm and other mapping objects, but not for bsddb and dbhash which were inadvertently missed.
2003-09-12 03:33:37 -03:00
- The bsddb module and dbhash module now support the iterator and
mapping protocols which make them more substitutable for dictionaries
and shelves.
**kwds arg was missing from __init__ for Dict{Reader,Writer} classes. will backport.
2003-09-06 16:52:12 -03:00
- The csv module's DictReader and DictWriter classes now accept keyword
arguments. This was an omission in the initial implementation.
Describe the fix to the email package.
2003-08-19 00:59:09 -03:00
- The email package handles some RFC 2231 parameters with missing
NEWS about email package 794466 patch.
2003-09-03 01:09:49 -03:00
CHARSET fields better. It also includes a patch to parameter
parsing when semicolons appear inside quotes.
Describe the fix to the email package.
2003-08-19 00:59:09 -03:00
Improvements to set.py: * Relaxed the argument restrictions for non-operator methods. They now allow any iterable instead of requiring a set. This makes the module a little easier to use and paves the way for an efficient C implementation which can take better advantage of iterable arguments while screening out immutables. * Deprecated Set.update() because it now duplicates Set.union_update() * Adapted the tests and docs to include the above changes. * Added more test coverage including testing identities and checking to make sure non-restartable generators work as arguments. Will backport to Py2.3.1 so that the interface remains consistent across versions. The deprecation of update() will be changed to a FutureWarning.
2003-08-17 05:34:09 -03:00
- sets.py now runs under Py2.2. In addition, the argument restrictions
for most set methods (but not the operators) have been relaxed to
Remove deprecation of sets.Set.update().
2003-11-19 11:52:14 -04:00
allow any iterable.
Make sets.py compatible with Py2.2
2003-08-15 18:17:04 -03:00
Removed deprecated functions
2003-08-05 09:32:41 -03:00
- _strptime.py now has a behind-the-scenes caching mechanism for the most
Mention caching and better thread-safety for Lib/_strptime.py
2003-08-05 03:27:04 -03:00
recent TimeRE instance used along with the last five unique directive
patterns. The overall module was also made more thread-safe.
Removed deprecated functions
2003-08-05 09:32:41 -03:00
- random.cunifvariate() and random.stdgamma() were deprecated in Py2.3
and removed in Py2.4.
missing news entry
2003-11-04 10:35:49 -04:00
- Bug #823328: urllib2.py's HTTP Digest Auth support works again.
Add a news entry for importing of CJK codecs.
2004-01-17 10:59:36 -04:00
- Patch #873597: CJK codecs are imported into rank of default codecs.
add skeletal "what's new" for 2.4a1 and mention a couple python-mode tweaks.
2003-08-01 02:01:54 -03:00
Tools/Demos
-----------
add hotshotmain ref
2004-01-27 10:49:04 -04:00
- A hotshotmain script was added to the Tools/scripts directory that
makes it easy to run a script under control of the hotshot profiler.
note db2pickle/pickle2db tweaks
2003-10-28 12:24:00 -04:00
- The db2pickle and pickle2db scripts can now dump/load gdbm files.
* explain flags in doc strings * reverse order of files on the command line in pickle2db.py to make it symmetrical with db2pickle.py in the two-arg case (src, then dest)
2004-03-03 13:42:08 -04:00
- The file order on the command line of the pickle2db script was reversed.
It is now [ picklefile ] dbfile. This provides better symmetry with
db2pickle. The file arguments to both scripts are now source followed by
destination in situations where both files are given.
mention new module doc display feature of pydoc in libref and NEWS
2003-09-10 16:04:13 -03:00
- The pydoc script will display a link to the module documentation for
modules determined to be part of the core distribution. The documentation
base directory defaults to http://www.python.org/doc/current/lib/ but can
be changed by setting the PYTHONDOCS environment variable.
Added doubled word warnings.
2003-08-25 01:39:55 -03:00
- texcheck.py now detects double word errors.
This started opening files in text mode by default in the 2.3 release, which is a disaster on Windows. Restored the binary default of all previous releases. Also minor code cleanups. Bugfix candidate!
2003-08-18 20:52:09 -03:00
- md5sum.py mistakenly opened input files in text mode by default, a
silent and dangerous change from previous releases. It once again
opens input files in binary mode by default. The -t and -b flags
remain for compatibility with the 2.3 release, but -b is the default
now.
add skeletal "what's new" for 2.4a1 and mention a couple python-mode tweaks.
2003-08-01 02:01:54 -03:00
- py-electric-colon now works when pending-delete/delete-selection mode is
in effect
- py-help-at-point is no longer bound to the F1 key - it's still bound to
C-c C-h
Document the Pynche patch.
2003-09-03 00:20:37 -03:00
- Pynche was fixed to not crash when there is no ~/.pynche file and no
-d option was given.
add skeletal "what's new" for 2.4a1 and mention a couple python-mode tweaks.
2003-08-01 02:01:54 -03:00
Build
-----
Patch #926209: Patch to setup.py to run on x86_64 Linux.
2004-06-04 10:55:13 -03:00
- In order to find libraries, setup.py now also looks in /lib64, for use
on AMD64.
Bug #934635: Fix a bug where the configure script couldn't detect getaddrinfo() properly if the KAME stack had SCTP support. (Submitted by SUZUKI Shinsuke)
2004-04-14 04:55:31 -03:00
- Bug #934635: Fixed a bug where the configure script couldn't detect
getaddrinfo() properly if the KAME stack had SCTP support.
remove support for missing ANSI C header files (limits.h, stddef.h, etc).
2004-02-10 12:50:21 -04:00
- Support for missing ANSI C header files (limits.h, stddef.h, etc) was
removed.
Remove support for --without-universal-newlines (see PEP 11).
2004-02-07 09:53:46 -04:00
- Systems requiring the D4, D6 or D7 variants of pthreads are no longer
supported (see PEP 11).
- Universal newline support can no longer be disabled (see PEP 11).
document PEP 11 progress so far.
2004-01-17 10:22:44 -04:00
- Support for DGUX, SunOS 4, IRIX 4 and Minix was removed (see PEP 11).
- Support for systems requiring --with-dl-dld or --with-sgi-dl was removed
(see PEP 11).
- Tests for sizeof(char) were removed since ANSI C mandates that
sizeof(char) must be 1.
add skeletal "what's new" for 2.4a1 and mention a couple python-mode tweaks.
2003-08-01 02:01:54 -03:00
C API
-----
Patch #957398: Add public API for Generator Object/Type.
2004-06-01 12:22:42 -03:00
- New public functions PyEval_EvaluateFrame and PyGen_New to expose
generator objects.
Two new public API functions, Py_IncRef and Py_DecRef. Useful for dynamic embedders of Python.
2004-04-22 14:23:49 -03:00
- New public functions Py_IncRef() and Py_DecRef(), exposing the
functionality of the Py_XINCREF() and Py_XDECREF macros. Useful for
Forgot to mention the SF number, and that Bob Ippolito provided the patch.
2004-04-22 14:28:25 -03:00
runtime dynamic embedding of Python. See patch #938302, by Bob
Ippolito.
Two new public API functions, Py_IncRef and Py_DecRef. Useful for dynamic embedders of Python.
2004-04-22 14:23:49 -03:00
Use a new macro, PySequence_Fast_ITEMS to factor out code common to three recent optimizations. Aside from reducing code volume, it increases readability.
2004-03-12 04:04:00 -04:00
- Added a new macro, PySequence_Fast_ITEMS, which retrieves a fast sequence's
underlying array of PyObject pointers. Useful for high speed looping.
* Added a new method flag, METH_COEXIST. * Used the flag to optimize set.__contains__(), dict.__contains__(), dict.__getitem__(), and list.__getitem__().
2003-12-13 07:26:12 -04:00
- Created a new method flag, METH_COEXIST, which causes a method to be loaded
even if already defined by a slot wrapper. This allows a __contains__
method, for example, to co-exist with a defined sq_contains slot. This
is helpful because the PyCFunction can take advantage of optimized calls
whenever METH_O or METH_NOARGS flags are defined.
Expose dict_contains() and PyDict_Contains() with is about 10% faster than PySequence_Contains() and more clearly applicable to dicts. Apply the new function in setobject.c where __contains__ checking is ubiquitous.
2003-11-25 17:12:14 -04:00
- Added a new function, PyDict_Contains(d, k) which is like
PySequence_Contains() but is specific to dictionaries and executes
about 10% faster.
Modified the Py_RETURN_* macros by having the statements surrounded by {} in order to prevent any unexpected surprises from someone using them in a conditional without using curly braces (e.g., ``if (foo) Py_RETURN_TRUE``.
2003-10-19 18:31:43 -03:00
- Added three new macros: Py_RETURN_NONE, Py_RETURN_TRUE, and Py_RETURN_FALSE.
Each return the singleton they mention after Py_INCREF()ing them.
Extended tuple's C API to include a new function, PyTuple_Pack() that is useful for rapidly building argument tuples without having to invoke the more sophisticated machinery of Py_BuildValue().
2003-10-12 15:24:34 -03:00
- Added a new function, PyTuple_Pack(n, ...) for constructing tuples from a
variable length argument list of Python objects without having to invoke
the more complex machinery of Py_BuildValue(). PyTuple_Pack(3, a, b, c)
is equivalent to Py_BuildValue("(OOO)", a, b, c).
add skeletal "what's new" for 2.4a1 and mention a couple python-mode tweaks.
2003-08-01 02:01:54 -03:00
New platforms
-------------
Tests
-----
Windows
-------
Add news item for _winreg fix (SF bug 851056).
2003-11-30 18:10:15 -04:00
- The _winreg module could segfault when reading very large registry
values, due to unchecked alloca() calls (SF bug 851056). The fix is
uses either PyMem_Malloc(n) or PyString_FromStringAndSize(NULL, n),
as appropriate, followed by a size check.
SF bug 801631: file.truncate fault on windows. file_truncate(): C doesn't define what fflush(fp) does if fp is open for update, and the preceding I/O operation on fp was input. On Windows, fflush() actually changes the current file position then. Because Windows doesn't support ftruncate() directly, this not only caused Python's file.truncate() to change the file position (contra our docs), it also caused the file not to change size. Repaired by getting the initial file position at the start, restoring it at the end, and tossing all the complicated micro-efficiency checks trying to avoid "provably unnecessary" seeks. file.truncate() can't be a frequent operation, and seeking to the current file position has got to be cheap anyway. Bugfix candidate.
2003-09-07 00:30:18 -03:00
- file.truncate() could misbehave if the file was open for update
(modes r+, rb+, w+, wb+), and the most recent file operation before
the truncate() call was an input operation. SF bug 801631.
add skeletal "what's new" for 2.4a1 and mention a couple python-mode tweaks.
2003-08-01 02:01:54 -03:00
Mac
----
Added section for 2.3 final; moved IDLE news into it that I inserted in a wrong place over the weekend.
2003-07-28 21:10:29 -03:00
What's New in Python 2.3 final?
===============================
*Release date: 29-Jul-2003*
IDLE
----
SF bug 778400: IDLE hangs when selecting "Edit with IDLE". The fix is confined to the Windows installer. Not a bugfix candidate: the need for the new -n switch added here was introduced by moving to the idlefork IDLE (so this change isn't needed or helpful before 2.3).
2003-07-29 14:22:57 -03:00
- Bug 778400: IDLE hangs when selecting "Edit with IDLE" from explorer.
This was unique to Windows, and was fixed by adding an -n switch to
the command the Windows installer creates to execute "Edit with IDLE"
context-menu actions.
Added section for 2.3 final; moved IDLE news into it that I inserted in a wrong place over the weekend.
2003-07-28 21:10:29 -03:00
- IDLE displays a new message upon startup: some "personal firewall"
kinds of programs (for example, ZoneAlarm) open a dialog of their
own when any program opens a socket. IDLE does use sockets, talking
on the computer's internal loopback interface. This connection is not
visible on any external interface and no data is sent to or received
from the Internet. So, if you get such a dialog when opening IDLE,
asking whether to let pythonw.exe talk to address 127.0.0.1, say yes,
and rest assured no communication external to your machine is taking
place. If you don't allow it, IDLE won't be able to start.
Merge 23c1-branch back into the head. Barry will send email about the New Plan (releases to be made off the head, ongoing random 2.4 stuff to be done on a short-lived branch, provided anyone is motivated enough to create one).
2003-07-21 11:25:23 -03:00
What's New in Python 2.3 release candidate 2?
=============================================
Update version numbers and dates for 2.3c2 -- we won't be able to do this during the day tomorrow, so doing it earlier than I'd like.
2003-07-23 21:15:46 -03:00
*Release date: 24-Jul-2003*
Merge 23c1-branch back into the head. Barry will send email about the New Plan (releases to be made off the head, ongoing random 2.4 stuff to be done on a short-lived branch, provided anyone is motivated enough to create one).
2003-07-21 11:25:23 -03:00
Core and builtins
-----------------
Change the zipimport implementation to accept files containing arbitrary bytes before the actual zip compatible archive. Zipfiles containing comments at the end of the file are still not supported. Add a testcase to test_zipimport, and update NEWS. This closes sf #775637 and sf #669036.
2003-07-22 15:10:15 -03:00
- It is now possible to import from zipfiles containing additional
Updated news for 2.3c2.
2003-07-24 22:09:40 -03:00
data bytes before the zip compatible archive. Zipfiles containing a
Change the zipimport implementation to accept files containing arbitrary bytes before the actual zip compatible archive. Zipfiles containing comments at the end of the file are still not supported. Add a testcase to test_zipimport, and update NEWS. This closes sf #775637 and sf #669036.
2003-07-22 15:10:15 -03:00
comment at the end are still unsupported.
Merge 23c1-branch back into the head. Barry will send email about the New Plan (releases to be made off the head, ongoing random 2.4 stuff to be done on a short-lived branch, provided anyone is motivated enough to create one).
2003-07-21 11:25:23 -03:00
Extension modules
-----------------
- A longstanding bug in the parser module's initialization could cause
fatal internal refcount confusion when the module got initialized more
than once. This has been fixed.
Added note about the pyexpat memory leak fix.
2003-07-21 14:17:10 -03:00
- Fixed memory leak in pyexpat; using the parser's ParseFile() method
with open files that aren't instances of the standard file type
caused an instance of the bound .read() method to be leaked on every
call.
Updated news for 2.3c2.
2003-07-24 22:09:40 -03:00
- Fixed some leaks in the locale module.
Merge 23c1-branch back into the head. Barry will send email about the New Plan (releases to be made off the head, ongoing random 2.4 stuff to be done on a short-lived branch, provided anyone is motivated enough to create one).
2003-07-21 11:25:23 -03:00
Library
-------
Updated news for 2.3c2.
2003-07-24 22:09:40 -03:00
- Lib/encodings/rot_13.py when used as a script, now more properly
uses the first Python interpreter on your path.
- Removed caching of TimeRE (and thus LocaleTime) in _strptime.py to
fix a locale related bug in the test suite. Although another patch
was needed to actually fix the problem, the cache code was not
restored.
Gave the main NEWS file its own IDLE section, and populated it with a blurb about ZoneAlarm (etc) nags.
2003-07-27 17:23:49 -03:00
IDLE
----
- Calltips patches.
Updated news for 2.3c2.
2003-07-24 22:09:40 -03:00
Merge 23c1-branch back into the head. Barry will send email about the New Plan (releases to be made off the head, ongoing random 2.4 stuff to be done on a short-lived branch, provided anyone is motivated enough to create one).
2003-07-21 11:25:23 -03:00
Build
-----
Updated news for 2.3c2.
2003-07-24 22:09:40 -03:00
- For MacOSX, added -mno-fused-madd to BASECFLAGS to fix test_coercion
on Panther (OSX 10.3).
Merge 23c1-branch back into the head. Barry will send email about the New Plan (releases to be made off the head, ongoing random 2.4 stuff to be done on a short-lived branch, provided anyone is motivated enough to create one).
2003-07-21 11:25:23 -03:00
C API
-----
Windows
-------
Windows fix: When PYTHONCASEOK is set, or for any other reason imports are satisfied in a case-insensitive manner, the attempt to import (the non-existent) fcntl gets satisfied by FCNTL.py instead, and the tempfile module defines a Unix-specific _set_cloexec() function in that case. As a result, temp files can't be created then (blows up with an AttributeError trying to reference fcntl.fcntl). This just popped up in the spambayes project, where there is no apparent workaround (which is why I'm pushing this in now).
2003-07-21 23:50:01 -03:00
- The tempfile module could do insane imports on Windows if PYTHONCASEOK
was set, making temp file creation impossible. Repaired.
Updated news for 2.3c2.
2003-07-24 22:09:40 -03:00
- Add a patch to workaround pthread_sigmask() bugs in Cygwin.
Merge 23c1-branch back into the head. Barry will send email about the New Plan (releases to be made off the head, ongoing random 2.4 stuff to be done on a short-lived branch, provided anyone is motivated enough to create one).
2003-07-21 11:25:23 -03:00
Mac
---
Updated news for 2.3c2.
2003-07-24 22:09:40 -03:00
- Various fixes to pimp.
- Scripts runs with pythonw no longer had full window manager access.
- Don't force boot-disk-only install, for reasons unknown it causes
more problems than it solves.
Merge 23c1-branch back into the head. Barry will send email about the New Plan (releases to be made off the head, ongoing random 2.4 stuff to be done on a short-lived branch, provided anyone is motivated enough to create one).
2003-07-21 11:25:23 -03:00
Partial progress on NEWS.
2003-07-17 14:57:58 -03:00
What's New in Python 2.3 release candidate 1?
=============================================
Fix SF 762891: "del p[key]" on proxy object raises SystemError()
2003-06-30 01:18:48 -03:00
Forgot the release date.
2003-07-18 17:10:02 -03:00
*Release date: 18-Jul-2003*
Fix SF 762891: "del p[key]" on proxy object raises SystemError()
2003-06-30 01:18:48 -03:00
Core and builtins
-----------------
New function sys.getcheckinterval(), to complement setcheckinterval().
2003-07-06 15:36:54 -03:00
- The new function sys.getcheckinterval() returns the last value set
by sys.setcheckinterval().
Partial progress on NEWS.
2003-07-17 14:57:58 -03:00
- Several bugs in the symbol table phase of the compiler have been
fixed. Errors could be lost and compilation could fail without
The rest of the news.
2003-07-17 16:19:05 -03:00
reporting an error. SF patch 763201.
Partial progress on NEWS.
2003-07-17 14:57:58 -03:00
- The interpreter is now more robust about importing the warnings
module. In an executable generated by freeze or similar programs,
earlier versions of 2.3 would fail if the warnings module could
The rest of the news.
2003-07-17 16:19:05 -03:00
not be found on the file system. Fixes SF bug 771097.
Partial progress on NEWS.
2003-07-17 14:57:58 -03:00
- A warning about assignments to module attributes that shadow
builtins, present in earlier releases of 2.3, has been removed.
Merge 23c1-branch back into the head. Barry will send email about the New Plan (releases to be made off the head, ongoing random 2.4 stuff to be done on a short-lived branch, provided anyone is motivated enough to create one).
2003-07-21 11:25:23 -03:00
Partial progress on NEWS.
2003-07-17 14:57:58 -03:00
- It is not possible to create subclasses of builtin types like str
and tuple that define an itemsize. Earlier releases of Python 2.3
allowed this by mistake, leading to crashes and other problems.
- The thread_id is now initialized to 0 in a non-thread build. SF bug
The rest of the news.
2003-07-17 16:19:05 -03:00
770247.
- SF bug 762891: "del p[key]" on proxy object no longer raises SystemError.
Partial progress on NEWS.
2003-07-17 14:57:58 -03:00
Fix SF 762891: "del p[key]" on proxy object raises SystemError()
2003-06-30 01:18:48 -03:00
Extension modules
-----------------
- weakref.proxy() can now handle "del obj[i]" for proxy objects
defining __delitem__. Formerly, it generated a SystemError.
- SSL no longer crashes the interpreter when the remote side disconnects.
Add mmap bugfix; typo and grammar fixes
2003-07-16 17:11:34 -03:00
- On Unix the mmap module can again be used to map device files.
Make temporary change of using _strptime for time.strptime permanent. Flesh out docs to better explain time.strptime (closes bug #697990).
2003-07-01 02:16:08 -03:00
- time.strptime now exclusively uses the Python implementation
contained within the _strptime module.
Partial progress on NEWS.
2003-07-17 14:57:58 -03:00
- The print slot of weakref proxy objects was removed, because it was
not consistent with the object's repr slot.
- The mmap module only checks file size for regular files, not
The rest of the news.
2003-07-17 16:19:05 -03:00
character or block devices. SF patch 708374.
- The cPickle Pickler garbage collection support was fixed to traverse
the find_class attribute, if present.
Merge 23c1-branch back into the head. Barry will send email about the New Plan (releases to be made off the head, ongoing random 2.4 stuff to be done on a short-lived branch, provided anyone is motivated enough to create one).
2003-07-21 11:25:23 -03:00
- There are several fixes for the bsddb3 wrapper module.
The rest of the news.
2003-07-17 16:19:05 -03:00
bsddb3 no longer crashes if an environment is closed before a cursor
(SF bug 763298).
The DB and DBEnv set_get_returns_none function was extended to take
Minor typo
2003-07-20 15:00:54 -03:00
a level instead of a boolean flag. The new level 2 means that in
addition, cursor.set()/.get() methods return None instead of raising
an exception.
The rest of the news.
2003-07-17 16:19:05 -03:00
A typo was fixed in DBCursor.join_item(), preventing a crash.
Fix SF 762891: "del p[key]" on proxy object raises SystemError()
2003-06-30 01:18:48 -03:00
Library
-------
Partial progress on NEWS.
2003-07-17 14:57:58 -03:00
- distutils now supports MSVC 7.1
Doctest now examines all docstrings by default. Previously, it would skip over functions with private names (as indicated by the underscore naming convention). The old default created too much of a risk that user tests were being skipped inadvertently. Note, this change could break code in the unlikely case that someone had intentionally put failing tests in the docstrings of private functions. The breakage is easily fixable by specifying the old behavior when calling testmod() or Tester(). The more likely case is that the silent failure was unintended and that the user needed to be informed so the test could be fixed.
2003-07-16 16:25:22 -03:00
- doctest now examines all docstrings by default. Previously, it would
skip over functions with private names (as indicated by the underscore
naming convention). The old default created too much of a risk that
user tests were being skipped inadvertently. Note, this change could
break code in the unlikely case that someone had intentionally put
failing tests in the docstrings of private functions. The breakage
is easily fixable by specifying the old behavior when calling testmod()
or Tester().
Partial progress on NEWS.
2003-07-17 14:57:58 -03:00
- There were several fixes to the way dumbdbms are closed. It's vital
that a dumbdbm database be closed properly, else the on-disk data
and directory files can be left in mutually inconsistent states.
dumbdbm.py's _Database.__del__() method attempted to close the
database properly, but a shutdown race in _Database._commit() could
prevent this from working, so that a program trusting __del__() to
get the on-disk files in synch could be badly surprised. The race
has been repaired. A sync() method was also added so that shelve
can guarantee data is written to disk.
Make close() identical to __del__() for a dumbdbm database. Make closing idempotent (it used to raise a nuisance exception on the 2nd close attempt). Bugfix candidate? Probably, but arguable.
2003-07-13 14:21:10 -03:00
Partial progress on NEWS.
2003-07-17 14:57:58 -03:00
The close() method can now be called more than once without complaint.
Fixed critical shutdown race in _Database._commit. Related to SF patch 723231 (which pointed out the problem, but didn't fix it, just shut up the warning msg -- which was pointing out a dead- serious bug!). Bugfix candidate.
2003-07-12 23:22:03 -03:00
Make the classes exposed by threading.py new-style classes. This is mostly for convenience and to aid debugging.
2003-07-01 17:01:55 -03:00
- The classes in threading.py are now new-style classes. That they
weren't before was an oversight.
The rest of the news.
2003-07-17 16:19:05 -03:00
- The urllib2 digest authentication handlers now define the correct
auth_header. The earlier versions would fail at runtime.
Fix SF bug #763023, difflib.py: ratio() zero division not caught Backport candidate
2003-07-01 11:59:46 -03:00
- SF bug 763023: fix uncaught ZeroDivisionError in difflib ratio methods
when there are no lines.
Fix SF bug #763637, 2.3b2 unpack tuple of wrong size in after_cancel Tk 8.4 may return different values than 8.3. This fix should handle either version.
2003-07-01 18:12:47 -03:00
- SF bug 763637: fix exception in Tkinter with after_cancel
which could occur with Tk 8.4
Partial progress on NEWS.
2003-07-17 14:57:58 -03:00
- SF bug 770601: CGIHTTPServer.py now passes the entire environment
to child processes.
The rest of the news.
2003-07-17 16:19:05 -03:00
- SF bug 765238: add filter to fnmatch's __all__.
- SF bug 748201: make time.strptime() error messages more helpful.
- SF patch 764470: Do not dump the args attribute of a Fault object in
xmlrpclib.
- SF patch 549151: urllib and urllib2 now redirect POSTs on 301
responses.
- SF patch 766650: The whichdb module was fixed to recognize dbm files
generated by gdbm on OS/2 EMX.
- SF bugs 763047 and 763052: fixes bug of timezone value being left as
-1 when ``time.tzname[0] == time.tzname[1] and not time.daylight``
is true when it should only when time.daylight is true.
- SF bug 764548: re now allows subclasses of str and unicode to be
used as patterns.
- SF bug 763637: In Tkinter, change after_cancel() to handle tuples
of varying sizes. Tk 8.4 returns a different number of values
than Tk 8.3.
- SF bug 763023: difflib.ratio() did not catch zero division.
- The Queue module now has an __all__ attribute.
Partial progress on NEWS.
2003-07-17 14:57:58 -03:00
Fix SF 762891: "del p[key]" on proxy object raises SystemError()
2003-06-30 01:18:48 -03:00
Tools/Demos
-----------
The rest of the news.
2003-07-17 16:19:05 -03:00
- See Lib/idlelib/NEWS.txt for IDLE news.
SF bug 753592, websucker bug Pass the proper variable when the user supplies a directory. Will backport.
2003-07-01 01:14:28 -03:00
- SF bug 753592: webchecker/wsgui now handles user supplied directories.
The rest of the news.
2003-07-17 16:19:05 -03:00
- The trace.py script has been removed. It is now in the standard library.
Partial progress on NEWS.
2003-07-17 14:57:58 -03:00
Fix SF 762891: "del p[key]" on proxy object raises SystemError()
2003-06-30 01:18:48 -03:00
Build
-----
The rest of the news.
2003-07-17 16:19:05 -03:00
- Python now compiles with -fno-strict-aliasing if possible (SF bug 766696).
Partial progress on NEWS.
2003-07-17 14:57:58 -03:00
- The socket module compiles on IRIX 6.5.10.
The rest of the news.
2003-07-17 16:19:05 -03:00
- An irix64 system is treated the same way as an irix6 system (SF
patch 764560).
Partial progress on NEWS.
2003-07-17 14:57:58 -03:00
The rest of the news.
2003-07-17 16:19:05 -03:00
- Several definitions were missing on FreeBSD 5.x unless the
__BSD_VISIBLE symbol was defined. configure now defines it as
needed.
Partial progress on NEWS.
2003-07-17 14:57:58 -03:00
Fix SF 762891: "del p[key]" on proxy object raises SystemError()
2003-06-30 01:18:48 -03:00
C API
-----
The rest of the news.
2003-07-17 16:19:05 -03:00
- Unicode objects now support mbcs as a built-in encoding, so the C
API can use it without deferring to the encodings package.
Fix SF 762891: "del p[key]" on proxy object raises SystemError()
2003-06-30 01:18:48 -03:00
Windows
-------
The rest of the news.
2003-07-17 16:19:05 -03:00
- The Windows implementation of PyThread_start_new_thread() never
checked error returns from Windows functions correctly. As a result,
it could claim to start a new thread even when the Microsoft
_beginthread() function failed (due to "too many threads" -- this is
on the order of thousands when it happens). In these cases, the
Python exception ::
thread.error: can't start new thread
is raised now.
- SF bug 766669: Prevent a GPF on interpreter exit when sockets are in
use. The interpreter now calls WSACleanup() from Py_Finalize()
instead of from DLL teardown.
Fix SF 762891: "del p[key]" on proxy object raises SystemError()
2003-06-30 01:18:48 -03:00
Mac
---
The rest of the news.
2003-07-17 16:19:05 -03:00
- Bundlebuilder now inherits default values in the right way. It was
Fix typo.
2003-07-30 09:14:02 -03:00
previously possible for app bundles to get a type of "BNDL" instead
The rest of the news.
2003-07-17 16:19:05 -03:00
of "APPL." Other improvements include, a --build-id option to
specify the CFBundleIdentifier and using the --python option to set
the executable in the bundle.
- Fixed two bugs in MacOSX framework handling.
Fix SF 762891: "del p[key]" on proxy object raises SystemError()
2003-06-30 01:18:48 -03:00
Bugfix for #775892: added -mno-fused-madd to BASECFLAGS on MacOSX. This makes test_coercion pass on Panther. Also added a note to NEWS that pythonw works again (it was broken in rc1).
2003-07-23 19:17:28 -03:00
- pythonw did not allow user interaction in 2.3rc1, this has been fixed.
- Python is now compiled with -mno-fused-madd, making all tests pass
on Panther.
A start on news for 2.3b2.
2003-04-26 11:53:01 -03:00
What's New in Python 2.3 beta 2?
================================
Filled in release date; repaired grammar in a news item.
2003-06-29 13:18:08 -03:00
*Release date: 29-Jun-2003*
A start on news for 2.3b2.
2003-04-26 11:53:01 -03:00
Core and builtins
-----------------
Added news about os.environ['PYTHONINSPECT'] = 'yes'
2003-06-29 14:10:11 -03:00
- A program can now set the environment variable PYTHONINSPECT to some
string value in Python, and cause the interpreter to enter the
interactive prompt at program exit, as if Python had been invoked
with the -i option.
SF #754014: list.index() should accept optional start, end arguments Also, modified UserList.index() to match and expanded the related tests.
2003-06-17 02:05:49 -03:00
- list.index() now accepts optional start and stop arguments. Similar
changes were made to UserList.index(). SF feature request 754014.
News about the new IDLE (is more needed?). News about SF patch 751998.
2003-06-13 17:37:23 -03:00
- SF patch 751998 fixes an unwanted side effect of the previous fix
for SF bug 742860 (the next item).
Fleshed out WeakKeyDictionary.__delitem__ NEWS to cover issues raised on Python-Dev. Fixed typos in test comments. Added some trivial new test guts to show the parallelism (now) among __delitem__, __setitem__ and __getitem__ wrt error conditions. Still a bugfix candidate for 2.2.3 final, but waiting for Fred to get a chance to chime in.
2003-05-25 14:44:31 -03:00
- SF bug 742860: "WeakKeyDictionary __delitem__ uses iterkeys". This
wasn't threadsafe, was very inefficient (expected time O(len(dict))
instead of O(1)), and could raise a spurious RuntimeError if another
thread mutated the dict during __delitem__, or if a comparison function
mutated it. It also neglected to raise KeyError when the key wasn't
present; didn't raise TypeError when the key wasn't of a weakly
referencable type; and broke various more-or-less obscure dict
invariants by using a sequence of equality comparisons over the whole
set of dict keys instead of computing the key's hash code to narrow
the search to those keys with the same hash code. All of these are
considered to be bugs. A new implementation of __delitem__ repairs all
that, but note that fixing these bugs may change visible behavior in
code relying (whether intentionally or accidentally) on old behavior.
SF 742860: WeakKeyDictionary __delitem__ uses iterkeys Someone review this, please! Final releases are getting close, Fred (the weakref guy) won't be around until Tuesday, and the pre-patch code can indeed raise spurious RuntimeErrors in the presence of threads or mutating comparison functions. See the bug report for my confusions: I can't see any reason for why __delitem__ iterated over the keys. The new one-liner implementation is much faster, can't raise RuntimeError, and should be better-behaved in all respects wrt threads. New tests test_weak_keyed_bad_delitem and test_weak_keyed_cascading_deletes fail before this patch. Bugfix candidate for 2.2.3 too, if someone else agrees with this patch.
2003-05-24 22:45:11 -03:00
Add several news items for changes I made since b1.
2003-06-29 14:25:39 -03:00
- SF bug 734869: Fixed a compiler bug that caused a fatal error when
compiling a list comprehension that contained another list comprehension
embedded in a lambda expression.
SF bug 705231: Assertion failed, python aborts. float_pow(): Don't let the platform pow() raise -1.0 to an integer power anymore; at least glibc gets it wrong in some cases. Note that math.pow() will continue to deliver wrong (but platform-native) results in such cases.
2003-05-24 17:18:24 -03:00
- SF bug 705231: builtin 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.
Add several news items for changes I made since b1.
2003-06-29 14:25:39 -03:00
- 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.
Patch #612627: Add encoding attribute to file objects, and determine the terminal encoding on Windows and Unix.
2003-05-10 04:10:12 -03:00
- The encoding attribute has been added for file objects, and set to
the terminal encoding on Unix and Windows.
Somewhere along the way, the softspace attr of file objects became read- only. Repaired, and added new tests to test_file.py.
2003-05-04 01:16:52 -03:00
- The softspace attribute of file objects became read-only by oversight.
It's writable again.
SF bug #730296: Unexpected Changes in list Iterator Reverted a Py2.3b1 change to iterator in subclasses of list and tuple. They had been changed to use __getitem__ whenever it had been overriden in the subclass. This caused some usabilty and performance problems. Also, it was inconsistent with the rest of python where many container methods access the underlying object directly without first checking for an overridden getter. Users needing a change in iterator behavior should override it directly.
2003-05-06 22:28:47 -03:00
- Reverted a 2.3 beta 1 change to iterators for subclasses of list and
tuple. By default, the iterators now access data elements directly
instead of going through __getitem__. If __getitem__ access is
Add mmap bugfix; typo and grammar fixes
2003-07-16 17:11:34 -03:00
preferred, then __iter__ can be overridden.
SF bug #730296: Unexpected Changes in list Iterator Reverted a Py2.3b1 change to iterator in subclasses of list and tuple. They had been changed to use __getitem__ whenever it had been overriden in the subclass. This caused some usabilty and performance problems. Also, it was inconsistent with the rest of python where many container methods access the underlying object directly without first checking for an overridden getter. Users needing a change in iterator behavior should override it directly.
2003-05-06 22:28:47 -03:00
Add several news items for changes I made since b1.
2003-06-29 14:25:39 -03:00
- SF bug 735247: The staticmethod and super types participate in
garbage collection. Before this change, it was possible for leaks to
occur in functions with non-global free variables that used these types.
A start on news for 2.3b2.
2003-04-26 11:53:01 -03:00
Extension modules
-----------------
SF patch #760257: add socket.timeout exception
2003-06-29 00:29:42 -03:00
- the socket module has a new exception, socket.timeout, to allow
timeouts to be handled separately from other socket errors.
Add several news items for changes I made since b1.
2003-06-29 14:25:39 -03:00
- SF bug 751276: cPickle has fixed to propagate exceptions raised in
user code. In earlier versions, cPickle caught and ignored any
exception when it performed operations that it expected to raise
specific exceptions like AttributeError.
- cPickle Pickler and Unpickler objects now participate in garbage
collection.
mimetools.choose_boundary() news.
2003-06-15 20:13:35 -03:00
- mimetools.choose_boundary() could return duplicate strings at times,
especially likely on Windows. The strings returned are now guaranteed
unique within a single program run.
dummy_thread modified to have interrupt_main and to behave appropriately when called. Added announcement in Misc/NEWS for thread.interrupt_main and mention of dummy_thread's change.
2003-06-13 20:44:35 -03:00
- thread.interrupt_main() raises KeyboardInterrupt in the main thread.
dummy_thread has also been modified to try to simulate the behavior.
Fix array.array.insert(), so that it treats negative indices as being relative to the end of the array, just like list.insert() does. This closes SF bug #739313.
2003-05-18 00:15:10 -03:00
- array.array.insert() now treats negative indices as being relative
to the end of the array, just like list.insert() does. (SF bug #739313)
datetime.timedelta is now subclassable in Python. The new test shows one good use: a subclass adding a method to express the duration as a number of hours (or minutes, or whatever else you want to add). The native breakdown into days+seconds+us is often clumsy. Incidentally moved a large chunk of object-initialization code closer to the top of the file, to avoid worse forward-reference trickery.
2003-05-17 12:57:00 -03:00
- The datetime module classes datetime, time, and timedelta are now
properly subclassable.
datetime.datetime and datetime.time can now be subclassed in Python. Brr.
2003-05-17 02:55:19 -03:00
Patch #734118: Add {get|set}busywaitinterval.
2003-05-09 05:19:48 -03:00
- _tkinter.{get|set}busywaitinterval was added.
Note itertools.islice() bugfix.
2003-05-02 17:24:56 -03:00
- itertools.islice() now accepts stop=None as documented.
Fixes SF bug #730685.
add note about bsddb185 module
2003-05-06 17:42:37 -03:00
- the bsddb185 module is built in one restricted instance -
/usr/include/db.h exists and defines HASHVERSION to be 2. This is true
for many BSD-derived systems.
Add several news items for changes I made since b1.
2003-06-29 14:25:39 -03:00
A start on news for 2.3b2.
2003-04-26 11:53:01 -03:00
Library
-------
Some nifty doctest extensions from Jim Fulton, currently used in Zope3. I won't have time to write real docs, but spent a lot of time adding comments to his code and fleshing out the exported functions' docstrings. There's probably opportunity to consolidate how docstrings get extracted too, and the new code for that is probably better than the old code for that (which strained mightily to recover from 2.2's new class/type gimmicks).
2003-06-29 02:30:48 -03:00
- Some happy doctest extensions from Jim Fulton have been added to
doctest.py. These are already being used in Zope3. The two
primary ones:
doctest.debug(module, name) extracts the doctests from the named object
in the given module, puts them in a temp file, and starts pdb running
on that file. This is great when a doctest fails.
doctest.DocTestSuite(module=None) returns a synthesized unittest
TestSuite instance, to be run by the unittest framework, which
runs all the doctests in the module. This allows writing tests in
doctest style (which can be clearer and shorter than writing tests
in unittest style), without losing unittest's powerful testing
framework features (which doctest lacks).
A hack to ease compatibility with pre-2.3 Pythons: by default, doctest now accepts "True" when a test expects "1", and similarly for "False" versus "0". This is un-doctest-like, but on balance makes it much more pleasant to write doctests that pass under 2.2 and 2.3. I expect it to go away again, when 2.2 is forgotten. In the meantime, there's a new doctest module constant that can be passed to a new optional argument, if you want to turn this behavior off. Note that this substitution is very simple-minded: the expected and actual outputs have to consist of single tokens. No attempt is made, e.g., to accept [True, False] when a test expects [1, 0]. This is a simple hack for simple tests, and I intend to keep it that way.
2003-06-27 17:48:05 -03:00
- For compatibility with doctests created before 2.3, if an expected
output block consists solely of "1" and the actual output block
consists solely of "True", it's accepted as a match; similarly
for "0" and "False". This is quite un-doctest-like, but is practical.
The behavior can be disabled by passing the new doctest module
constant DONT_ACCEPT_TRUE_FOR_1 to the new optionflags optional
argument.
Add several news items for changes I made since b1.
2003-06-29 14:25:39 -03:00
- ZipFile.testzip() now only traps BadZipfile exceptions. Previously,
a bare except caught to much and reported all errors as a problem
in the archive.
- The logging module now has a new function, makeLogRecord() making
LogHandler easier to interact with DatagramHandler and SocketHandler.
SF Patch 569574 - enhancements to cgitb for plain text display
2003-06-17 09:58:31 -03:00
- The cgitb module has been extended to support plain text display (SF patch
569574).
News about the new IDLE (is more needed?). News about SF patch 751998.
2003-06-13 17:37:23 -03:00
- A brand new version of IDLE (from the IDLEfork project at
SourceForge) is now included as Lib/idlelib. The old Tools/idle is
no more.
Add several news items for changes I made since b1.
2003-06-29 14:25:39 -03:00
- Added a new module: trace (documentation missing). This module used
to be distributed in Tools/scripts. It uses sys.settrace() to trace
code execution -- either function calls or individual lines. It can
generate tracing output during execution or a post-mortem report of
code coverage.
Add item about new threading module functions.
2003-06-16 17:38:15 -03:00
- The threading module has new functions settrace() and setprofile()
that cooperate with the functions of the same name in the sys
module. A function registered with the threading module will
Add several news items for changes I made since b1.
2003-06-29 14:25:39 -03:00
be used for all threads it creates. The new trace module uses this
to provide tracing for code running in threads.
Add item about new threading module functions.
2003-06-16 17:38:15 -03:00
SF patch 707900, fixing bug 702858, by Steven Taschuk. Copying a new-style class that had a reference to itself didn't work. (The same thing worked fine for old-style classes.)
2003-06-13 16:28:47 -03:00
- copy.py: applied SF patch 707900, fixing bug 702858, by Steven
Taschuk. Copying a new-style class that had a reference to itself
didn't work. (The same thing worked fine for old-style classes.)
Copy builtin functions as atomic. Fixes #746304. Will backport to 2.2.
2003-06-14 04:10:06 -03:00
Builtin functions are now treated as atomic, fixing bug #746304.
SF patch 707900, fixing bug 702858, by Steven Taschuk. Copying a new-style class that had a reference to itself didn't work. (The same thing worked fine for old-style classes.)
2003-06-13 16:28:47 -03:00
Announce difflib.context_diff() and difflib.unified_diff().
2003-06-08 16:42:33 -03:00
- difflib.py has two new functions: context_diff() and unified_diff().
More fixes according to SF 549151: - When redirecting, always use GET. This is common practice and more-or-less sanctioned by the HTTP standard. - Add a handler for 307 redirection, which becomes an error for POST, but a regular redirect for GET and HEAD.
2003-05-15 22:46:51 -03:00
- More fixes to urllib (SF 549151): (a) When redirecting, always use
GET. This is common practice and more-or-less sanctioned by the
HTTP standard. (b) Add a handler for 307 redirection, which becomes
an error for POST, but a regular redirect for GET and HEAD
Add optional 'onerror' argument to os.walk(), to control error handling.
2003-05-13 15:01:19 -03:00
- Added optional 'onerror' argument to os.walk(), to control error
handling.
Patch #711902: Cause pydoc to show data descriptor __doc__ strings.
2003-05-03 06:09:02 -03:00
- inspect.is{method|data}descriptor was added, to allow pydoc display
__doc__ of data descriptors.
document socket speed reclamation. Patch 729293.
2003-04-29 18:07:16 -03:00
- Fixed socket speed loss caused by use of the _socketobject wrapper class
in socket.py.
SF bug 735293: Command line timeit.py sets sys.path badly Paul Moore's patch to have timeit.py check the current directory for imports (instead of the directory for Lib/timeit.py).
2003-05-20 01:59:56 -03:00
- timeit.py now checks the current directory for imports.
- urllib2.py now knows how to order proxy classes, so the user doesn't have to insert it in front of other classes, nor do dirty tricks like inserting a "dummy" HTTPHandler after a ProxyHandler when building an opener with proxy support.
2003-06-07 14:53:08 -03:00
- urllib2.py now knows how to order proxy classes, so the user doesn't
have to insert it in front of other classes, nor do dirty tricks like
inserting a "dummy" HTTPHandler after a ProxyHandler when building an
opener with proxy support.
Merge branch updates back into the main trunk
2003-06-30 00:35:06 -03:00
- Iterators have been added for dbm keys.
- random.Random objects can now be pickled.
A start on news for 2.3b2.
2003-04-26 11:53:01 -03:00
Tools/Demos
-----------
Support keyword and topics help in cli(). Fixes #715782.
2003-06-14 06:03:46 -03:00
- pydoc now offers help on keywords and topics.
News about the new IDLE (is more needed?). News about SF patch 751998.
2003-06-13 17:37:23 -03:00
- Tools/idle is gone; long live Lib/idlelib.
Filled in release date; repaired grammar in a news item.
2003-06-29 13:18:08 -03:00
- diff.py prints file diffs in context, unified, or ndiff formats,
providing a command line interface to difflib.py.
Added a command line interface for difflib.py
2003-06-08 20:10:15 -03:00
Added a tool for making a rough check of LaTeX documents. It checks for known commands, forward slashes, unbalanced or mismatched delimters, and unbalanced or mismatched begin/end blocks.
2003-05-10 00:30:13 -03:00
- texcheck.py is a new script for making a rough validation of Python LaTeX
files.
A start on news for 2.3b2.
2003-04-26 11:53:01 -03:00
Build
-----
Add mmap bugfix; typo and grammar fixes
2003-07-16 17:11:34 -03:00
- Setting DESTDIR during 'make install' now allows specifying a
Patch #718286: Support DESTDIR.
2003-05-11 17:25:35 -03:00
different root directory.
A start on news for 2.3b2.
2003-04-26 11:53:01 -03:00
C API
-----
PyType_Ready(): Complain if the type is a base type, and gc'able, and tp_free is NULL or PyObject_Del at the end. Because it's a base type it must call tp_free in its dealloc function, and because it's gc'able it must not call PyObject_Del. inherit_slots(): Don't inherit tp_free unless the type and its base agree about whether they're gc'able. If the type is gc'able and the base is not, and the base uses the default PyObject_Del for its tp_free, give the type PyObject_GC_Del for its tp_free (the appropriate default for a gc'able type). cPickle.c: The Pickler and Unpickler types claim to be base classes and gc'able, but their dealloc functions didn't call tp_free. Repaired that. Also call PyType_Ready() on these typeobjects, so that the correct (PyObject_GC_Del) default memory-freeing function gets plugged into these types' tp_free slots.
2003-05-21 18:29:48 -03:00
- PyType_Ready(): If a type declares that it participates in gc
(Py_TPFLAGS_HAVE_GC), and its base class does not, and its base class's
tp_free slot is the default _PyObject_Del, and type does not define
a tp_free slot itself, _PyObject_GC_Del is assigned to type->tp_free.
Previously _PyObject_Del was inherited, which could at best lead to a
segfault. In addition, if even after this magic the type's tp_free
slot is _PyObject_Del or NULL, and the type is a base type
(Py_TPFLAGS_BASETYPE), TypeError is raised: since the type is a base
type, its dealloc function must call type->tp_free, and since the type
is gc'able, tp_free must not be NULL or _PyObject_Del.
Merge branch updates back into the main trunk
2003-06-30 00:35:06 -03:00
- PyThreadState_SetAsyncExc(): A new API (deliberately accessible only
from C) to interrupt a thread by sending it an exception. It is
intentional that you have to write your own C extension to call it
from Python.
A start on news for 2.3b2.
2003-04-26 11:53:01 -03:00
New platforms
-------------
None this time.
Tests
-----
- test_imp rewritten so that it doesn't raise RuntimeError if run as a
side effect of being imported ("import test.autotest").
Windows
-------
2.3b2 on Windows will ship with Tcl/Tk 8.4.3. Note: this still didn't fix the hangs on Win98SE when starting IDLE via "python" from a DOS box, but did appear to make them harder to provoke. I closed that bug report as being hopeless (and if someone wants to open it again, don't dare assign it to me again <0.1 wink>).
2003-06-21 22:42:20 -03:00
- The Windows installer ships with Tcl/Tk 8.4.3 (upgraded from 8.4.1).
Leading "C:" no longer hardcoded in the default installation directory. After removing that, two testers on machines where C: is not the system drive reported that the installer suggested their system drive instead of C:, and that's what they wanted it to do.
2003-05-08 15:13:59 -03:00
- The installer always suggested that Python be installed on the C:
drive, due to a hardcoded "C:" generated by the Wise installation
wizard. People with machines where C: is not the system drive
usually want Python installed on whichever drive is their system drive
instead. We removed the hardcoded "C:", and two testers on machines
where C: is not the system drive report that the installer now
suggests their system drive. Note that you can always select the
directory you want in the "Select Destination Directory" dialog --
that's what it's for.
A start on news for 2.3b2.
2003-04-26 11:53:01 -03:00
Mac
---
added note about autoGIL
2003-05-09 12:01:25 -03:00
- There's a new module called "autoGIL", which offers a mechanism to
automatically release the Global Interpreter Lock when an event loop
goes to sleep, allowing other threads to run. It's currently only
supported on OSX, in the Mach-O version.
Added two mac items (pimp auto-update and OSA property access).
2003-06-16 10:53:40 -03:00
- The OSA modules now allow direct access to properties of the
toplevel application class (in AppleScript terminology).
- The Package Manager can now update itself.
A start on news for 2.3b2.
2003-04-26 11:53:01 -03:00
Merge branch updates back into the main trunk
2003-06-30 00:35:06 -03:00
SourceForge Bugs and Patches Applied
------------------------------------
430160, 471893, 501716, 542562, 549151, 569574, 595837, 596434,
598163, 604210, 604716, 610332, 612627, 614770, 620190, 621891,
622042, 639139, 640236, 644345, 649742, 649742, 658233, 660022,
661318, 661676, 662807, 662923, 666219, 672855, 678325, 682347,
683486, 684981, 685773, 686254, 692776, 692959, 693094, 696777,
697989, 700827, 703666, 708495, 708604, 708901, 710733, 711902,
713722, 715782, 718286, 719359, 719367, 723136, 723831, 723962,
724588, 724767, 724767, 725942, 726150, 726446, 726869, 727051,
727719, 727719, 727805, 728277, 728563, 728656, 729096, 729103,
729293, 729297, 729300, 729317, 729395, 729622, 729817, 730170,
730296, 730594, 730685, 730826, 730963, 731209, 731403, 731504,
731514, 731626, 731635, 731643, 731644, 731644, 731689, 732124,
732143, 732234, 732284, 732284, 732479, 732761, 732783, 732951,
733667, 733781, 734118, 734231, 734869, 735051, 735293, 735527,
735613, 735694, 736962, 736962, 737970, 738066, 739313, 740055,
740234, 740301, 741806, 742126, 742741, 742860, 742860, 742911,
744041, 744104, 744238, 744687, 744877, 745055, 745478, 745525,
745620, 746012, 746304, 746366, 746801, 746953, 747348, 747667,
747954, 748846, 748849, 748973, 748975, 749191, 749210, 749759,
749831, 749911, 750008, 750092, 750542, 750595, 751038, 751107,
751276, 751451, 751916, 751941, 751956, 751998, 752671, 753451,
753602, 753617, 753845, 753925, 754014, 754340, 754447, 755031,
755087, 755147, 755245, 755683, 755987, 756032, 756996, 757058,
757229, 757818, 757821, 757822, 758112, 758910, 759227, 759889,
760257, 760703, 760792, 761104, 761337, 761519, 761830, 762455
Prepped for 2.3b1. Added an extra blank line before "What's New in Python 2.2 final?".
2003-02-19 21:56:17 -04:00
What's New in Python 2.3 beta 1?
================================
Update version number and release date.
2003-04-25 16:19:52 -03:00
*Release date: 25-Apr-2003*
Prepped for 2.3b1. Added an extra blank line before "What's New in Python 2.2 final?".
2003-02-19 21:56:17 -04:00
Core and builtins
-----------------
Mention the new getargs.c format codes.
2003-04-23 16:35:25 -03:00
- New format codes B, H, I, k and K have been implemented for
PyArg_ParseTuple and PyBuild_Value.
Adding new built-in function sum, with docs and tests.
2003-04-22 05:12:33 -03:00
- New builtin function sum(seq, start=0) returns the sum of all the
items in iterable object seq, plus start (items are normally numbers,
and cannot be strings).
- bool() called without arguments now returns False rather than raising an exception. This is consistent with calling the constructors for the other builtin types -- called without argument they all return the false value of that type. (SF patch #724135) Thanks to Alex Martelli.
2003-04-19 15:15:10 -03:00
- bool() called without arguments now returns False rather than
raising an exception. This is consistent with calling the
constructors for the other builtin types -- called without argument
they all return the false value of that type. (SF patch #724135)
Changes in support of PEP 269.
2003-04-17 13:53:26 -03:00
- In support of PEP 269 (making the pgen parser generator accessible
from Python), some changes to the pgen code structure were made; a
few files that used to be linked only with pgen are now linked with
Python itself.
- The repr() of a weakref object now shows the __name__ attribute of the referenced object, if it has one. Also use %p to format pointers consistently, and use <weakproxy ...> in proxy_repr(), to match the type name.
2003-04-16 18:13:23 -03:00
- The repr() of a weakref object now shows the __name__ attribute of
the referenced object, if it has one.
- super() no longer ignores data descriptors, except __class__. See the thread started at http://mail.python.org/pipermail/python-dev/2003-April/034338.html
2003-04-16 16:40:58 -03:00
- super() no longer ignores data descriptors, except __class__. See
the thread started at
http://mail.python.org/pipermail/python-dev/2003-April/034338.html
- list.insert(i, x) now interprets negative i as it would be interpreted by slicing, so negative values count from the end of the list. This was the only place where such an interpretation was not placed on a list index.
2003-04-14 17:58:14 -03:00
- list.insert(i, x) now interprets negative i as it would be
interpreted by slicing, so negative values count from the end of the
list. This was the only place where such an interpretation was not
placed on a list index.
Patch by Chad Netzer (with significant change): - range() now works even if the arguments are longs with magnitude larger than sys.maxint, as long as the total length of the sequence fits. E.g., range(2**100, 2**101, 2**100) is the following list: [1267650600228229401496703205376L]. (SF patch #707427.)
2003-04-11 15:43:06 -03:00
- range() now works even if the arguments are longs with magnitude
larger than sys.maxint, as long as the total length of the sequence
fits. E.g., range(2**100, 2**101, 2**100) is the following list:
[1267650600228229401496703205376L]. (SF patch #707427.)
Reworked has_finalizer() to use the new _PyObject_Lookup() instead of PyObject_HasAttr(); the former promises never to execute arbitrary Python code. Undid many of the changes recently made to worm around the worst consequences of that PyObject_HasAttr() could execute arbitrary Python code. Compatibility is hard to discuss, because the dangerous cases are so perverse, and much of this appears to rely on implementation accidents. To start with, using hasattr() to check for __del__ wasn't only dangerous, in some cases it was wrong: if an instance of an old- style class didn't have "__del__" in its instance dict or in any base class dict, but a getattr hook said __del__ existed, then hasattr() said "yes, this object has a __del__". But instance_dealloc() ignores the possibility of getattr hooks when looking for a __del__, so while object.__del__ succeeds, no __del__ method is called when the object is deleted. gc was therefore incorrect in believing that the object had a finalizer. The new method doesn't suffer that problem (like instance_dealloc(), _PyObject_Lookup() doesn't believe __del__ exists in that case), but does suffer a somewhat opposite-- and even more obscure --oddity: if an instance of an old-style class doesn't have "__del__" in its instance dict, and a base class does have "__del__" in its dict, and the first base class with a "__del__" associates it with a descriptor (an object with a __get__ method), *and* if that descriptor raises an exception when __get__ is called, then (a) the current method believes the instance does have a __del__, but (b) hasattr() does not believe the instance has a __del__. While these disagree, I believe the new method is "more correct": because the descriptor *will* be called when the object is destructed, it can execute arbitrary Python code at the time the object is destructed, and that's really what gc means by "has a finalizer": not specifically a __del__ method, but more generally the possibility of executing arbitrary Python code at object destruction time. Code in a descriptor's __get__() executed at destruction time can be just as problematic as code in a __del__() executed then. So I believe the new method is better on all counts. Bugfix candidate, but it's unclear to me how all this differs in the 2.2 branch (e.g., new-style and old-style classes already took different gc paths in 2.3 before this last round of patches, but don't in the 2.2 branch).
2003-04-07 16:21:15 -03:00
- Some horridly obscure problems were fixed involving interaction
between garbage collection and old-style classes with "ambitious"
getattr hooks. If an old-style instance didn't have a __del__ method,
but did have a __getattr__ hook, and the instance became reachable
only from an unreachable cycle, and the hook resurrected or deleted
unreachable objects when asked to resolve "__del__", anything up to
a segfault could happen. That's been repaired.
SF patch #693753: fix for bug 639806: default for dict.pop (contributed by Michael Stone.)
2003-03-06 19:54:28 -04:00
- dict.pop now takes an optional argument specifying a default
value to return if the key is not in the dict. If a default is not
given and the key is not found, a KeyError will still be raised.
Parallel changes were made to UserDict.UserDict and UserDict.DictMixin.
[SF patch #693753] (contributed by Michael Stone.)
Always initialize Py_FileSystemDefaultEncoding on Unix in Py_Initialize, and not as a side effect of setlocale. Expose it as sys.getfilesystemencoding. Adjust test case.
2003-03-05 11:13:47 -04:00
- sys.getfilesystemencoding() was added to expose
Py_FileSystemDefaultEncoding.
- New function sys.exc_clear() clears the current exception. This is rarely needed, but can sometimes be useful to release objects referenced by the traceback held in sys.exc_info()[2]. (SF patch #693195.) Thanks to Kevin Jacobs!
2003-02-28 23:20:41 -04:00
- New function sys.exc_clear() clears the current exception. This is
rarely needed, but can sometimes be useful to release objects
referenced by the traceback held in sys.exc_info()[2]. (SF patch
#693195.)
Fix SF bug #689659, 64-bit int and long hash keys incompatible On a 64-bit machine, a dictionary could contain duplicate int/long keys if the value was > 2**32.
2003-02-23 19:11:41 -04:00
- On 64-bit systems, a dictionary could contain duplicate long/int keys
if the key value was larger than 2**32. See SF bug #689659.
Prepped for 2.3b1. Added an extra blank line before "What's New in Python 2.2 final?".
2003-02-19 21:56:17 -04:00
Fixed SF bug #663074. The codec system was using global static variables to store internal data. As a result, any atempts to use the unicode system with multiple active interpreters, or successive interpreter executions, would fail. Now that information is stored into members of the PyInterpreterState structure.
2003-03-18 20:35:36 -04:00
- Fixed SF bug #663074. The codec system was using global static
Fix typo.
2003-03-31 12:15:13 -04:00
variables to store internal data. As a result, any attempts to use the
Fixed SF bug #663074. The codec system was using global static variables to store internal data. As a result, any atempts to use the unicode system with multiple active interpreters, or successive interpreter executions, would fail. Now that information is stored into members of the PyInterpreterState structure.
2003-03-18 20:35:36 -04:00
unicode system with multiple active interpreters, or successive
interpreter executions, would fail.
Fix PyString_Format() so that '%c' % u'a' returns u'a' instead of raising a TypeError. (From SF patch #710127) Add tests to verify this is fixed. Add various tests for '%c' % int.
2003-03-31 14:07:50 -04:00
- "%c" % u"a" now returns a unicode string instead of raising a
Change formatchar(), so that u"%c" % 0xffffffff now raises an OverflowError instead of a TypeError to be consistent with "%c" % 256. See SF patch #710127.
2003-04-02 12:37:24 -04:00
TypeError. u"%c" % 0xffffffff now raises a OverflowError instead
Fix description: u"%c" % 0xffffffff returned a ValueError not a TypeError.
2003-04-02 12:57:59 -04:00
of a ValueError to be consistent with "%c" % 256. See SF patch #710127.
Fix PyString_Format() so that '%c' % u'a' returns u'a' instead of raising a TypeError. (From SF patch #710127) Add tests to verify this is fixed. Add various tests for '%c' % int.
2003-03-31 14:07:50 -04:00
Prepped for 2.3b1. Added an extra blank line before "What's New in Python 2.2 final?".
2003-02-19 21:56:17 -04:00
Extension modules
-----------------
Move socket news to 2.3b1 section! And mention has_ipv6.
2003-04-25 02:52:37 -03:00
- The socket module now provides the functions inet_pton and inet_ntop
for converting between string and packed representation of IP
addresses. There is also a new module variable, has_ipv6, which is
True iff the current Python has IPv6 support. See SF patch #658327.
For StringVar results to strings. Document that boolean things are of type bool. Requested in #721171.
2003-04-16 16:42:51 -03:00
- Tkinter wrappers around Tcl variables now pass objects directly
to Tcl, instead of first converting them to strings.
SF patch #720991 by Gary Herron: A small fix for bug #545855 and Greg Chapman's addition of op code SRE_OP_MIN_REPEAT_ONE for eliminating recursion on simple uses of pattern '*?' on a long string.
2003-04-14 14:59:34 -03:00
- The .*? pattern in the re module is now special-cased to avoid the
recursion limit. (SF patch #720991 -- many thanks to Gary Herron
and Greg Chapman.)
- New function sys.call_tracing() allows pdb to debug code recursively. - pdb has a new command, "debug", which lets you step through arbitrary code from the debugger's (pdb) prompt.
2003-04-09 16:06:21 -03:00
- New function sys.call_tracing() allows pdb to debug code
recursively.
s/referrents/referents/g. Gotta love that referrers remains rife with rs.
2003-04-08 14:17:17 -03:00
- New function gc.get_referents(obj) returns a list of objects
Finished implementing gc.get_referrents(): dealt with error and end cases, wrote docs, added a test.
2003-04-08 13:39:48 -03:00
directly referenced by obj. In effect, it exposes what the object's
tp_traverse slot does, and can be helpful when debugging memory
leaks.
Revert Patch #670715: iconv support.
2003-04-03 00:49:12 -04:00
- The iconv module has been removed from this release.
SF bug 705836: struct.pack of floats in non-native endian order pack_float, pack_double, save_float: All the routines for creating IEEE-format packed representations of floats and doubles simply ignored that rounding can (in rare cases) propagate out of a long string of 1 bits. At worst, the end-off carry can (by mistake) interfere with the exponent value, and then unpacking yields a result wrong by a factor of 2. In less severe cases, it can end up losing more low-order bits than intended, or fail to catch overflow *caused* by rounding. Bugfix candidate, but I already backported this to 2.2. In 2.3, this code remains in severe need of refactoring.
2003-03-20 14:32:13 -04:00
- The platform-independent routines for packing floats in IEEE formats
(struct.pack's <f, >f, <d, and >d codes; pickle and cPickle's protocol 1
pickling of floats) ignored that rounding can cause a carry to
propagate. The worst consequence was that, in rare cases, <f and >f
could produce strings that, when unpacked again, were a factor of 2
away from the original float. This has been fixed. See SF bug
#705836.
Add mmap bugfix; typo and grammar fixes
2003-07-16 17:11:34 -03:00
- New function time.tzset() provides access to the C library tzset()
- New function time.tzset() provides access to the C library tzet() function, if supported. (SF patch #675422, by Stuart Bishop.)
2003-03-14 17:51:36 -04:00
function, if supported. (SF patch #675422.)
Fix SF #692416, don't crash interpreter for _tkinter.deletefilehandler in addition to createfilehandler and creaetetimerhandler.
2003-03-03 17:16:39 -04:00
- Using createfilehandler, deletefilehandler, createtimerhandler functions
on Tkinter.tkinter (_tkinter module) no longer crashes the interpreter.
See SF bug #692416.
Fix bug [ 555817 ] Flawed fcntl.ioctl implementation. with my patch that allows for an array to be mutated when passed as the buffer argument to ioctl() (details complicated by backwards compatibility considerations -- read the docs!).
2003-03-03 08:29:42 -04:00
- Modified the fcntl.ioctl() function to allow modification of a passed
mutable buffer (for details see the reference documentation).
User requested changes to the itertools module. Subsumed times() into repeat(). Added cycle() and chain().
2003-02-23 00:40:07 -04:00
- Made user requested changes to the itertools module.
Subsumed the times() function into repeat().
Added chain() and cycle().
Prepped for 2.3b1. Added an extra blank line before "What's New in Python 2.2 final?".
2003-02-19 21:56:17 -04:00
New generator os.walk() does a bit more than os.path.walk() does, and seems much easier to use. Code, docs, NEWS, and additions to test_os.py (testing this sucker is a bitch!).
2003-04-25 04:11:48 -03:00
- The rotor module is now deprecated; the encryption algorithm it uses
[Patch #679505] Document that the rotor module is deprecated
2003-04-24 10:19:56 -03:00
is not believed to be secure, and including crypto code with Python
has implications for exporting and importing it in various countries.
The socket module now always uses the _socketobject wrapper class, even on platforms which have dup(2). The makefile() method is built directly on top of the socket without duplicating the file descriptor, allowing timeouts to work properly. Includes a new test case (urllibnet) which requires the network resource. Closes bug 707074.
2003-03-30 00:54:24 -04:00
- The socket module now always uses the _socketobject wrapper class, even on
platforms which have dup(2). The makefile() method is built directly
on top of the socket without duplicating the file descriptor, allowing
timeouts to work properly.
Prepped for 2.3b1. Added an extra blank line before "What's New in Python 2.2 final?".
2003-02-19 21:56:17 -04:00
Library
-------
New generator os.walk() does a bit more than os.path.walk() does, and seems much easier to use. Code, docs, NEWS, and additions to test_os.py (testing this sucker is a bitch!).
2003-04-25 04:11:48 -03:00
- New generator function os.walk() is an easy-to-use alternative to
os.path.walk(). See os module docs for details. os.path.walk()
isn't deprecated at this time, but may become deprecated in a
future release.
New module platform.py, submitted by Marc-Andre Lemburg. There's no separate documentation for this module yet - apart from the doc-strings which explain the APIs.
2003-04-24 08:36:11 -03:00
- Added new module "platform" which provides a wide range of tools
for querying platform dependent features.
Fix case
2003-04-24 13:45:05 -03:00
- netrc now allows ASCII punctuation characters in passwords.
SF patch 557704: netrc module can't handle all passwords Revised netrc.py to include the additional ascii punctuation characters. Omitted the other logic changes. See Lib/netrc.py 1.17. Since this is more of a feature request than a bug, including in Py2.3 but not recommending for backporting.
2003-04-23 16:06:08 -03:00
Patch #553171: Add writeback parameter. Also add protocol parameter.
2003-04-19 17:59:03 -03:00
- shelve now supports the optional writeback argument, and exposes
pickle protocol versions.
- Several methods of nntplib.NNTP have grown an optional file argument which specifies a file where to divert the command's output (already supported by the body() method). (SF patch #720468) Thanks to Terry Carroll.
2003-04-19 15:04:57 -03:00
- Several methods of nntplib.NNTP have grown an optional file argument
which specifies a file where to divert the command's output
(already supported by the body() method). (SF patch #720468)
Patch #536883: SimpleXMLRPCServer auto-docing subclass.
2003-04-18 18:04:39 -03:00
- The self-documenting XML server library DocXMLRPCServer was added.
Implement IDNA (Internationalized Domain Names in Applications).
2003-04-18 07:39:54 -03:00
- Support for internationalized domain names has been added through
the 'idna' and 'punycode' encodings, the 'stringprep' module, the
'mkstringprep' tool, and enhancements to the socket and httplib
modules.
Add two dictionaries to htmlentitydefs: name2codepoint maps HTML entity names to Unicode codepoints (as integers). codepoint2name is the reverse mapping. From SF patch #722017.
2003-04-16 06:46:13 -03:00
- htmlentitydefs has two new dictionaries: name2codepoint maps
HTML entity names to Unicode codepoints (as integers).
codepoint2name is the reverse mapping. See SF patch #722017.
- New function sys.call_tracing() allows pdb to debug code recursively. - pdb has a new command, "debug", which lets you step through arbitrary code from the debugger's (pdb) prompt.
2003-04-09 16:06:21 -03:00
- pdb has a new command, "debug", which lets you step through
arbitrary code from the debugger's (pdb) prompt.
SF bug #715145: unittest.py still uses != in failUnlessEqual
2003-04-04 18:56:42 -04:00
- unittest.failUnlessEqual and its equivalent unittest.assertEqual now
return 'not a == b' rather than 'a != b'. This gives the desired
result for classes that define __eq__ without defining __ne__.
Reworked has_finalizer() to use the new _PyObject_Lookup() instead of PyObject_HasAttr(); the former promises never to execute arbitrary Python code. Undid many of the changes recently made to worm around the worst consequences of that PyObject_HasAttr() could execute arbitrary Python code. Compatibility is hard to discuss, because the dangerous cases are so perverse, and much of this appears to rely on implementation accidents. To start with, using hasattr() to check for __del__ wasn't only dangerous, in some cases it was wrong: if an instance of an old- style class didn't have "__del__" in its instance dict or in any base class dict, but a getattr hook said __del__ existed, then hasattr() said "yes, this object has a __del__". But instance_dealloc() ignores the possibility of getattr hooks when looking for a __del__, so while object.__del__ succeeds, no __del__ method is called when the object is deleted. gc was therefore incorrect in believing that the object had a finalizer. The new method doesn't suffer that problem (like instance_dealloc(), _PyObject_Lookup() doesn't believe __del__ exists in that case), but does suffer a somewhat opposite-- and even more obscure --oddity: if an instance of an old-style class doesn't have "__del__" in its instance dict, and a base class does have "__del__" in its dict, and the first base class with a "__del__" associates it with a descriptor (an object with a __get__ method), *and* if that descriptor raises an exception when __get__ is called, then (a) the current method believes the instance does have a __del__, but (b) hasattr() does not believe the instance has a __del__. While these disagree, I believe the new method is "more correct": because the descriptor *will* be called when the object is destructed, it can execute arbitrary Python code at the time the object is destructed, and that's really what gc means by "has a finalizer": not specifically a __del__ method, but more generally the possibility of executing arbitrary Python code at object destruction time. Code in a descriptor's __get__() executed at destruction time can be just as problematic as code in a __del__() executed then. So I believe the new method is better on all counts. Bugfix candidate, but it's unclear to me how all this differs in the 2.2 branch (e.g., new-style and old-style classes already took different gc paths in 2.3 before this last round of patches, but don't in the 2.2 branch).
2003-04-07 16:21:15 -03:00
- sgmllib now supports SGML marked sections, in particular the
Patch #545300: Support marked sections.
2003-03-30 10:25:40 -04:00
MS Office extensions.
SF 698520: Iterator for urllib.URLOpener Contributed by Brett Cannon.
2003-03-09 01:33:33 -04:00
- The urllib module now offers support for the iterator protocol.
SF patch 698520 contributed by Brett Cannon.
Mention timeit.py.
2003-03-05 21:56:12 -04:00
- New module timeit provides a simple framework for timing the
execution speed of expressions and statements.
SF bug 693121: Set == non-Set is a TypeError. Allow mixed-type __eq__ and __ne__ for Set objects. This is messier than I'd like because Set *also* implements __cmp__. I know of one glitch now: cmp(s, t) returns 0 now when s and t are both Sets and s == t, despite that Set.__cmp__ unconditionally raises TypeError (and by intent). The rub is that __eq__ gets tried first, and the x.__eq__(y) True result convinces Python that cmp(x, y) is 0 without even calling Set.__cmp__.
2003-03-01 20:19:49 -04:00
- sets.Set objects now support mixed-type __eq__ and __ne__, instead
of raising TypeError. If x is a Set object and y is a non-Set object,
x == y is False, and x != y is True. This is akin to the change made
for mixed-type comparisons of datetime objects in 2.3a2; more info
about the rationale is in the NEWS entry for that. See also SF bug
report <http://www.python.org/sf/693121>.
Patch #683592 revisited, after discussions with MvL: - Implement the behavior as specified in PEP 277, meaning os.listdir() will only return unicode strings if it is _called_ with a unicode argument. - And then return only unicode, don't attempt to convert to ASCII. - Don't switch on Py_FileSystemDefaultEncoding, but simply use the default encoding if Py_FileSystemDefaultEncoding is NULL. This means os.listdir() can now raise UnicodeDecodeError if the default encoding can't represent the directory entry. (This seems better than silcencing the error and fall back to a byte string.) - Attempted to decribe the above in Doc/lib/libos.tex. - Reworded the Misc/NEWS items to reflect the current situation. This checkin also fixes bug #696261, which was due to os.listdir() not using Py_FileSystemDefaultEncoding, like all file system calls are supposed to.
2003-03-03 13:32:15 -04:00
- On Unix platforms, if os.listdir() is called with a Unicode argument,
it now returns Unicode strings. (This behavior was added earlier
to the Windows NT/2k/XP version of os.listdir().)
Prepped for 2.3b1. Added an extra blank line before "What's New in Python 2.2 final?".
2003-02-19 21:56:17 -04:00
Add news item for patch #695090
2003-02-28 18:09:33 -04:00
- Distutils: both 'py_modules' and 'packages' keywords can now be specified
in core.setup(). Previously you could supply one or the other, but
not both of them. (SF patch #695090 from Bernhard Herzog)
announce csv package
2003-03-20 19:36:55 -04:00
- New csv package makes it easy to read/write CSV files.
Implemented posix-mode parsing support in shlex.py, as dicussed in mailing list, and in patch #722686.
2003-04-17 18:31:33 -03:00
- Module shlex has been extended to allow posix-like shell parsings,
including a split() function for easy spliting of quoted strings and
commands. An iterator interface was also implemented.
Prepped for 2.3b1. Added an extra blank line before "What's New in Python 2.2 final?".
2003-02-19 21:56:17 -04:00
Tools/Demos
-----------
_Py_PrintReferenceAddresses(): also print the type name. In real use I'm finding some pretty baffling output, like reprs consisting entirely of three left parens. At least this will let us know what type the object is (it's not str -- there's no quote character in the repr). New tool combinerefs.py, to combine the two output blocks produced via PYTHONDUMPREFS.
2003-04-17 21:45:59 -03:00
- New script combinerefs.py helps analyze new PYTHONDUMPREFS output.
See the module docstring for details.
Prepped for 2.3b1. Added an extra blank line before "What's New in Python 2.2 final?".
2003-02-19 21:56:17 -04:00
Build
-----
Fix SF bug #691793, Python 2.3a2 build fails on Tru64
2003-02-23 19:45:35 -04:00
- Fix problem building on OSF1 because the compiler only accepted
preprocessor directives that start in column 1. (SF bug #691793.)
Prepped for 2.3b1. Added an extra blank line before "What's New in Python 2.2 final?".
2003-02-19 21:56:17 -04:00
C API
-----
- New C API PyGC_Collect(), same as calling gc.collect(). - Call this in Py_Finalize(). - Expand the Misc/NEWS text on PY_LONG_LONG.
2003-04-17 14:29:22 -03:00
- Added PyGC_Collect(), equivalent to calling gc.collect().
- pythunrun.c, Py_Finalize(): move the call to _Py_PrintReferences() even farther down, to just before the call to _PyObject_DebugMallocStats(). This required the following changes: - pystate.c, PyThreadState_GetDict(): changed not to raise an exception or issue a fatal error when no current thread state is available, but simply return NULL without raising an exception (ever). - object.c, Py_ReprEnter(): when PyThreadState_GetDict() returns NULL, don't raise an exception but return 0. This means that when printing a container that's recursive, printing will go on and on and on. But that shouldn't happen in the case we care about (see first bullet). - Updated Misc/NEWS and Doc/api/init.tex to reflect changes to PyThreadState_GetDict() definition.
2003-04-15 12:12:39 -03:00
- PyThreadState_GetDict() was changed not to raise an exception or
issue a fatal error when no current thread state is available. This
makes it possible to print dictionaries when no thread is active.
- New C API PyGC_Collect(), same as calling gc.collect(). - Call this in Py_Finalize(). - Expand the Misc/NEWS text on PY_LONG_LONG.
2003-04-17 14:29:22 -03:00
- LONG_LONG was renamed to PY_LONG_LONG. Extensions that use this and
need compatibility with previous versions can use this:
Merge back from r23b1-branch
2003-04-25 21:21:31 -03:00
- New C API PyGC_Collect(), same as calling gc.collect(). - Call this in Py_Finalize(). - Expand the Misc/NEWS text on PY_LONG_LONG.
2003-04-17 14:29:22 -03:00
#ifndef PY_LONG_LONG
#define PY_LONG_LONG LONG_LONG
#endif
Rename LONG_LONG to PY_LONG_LONG. Fixes #710285.
2003-03-29 06:06:18 -04:00
Renamed PyObject_GenericGetIter to PyObject_SelfIter to more accurately describe what the function does. Suggested by Thomas Wouters.
2003-03-17 15:46:11 -04:00
- Added PyObject_SelfIter() to fill the tp_iter slot for the
Created PyObject_GenericGetIter(). Factors out the common case of returning self.
2003-03-17 04:24:35 -04:00
typical case where the method returns its self argument.
- The extended type structure used for heap types (new-style classes defined by Python code using a class statement) is now exported from object.h as PyHeapTypeObject. (SF patch #696193.)
2003-03-07 11:13:17 -04:00
- The extended type structure used for heap types (new-style
classes defined by Python code using a class statement) is now
exported from object.h as PyHeapTypeObject. (SF patch #696193.)
Prepped for 2.3b1. Added an extra blank line before "What's New in Python 2.2 final?".
2003-02-19 21:56:17 -04:00
New platforms
-------------
Merge back from r23b1-branch
2003-04-25 21:21:31 -03:00
None this time.
Prepped for 2.3b1. Added an extra blank line before "What's New in Python 2.2 final?".
2003-02-19 21:56:17 -04:00
Tests
-----
Fix SF bugs #692951 and 692988, test_timeout.py needs 'network' resource require -u network to run test_timeout since it fails when not connected to a network.
2003-02-28 15:57:03 -04:00
- test_timeout now requires -u network to be passed to regrtest to run.
See SF bug #692988.
Prepped for 2.3b1. Added an extra blank line before "What's New in Python 2.2 final?".
2003-02-19 21:56:17 -04:00
Windows
-------
Enable os.fsync() for Windows, mapping it to MS's _commit() there. The docs here are best-guess: the MS docs I could find weren't clear, and some even claimed _commit() has no effect on Win32 systems (which is easily shown to be false just by trying it).
2003-04-22 23:39:17 -03:00
- os.fsync() now exists on Windows, and calls the Microsoft _commit()
function.
- New function winsound.MessageBeep() wraps the Win32 API MessageBeep().
2003-04-09 16:39:06 -03:00
- New function winsound.MessageBeep() wraps the Win32 API
MessageBeep().
Prepped for 2.3b1. Added an extra blank line before "What's New in Python 2.2 final?".
2003-02-19 21:56:17 -04:00
Mac
---
Patch #683592 revisited, after discussions with MvL: - Implement the behavior as specified in PEP 277, meaning os.listdir() will only return unicode strings if it is _called_ with a unicode argument. - And then return only unicode, don't attempt to convert to ASCII. - Don't switch on Py_FileSystemDefaultEncoding, but simply use the default encoding if Py_FileSystemDefaultEncoding is NULL. This means os.listdir() can now raise UnicodeDecodeError if the default encoding can't represent the directory entry. (This seems better than silcencing the error and fall back to a byte string.) - Attempted to decribe the above in Doc/lib/libos.tex. - Reworded the Misc/NEWS items to reflect the current situation. This checkin also fixes bug #696261, which was due to os.listdir() not using Py_FileSystemDefaultEncoding, like all file system calls are supposed to.
2003-03-03 13:32:15 -04:00
- os.listdir() now returns Unicode strings on MacOS X when called with
a Unicode argument. See the general news item under "Library".
Patch #683592: unicode support for os.listdir() os.listdir() may now return unicode strings on platforms that set Py_FileSystemDefaultEncoding.
2003-02-25 17:42:15 -04:00
Added a note about MacOS.WMAvailable().
2003-02-24 07:04:17 -04:00
- A new method MacOS.WMAvailable() returns true if it is safe to access
the window manager, false otherwise.
SF bug 693121: Set == non-Set is a TypeError. Allow mixed-type __eq__ and __ne__ for Set objects. This is messier than I'd like because Set *also* implements __cmp__. I know of one glitch now: cmp(s, t) returns 0 now when s and t are both Sets and s == t, despite that Set.__cmp__ unconditionally raises TypeError (and by intent). The rub is that __eq__ gets tried first, and the x.__eq__(y) True result convinces Python that cmp(x, y) is 0 without even calling Set.__cmp__.
2003-03-01 20:19:49 -04:00
Added a Mac note that EasyDialogs dialogs now bring the application to the foreground.
2003-03-24 08:13:54 -04:00
- EasyDialogs dialogs are now movable-modal, and if the application is
currently in the background they will ask to be moved to the foreground
before displaying.
Reworked has_finalizer() to use the new _PyObject_Lookup() instead of PyObject_HasAttr(); the former promises never to execute arbitrary Python code. Undid many of the changes recently made to worm around the worst consequences of that PyObject_HasAttr() could execute arbitrary Python code. Compatibility is hard to discuss, because the dangerous cases are so perverse, and much of this appears to rely on implementation accidents. To start with, using hasattr() to check for __del__ wasn't only dangerous, in some cases it was wrong: if an instance of an old- style class didn't have "__del__" in its instance dict or in any base class dict, but a getattr hook said __del__ existed, then hasattr() said "yes, this object has a __del__". But instance_dealloc() ignores the possibility of getattr hooks when looking for a __del__, so while object.__del__ succeeds, no __del__ method is called when the object is deleted. gc was therefore incorrect in believing that the object had a finalizer. The new method doesn't suffer that problem (like instance_dealloc(), _PyObject_Lookup() doesn't believe __del__ exists in that case), but does suffer a somewhat opposite-- and even more obscure --oddity: if an instance of an old-style class doesn't have "__del__" in its instance dict, and a base class does have "__del__" in its dict, and the first base class with a "__del__" associates it with a descriptor (an object with a __get__ method), *and* if that descriptor raises an exception when __get__ is called, then (a) the current method believes the instance does have a __del__, but (b) hasattr() does not believe the instance has a __del__. While these disagree, I believe the new method is "more correct": because the descriptor *will* be called when the object is destructed, it can execute arbitrary Python code at the time the object is destructed, and that's really what gc means by "has a finalizer": not specifically a __del__ method, but more generally the possibility of executing arbitrary Python code at object destruction time. Code in a descriptor's __get__() executed at destruction time can be just as problematic as code in a __del__() executed then. So I believe the new method is better on all counts. Bugfix candidate, but it's unclear to me how all this differs in the 2.2 branch (e.g., new-style and old-style classes already took different gc paths in 2.3 before this last round of patches, but don't in the 2.2 branch).
2003-04-07 16:21:15 -03:00
Added a note about scripting support and the IDE builtin help.
2003-04-01 18:33:37 -04:00
- OSA Scripting support has improved a lot, and gensuitemodule.py can now
Added a note that the Mac OSA modules are documented.
2003-04-11 12:37:20 -03:00
be used by mere mortals. The documentation is now also more or less
complete.
Reworked has_finalizer() to use the new _PyObject_Lookup() instead of PyObject_HasAttr(); the former promises never to execute arbitrary Python code. Undid many of the changes recently made to worm around the worst consequences of that PyObject_HasAttr() could execute arbitrary Python code. Compatibility is hard to discuss, because the dangerous cases are so perverse, and much of this appears to rely on implementation accidents. To start with, using hasattr() to check for __del__ wasn't only dangerous, in some cases it was wrong: if an instance of an old- style class didn't have "__del__" in its instance dict or in any base class dict, but a getattr hook said __del__ existed, then hasattr() said "yes, this object has a __del__". But instance_dealloc() ignores the possibility of getattr hooks when looking for a __del__, so while object.__del__ succeeds, no __del__ method is called when the object is deleted. gc was therefore incorrect in believing that the object had a finalizer. The new method doesn't suffer that problem (like instance_dealloc(), _PyObject_Lookup() doesn't believe __del__ exists in that case), but does suffer a somewhat opposite-- and even more obscure --oddity: if an instance of an old-style class doesn't have "__del__" in its instance dict, and a base class does have "__del__" in its dict, and the first base class with a "__del__" associates it with a descriptor (an object with a __get__ method), *and* if that descriptor raises an exception when __get__ is called, then (a) the current method believes the instance does have a __del__, but (b) hasattr() does not believe the instance has a __del__. While these disagree, I believe the new method is "more correct": because the descriptor *will* be called when the object is destructed, it can execute arbitrary Python code at the time the object is destructed, and that's really what gc means by "has a finalizer": not specifically a __del__ method, but more generally the possibility of executing arbitrary Python code at object destruction time. Code in a descriptor's __get__() executed at destruction time can be just as problematic as code in a __del__() executed then. So I believe the new method is better on all counts. Bugfix candidate, but it's unclear to me how all this differs in the 2.2 branch (e.g., new-style and old-style classes already took different gc paths in 2.3 before this last round of patches, but don't in the 2.2 branch).
2003-04-07 16:21:15 -03:00
Added a note about scripting support and the IDE builtin help.
2003-04-01 18:33:37 -04:00
- The IDE (in a framework build) now includes introductory documentation
in Apple Help Viewer format.
Prepped for 2.3b1. Added an extra blank line before "What's New in Python 2.2 final?".
2003-02-19 21:56:17 -04:00
Expose I_ constants. Auto-detect stropts.h. Properly configure the slave terminal.
2003-01-01 05:51:12 -04:00
What's New in Python 2.3 alpha 2?
=================================
Update versions/dates for release of 2.3a2. Added some last-minute news.
2003-02-19 14:18:47 -04:00
*Release date: 19-Feb-2003*
Expose I_ constants. Auto-detect stropts.h. Properly configure the slave terminal.
2003-01-01 05:51:12 -04:00
Core and builtins
Provide access to the import lock, fixing SF bug #580952. This is mostly from SF patch #683257, but I had to change unlock_import() to return an error value to avoid fatal error. Should this be backported? The patch requested this, but it's a new feature.
2003-02-12 17:46:11 -04:00
-----------------
Expose I_ constants. Auto-detect stropts.h. Properly configure the slave terminal.
2003-01-01 05:51:12 -04:00
Add a note about the recent PEP 293 changes.
2003-02-19 12:34:11 -04:00
- Negative positions returned from PEP 293 error callbacks are now
treated as being relative to the end of the input string. Positions
that are out of bounds raise an IndexError.
- sys.path[0] (the directory from which the script is loaded) is now turned into an absolute pathname, unless it is the empty string. (SF patch #664376, by Skip Montanaro.)
2003-02-19 11:25:10 -04:00
- sys.path[0] (the directory from which the script is loaded) is now
turned into an absolute pathname, unless it is the empty string.
(SF patch #664376.)
- Finally fixed the bug in compile() and exec where a string ending with an indented code block but no newline would raise SyntaxError. This would have been a four-line change in parsetok.c... Except codeop.py depends on this behavior, so a compilation flag had to be invented that causes the tokenizer to revert to the old behavior; this required extra changes to 2 .h files, 2 .c files, and 2 .py files. (Fixes SF bug #501622.)
2003-02-13 18:07:59 -04:00
- Finally fixed the bug in compile() and exec where a string ending
with an indented code block but no newline would raise SyntaxError.
This would have been a four-line change in parsetok.c... Except
codeop.py depends on this behavior, so a compilation flag had to be
invented that causes the tokenizer to revert to the old behavior;
this required extra changes to 2 .h files, 2 .c files, and 2 .py
Add SF reference to news item.
2003-02-13 18:19:20 -04:00
files. (Fixes SF bug #501622.)
- Finally fixed the bug in compile() and exec where a string ending with an indented code block but no newline would raise SyntaxError. This would have been a four-line change in parsetok.c... Except codeop.py depends on this behavior, so a compilation flag had to be invented that causes the tokenizer to revert to the old behavior; this required extra changes to 2 .h files, 2 .c files, and 2 .py files. (Fixes SF bug #501622.)
2003-02-13 18:07:59 -04:00
SF patch #685738 by Michael Stone. This changes the default __new__ to refuse arguments iff tp_init is the default __init__ implementation -- thus making it a TypeError when you try to pass arguments to a constructor if the class doesn't override at least __init__ or __new__.
2003-02-13 12:30:16 -04:00
- If a new-style class defines neither __new__ nor __init__, its
constructor would ignore all arguments. This is changed now: the
constructor refuses arguments in this case. This might break code
that worked under Python 2.2. The simplest fix is to add a no-op
fixed markup
2003-02-19 19:31:51 -04:00
__init__: ``def __init__(self, *args, **kw): pass``.
SF patch #685738 by Michael Stone. This changes the default __new__ to refuse arguments iff tp_init is the default __init__ implementation -- thus making it a TypeError when you try to pass arguments to a constructor if the class doesn't override at least __init__ or __new__.
2003-02-13 12:30:16 -04:00
SF #660455 : patch by NNorwitz. "Unsigned" (i.e., positive-looking, but really negative) hex/oct constants with a leading minus sign are once again properly negated. The micro-optimization for negated numeric constants did the wrong thing for such hex/oct constants. The patch avoids the optimization for all hex/oct constants. This needs to be backported to Python 2.2!
2003-02-12 13:05:26 -04:00
- Through a bytecode optimizer bug (and I bet you didn't even know
Python *had* a bytecode optimizer :-), "unsigned" hex/oct constants
with a leading minus sign would come out with the wrong sign.
("Unsigned" hex/oct constants are those with a face value in the
range sys.maxint+1 through sys.maxint*2+1, inclusive; these have
always been interpreted as negative numbers through sign folding.)
E.g. 0xffffffff is -1, and -(0xffffffff) is 1, but -0xffffffff would
come out as -4294967295. This was the case in Python 2.2 through
2.2.2 and 2.3a1, and in Python 2.4 it will once again have that
value, but according to PEP 237 it really needs to be 1 now. This
will be backported to Python 2.2.3 a well. (SF #660455)
Issue a warning when int('0...', 0) returns an int with the sign folded; this will change in Python 2.4. On a 32-bit machine, this happens for 0x80000000 through 0xffffffff, and for octal constants in the same value range. No warning is issued if an explicit base is given, *or* if the string contains a sign (since in those cases no sign folding ever happens).
2003-02-12 16:48:22 -04:00
- int(s, base) sometimes sign-folds hex and oct constants; it only
does this when base is 0 and s.strip() starts with a '0'. When the
sign is actually folded, as in int("0xffffffff", 0) on a 32-bit
machine, which returns -1, a FutureWarning is now issued; in Python
2.4, this will return 4294967295L, as do int("+0xffffffff", 0) and
int("0xffffffff", 16) right now. (PEP 347)
Implement another useful feature for proxies: in super(X, x), x may now be a proxy for an X instance, as long as issubclass(x.__class__, X).
2003-02-11 23:58:38 -04:00
- super(X, x): x may now be a proxy for an X instance, i.e.
issubclass(x.__class__, X) but not issubclass(type(x), X).
SF #532767: isinstance(x, X) should work when x is a proxy for an X instance, as long as x.__class__ is X or a subclass thereof. Did a little cleanup of PyObject_IsInstance() too.
2003-02-11 23:32:58 -04:00
- isinstance(x, X): if X is a new-style class, this is now equivalent
to issubclass(type(x), X) or issubclass(x.__class__, X). Previously
only type(x) was tested. (For classic classes this was already the
case.)
mention unicode support in compile, eval and exec
2003-02-10 05:57:08 -04:00
- compile(), eval() and the exec statement now fully support source code
passed as unicode strings.
Fix SF bug #683467, 'int' ability to generate longs not inherited When subclassing from an int but not overriding __new__, long values were not converted properly. Try to convert longs into an int.
2003-02-09 22:12:43 -04:00
- int subclasses can be initialized with longs if the value fits in an int.
See SF bug #683467.
long(string, base) now takes time linear in len(string) when base is a power of 2. Enabled the tail end of test_long() in pickletester.py because it no longer takes forever when run from test_pickle.py.
2003-02-02 03:51:32 -04:00
- long(string, base) takes time linear in len(string) when base is a power
of 2 now. It used to take time quadratic in len(string).
Patch #636005: Filter unicode into unicode.
2003-01-25 18:46:11 -04:00
- filter returns now Unicode results for Unicode arguments.
Allow PyFile_GetLine() to return Unicode objects. Fixes #660165.
2003-01-03 15:16:14 -04:00
- raw_input can now return Unicode objects.
Allow list sort's comparison function to explicitly be None. See SF patch 661092.
2003-01-02 16:51:08 -04:00
- List objects' sort() method now accepts None as the comparison function.
Passing None is semantically identical to calling sort() with no
arguments.
Fix SF bug #667147, Segmentation fault printing str subclass Fix infinite recursion which occurred when printing an object whose __str__() returned self. Will backport
2003-01-13 16:13:12 -04:00
- Fixed crash when printing a subclass of str and __str__ returned self.
See SF bug #667147.
Fix SF bug# 676155, RuntimeWarning with tp_compare Check return value of PyLong_AsDouble(), it can return an error.
2003-01-28 15:21:24 -04:00
- Fixed an invalid RuntimeWarning and an undetected error when trying
The various datetime object __setstate__() methods are no longer public (pickling no longer needs them, and immutable objects shouldn't have visible __setstate__() methods regardless). Rearranged the code to put the internal setstate functions in the constructor sections. Repaired the timedelta reduce() method, which was still producing stuff that required a public timedelta.__setstate__() when unpickling.
2003-01-31 18:27:17 -04:00
to convert a long integer into a float which couldn't fit.
Fix SF bug# 676155, RuntimeWarning with tp_compare Check return value of PyLong_AsDouble(), it can return an error.
2003-01-28 15:21:24 -04:00
See SF bug #676155.
Clarify that __module__ applies to various type of functions.
2003-02-06 12:16:50 -04:00
- Function objects now have a __module__ attribute that is bound to
Add news item about __module__ attribute on functions.
2003-02-06 12:00:15 -04:00
the name of the module in which the function was defined. This
Clarify that __module__ applies to various type of functions.
2003-02-06 12:16:50 -04:00
applies for C functions and methods as well as functions and methods
defined in Python. This attribute is used by pickle.whichmodule(),
which changes the behavior of whichmodule slightly. In Python 2.2
whichmodule() returns "__main__" for functions that are not defined
at the top-level of a module (examples: methods, nested functions).
Now whichmodule() will return the proper module name.
Add news item about __module__ attribute on functions.
2003-02-06 12:00:15 -04:00
Expose I_ constants. Auto-detect stropts.h. Properly configure the slave terminal.
2003-01-01 05:51:12 -04:00
Extension modules
-----------------
Make PyNumber_Check() a bit more careful, since all sorts of things now have tp_as_number. Check for nb_int or nb_float.
2003-02-18 12:36:28 -04:00
- operator.isNumberType() now checks that the object has a nb_int or
nb_float slot, rather than simply checking whether it has a non-NULL
tp_as_number pointer.
Provide access to the import lock, fixing SF bug #580952. This is mostly from SF patch #683257, but I had to change unlock_import() to return an error value to avoid fatal error. Should this be backported? The patch requested this, but it's a new feature.
2003-02-12 17:46:11 -04:00
- The imp module now has ways to acquire and release the "import
lock": imp.acquire_lock() and imp.release_lock(). Note: this is a
reentrant lock, so releasing the lock only truly releases it when
this is the last release_lock() call. You can check with
imp.lock_held(). (SF bug #580952 and patch #683257.)
Merge in changes made to the 2.3a2 release.
2003-02-19 21:38:31 -04:00
- Change to cPickle to match pickle.py (see below and PEP 307).
Add tests and news entry about parser errors from bug #678518.
2003-02-09 21:54:06 -04:00
- Fix some bugs in the parser module. SF bug #678518.
- Thanks to Scott David Daniels, a subtle bug in how the zlib extension implemented flush() was fixed. Scott also rewrite the zlib test suite using the unittest module. (SF bug #640230 and patch #678531.) Backport candidate I think.
2003-02-03 16:45:52 -04:00
- Thanks to Scott David Daniels, a subtle bug in how the zlib
Fix typo.
2003-02-03 16:53:14 -04:00
extension implemented flush() was fixed. Scott also rewrote the
- Thanks to Scott David Daniels, a subtle bug in how the zlib extension implemented flush() was fixed. Scott also rewrite the zlib test suite using the unittest module. (SF bug #640230 and patch #678531.) Backport candidate I think.
2003-02-03 16:45:52 -04:00
zlib test suite using the unittest module. (SF bug #640230 and
patch #678531.)
Move itertools module from the sandbox and into production.
2003-01-31 20:10:11 -04:00
- Added an itertools module containing high speed, memory efficient
looping constructs inspired by tools from Haskell and SML.
Support socket timeout in SSL, by Geoff Talvola. (SF patch #675750, to fix SF bug #675552.)
2003-01-27 18:22:50 -04:00
- The SSL module now handles sockets with a timeout set correctly (SF
patch #675750, fixing SF bug #675552).
A note about EX_OK and friends in the posixmodule.
2003-01-07 16:55:26 -04:00
- os/posixmodule has grown the sysexits.h constants (EX_OK and friends).
Fix from Michael Stone for SF bug #660476 and #513033 (bogus thread state swaps in readline).
2003-01-07 16:34:19 -04:00
- Fixed broken threadstate swap in readline that could cause fatal
errors when a readline hook was being invoked while a background
thread was active. (SF bugs #660476 and #513033.)
Expose I_ constants. Auto-detect stropts.h. Properly configure the slave terminal.
2003-01-01 05:51:12 -04:00
- fcntl now exposes the strops.h I_* constants.
Bump the Windows build to use Sleepycat's 4.1.25.NC release (the latest bsddb release without strong cryptography).
2003-01-24 11:31:31 -04:00
- Fix a crash on Solaris that occurred when calling close() on
an mmap'ed file which was already closed. (SF patch #665913)
Fix spelling.
2003-03-11 17:43:55 -04:00
- Fixed several serious bugs in the zipimport implementation.
Merge in changes made to the 2.3a2 release.
2003-02-19 21:38:31 -04:00
Added a section to record datetime changes. There's apparently going to be an unbounded number of API changes <0.6 wink>.
2003-01-02 15:10:19 -04:00
- datetime changes:
The date class is now properly subclassable. (SF bug #720908) (This is only the tip of the iceberg; the time and datetime classes need the same treatment.)
2003-04-14 19:01:58 -03:00
The date class is now properly subclassable. (SF bug #720908)
Utterly minimal changes to collapse datetimetz into datetime, and timetz into time. This is little more than *exporting* the datetimetz object under the name "datetime", and similarly for timetz. A good implementation of this change requires more work, but this is fully functional if you don't stare too hard at the internals (e.g., right now a type named "datetime" shows up as a base class of the type named "datetime"). The docs also need extensive revision, not part of this checkin.
2003-01-08 16:40:01 -04:00
The datetime and datetimetz classes have been collapsed into a single
datetime class, and likewise the time and timetz classes into a single
time class. Previously, a datetimetz object with tzinfo=None acted
exactly like a datetime object, and similarly for timetz. This wasn't
enough of a difference to justify distinct classes, and life is simpler
now.
Added a section to record datetime changes. There's apparently going to be an unbounded number of API changes <0.6 wink>.
2003-01-02 15:10:19 -04:00
today() and now() now round system timestamps to the closest
A new implementation of astimezone() that does what we agreed on in all cases, plus even tougher tests of that. This implementation follows the correctness proof very closely, and should also be quicker (yes, I wrote the proof before the code, and the code proves the proof <wink>).
2003-01-04 02:03:15 -04:00
microsecond <http://www.python.org/sf/661086>. This repairs an
irritation most likely seen on Windows systems.
Added a section to record datetime changes. There's apparently going to be an unbounded number of API changes <0.6 wink>.
2003-01-02 15:10:19 -04:00
"Premature" doc changes, for new astimezone() rules, and the new tzinfo.fromutc() method. The C code doesn't implement any of this yet (well, not the C code on the machine I'm using now), nor does the test suite reflect it. The Python datetime.py implementation and test suite in the sandbox do match these doc changes. The C implementation probably won't catch up before Thursday (Wednesday is a scheduled "black hole" day this week <0.4 wink>).
2003-01-22 00:45:50 -04:00
In dt.astimezone(tz), if tz.utcoffset(dt) returns a duration,
The tzinfo methods utcoffset() and dst() must return a timedelta object (or None) now. In 2.3a1 they could also return an int or long, but that was an unhelpfully redundant leftover from an earlier version wherein they couldn't return a timedelta. TOOWTDI.
2003-01-02 17:28:08 -04:00
ValueError is raised if tz.dst(dt) returns None (2.3a1 treated it
A new implementation of astimezone() that does what we agreed on in all cases, plus even tougher tests of that. This implementation follows the correctness proof very closely, and should also be quicker (yes, I wrote the proof before the code, and the code proves the proof <wink>).
2003-01-04 02:03:15 -04:00
as 0 instead, but a tzinfo subclass wishing to participate in
time zone conversion has to take a stand on whether it supports
DST; if you don't care about DST, then code dst() to return 0 minutes,
meaning that DST is never in effect).
The tzinfo methods utcoffset() and dst() must return a timedelta object (or None) now. In 2.3a1 they could also return an int or long, but that was an unhelpfully redundant leftover from an earlier version wherein they couldn't return a timedelta. TOOWTDI.
2003-01-02 17:28:08 -04:00
Remark about datetime tzinfo examples.
2003-01-03 18:35:24 -04:00
The tzinfo methods utcoffset() and dst() must return a timedelta object
(or None) now. In 2.3a1 they could also return an int or long, but that
was an unhelpfully redundant leftover from an earlier version wherein
The tzinfo methods utcoffset() and dst() must return a timedelta object (or None) now. In 2.3a1 they could also return an int or long, but that was an unhelpfully redundant leftover from an earlier version wherein they couldn't return a timedelta. TOOWTDI.
2003-01-02 17:28:08 -04:00
they couldn't return a timedelta. TOOWTDI.
Remark about datetime tzinfo examples.
2003-01-03 18:35:24 -04:00
The example tzinfo class for local time had a bug. It was replaced
by a later example coded by Guido.
"Premature" doc changes, for new astimezone() rules, and the new tzinfo.fromutc() method. The C code doesn't implement any of this yet (well, not the C code on the machine I'm using now), nor does the test suite reflect it. The Python datetime.py implementation and test suite in the sandbox do match these doc changes. The C implementation probably won't catch up before Thursday (Wednesday is a scheduled "black hole" day this week <0.4 wink>).
2003-01-22 00:45:50 -04:00
datetime.astimezone(tz) no longer raises an exception when the
A new implementation of astimezone() that does what we agreed on in all cases, plus even tougher tests of that. This implementation follows the correctness proof very closely, and should also be quicker (yes, I wrote the proof before the code, and the code proves the proof <wink>).
2003-01-04 02:03:15 -04:00
input datetime has no UTC equivalent in tz. For typical "hybrid" time
zones (a single tzinfo subclass modeling both standard and daylight
time), this case can arise one hour per year, at the hour daylight time
"Premature" doc changes, for new astimezone() rules, and the new tzinfo.fromutc() method. The C code doesn't implement any of this yet (well, not the C code on the machine I'm using now), nor does the test suite reflect it. The Python datetime.py implementation and test suite in the sandbox do match these doc changes. The C implementation probably won't catch up before Thursday (Wednesday is a scheduled "black hole" day this week <0.4 wink>).
2003-01-22 00:45:50 -04:00
ends. See new docs for details. In short, the new behavior mimics
the local wall clock's behavior of repeating an hour in local time.
dt.astimezone() can no longer be used to convert between naive and aware
datetime objects. If you merely want to attach, or remove, a tzinfo
object, without any conversion of date and time members, use
dt.replace(tzinfo=whatever) instead, where "whatever" is None or a
tzinfo subclass instance.
A new method tzinfo.fromutc(dt) can be overridden in tzinfo subclasses
to give complete control over how a UTC time is to be converted to
a local time. The default astimezone() implementation calls fromutc()
as its last step, so a tzinfo subclass can affect that too by overriding
fromutc(). It's expected that the default fromutc() implementation will
be suitable as-is for "almost all" time zone subclasses, but the
creativity of political time zone fiddling appears unbounded -- fromutc()
allows the highly motivated to emulate any scheme expressible in Python.
A new implementation of astimezone() that does what we agreed on in all cases, plus even tougher tests of that. This implementation follows the correctness proof very closely, and should also be quicker (yes, I wrote the proof before the code, and the code proves the proof <wink>).
2003-01-04 02:03:15 -04:00
Reimplemented datetime.now() to be useful.
2003-01-23 15:58:02 -04:00
datetime.now(): The optional tzinfo argument was undocumented (that's
repaired), and its name was changed to tz ("tzinfo" is overloaded enough
already). With a tz argument, now(tz) used to return the local date
and time, and attach tz to it, without any conversion of date and time
members. This was less than useful. Now now(tz) returns the current
fixed markup
2003-02-19 19:31:51 -04:00
date and time as local time in tz's time zone, akin to ::
Reimplemented datetime.now() to be useful.
2003-01-23 15:58:02 -04:00
tz.fromutc(datetime.utcnow().replace(tzinfo=utc))
fixed markup
2003-02-19 19:31:51 -04:00
Reimplemented datetime.now() to be useful.
2003-01-23 15:58:02 -04:00
where "utc" is an instance of a tzinfo subclass modeling UTC. Without
a tz argument, now() continues to return the current local date and time,
as a naive datetime object.
SF bug 660872: datetimetz constructors behave counterintuitively (2.3a1). This gives much the same treatment to datetime.fromtimestamp(stamp, tz) as the last batch of checkins gave to datetime.now(tz): do "the obvious" thing with the tz argument instead of a senseless thing.
2003-01-23 16:53:10 -04:00
datetime.fromtimestamp(): Like datetime.now() above, this had less than
useful behavior when the optional tinzo argument was specified. See
also SF bug report <http://www.python.org/sf/660872>.
date and datetime comparison: when we don't know how to compare against "the other" argument, we raise TypeError, in order to prevent comparison from falling back to the default (and worse than useless, in this case) comparison by object address. That's fine so far as it goes, but leaves no way for another date/datetime object to make itself comparable to our objects. For example, it leaves Marc-Andre no way to teach mxDateTime dates how to compare against Python dates. Discussion on Python-Dev raised a number of impractical ideas, and the simple one implemented here: when we don't know how to compare against "the other" argument, we raise TypeError *unless* the other object has a timetuple attr. In that case, we return NotImplemented instead, and Python will give the other object a shot at handling the comparison then. Note that comparisons of time and timedelta objects still suffer the original problem, though.
2003-01-24 18:36:34 -04:00
date and datetime comparison: In order to prevent comparison from
falling back to the default compare-object-addresses strategy, these
raised TypeError whenever they didn't understand the other object type.
They still do, except when the other object has a "timetuple" attribute,
in which case they return NotImplemented now. This gives other
datetime objects (e.g., mxDateTime) a chance to intercept the
comparison.
Comparison for timedelta, time, date and datetime objects: __eq__ and __ne__ no longer complain if they don't know how to compare to the other thing. If no meaningful way to compare is known, saying "not equal" is sensible. This allows things like if adatetime in some_sequence: and somedict[adatetime] = whatever to work as expected even if some_sequence contains non-datetime objects, or somedict non-datetime keys, because they only call __eq__. It still complains (raises TypeError) for mixed-type comparisons in contexts that require a total ordering, such as list.sort(), use as a key in a BTree-based data structure, and cmp().
2003-02-07 18:50:28 -04:00
date, time, datetime and timedelta comparison: When the exception
for mixed-type comparisons in the last paragraph doesn't apply, if
the comparison is == then False is returned, and if the comparison is
!= then True is returned. Because dict lookup and the "in" operator
fixed markup
2003-02-19 19:31:51 -04:00
only invoke __eq__, this allows, for example, ::
Comparison for timedelta, time, date and datetime objects: __eq__ and __ne__ no longer complain if they don't know how to compare to the other thing. If no meaningful way to compare is known, saying "not equal" is sensible. This allows things like if adatetime in some_sequence: and somedict[adatetime] = whatever to work as expected even if some_sequence contains non-datetime objects, or somedict non-datetime keys, because they only call __eq__. It still complains (raises TypeError) for mixed-type comparisons in contexts that require a total ordering, such as list.sort(), use as a key in a BTree-based data structure, and cmp().
2003-02-07 18:50:28 -04:00
if some_datetime in some_sequence:
fixed markup
2003-02-19 19:31:51 -04:00
and ::
Comparison for timedelta, time, date and datetime objects: __eq__ and __ne__ no longer complain if they don't know how to compare to the other thing. If no meaningful way to compare is known, saying "not equal" is sensible. This allows things like if adatetime in some_sequence: and somedict[adatetime] = whatever to work as expected even if some_sequence contains non-datetime objects, or somedict non-datetime keys, because they only call __eq__. It still complains (raises TypeError) for mixed-type comparisons in contexts that require a total ordering, such as list.sort(), use as a key in a BTree-based data structure, and cmp().
2003-02-07 18:50:28 -04:00
some_dict[some_timedelta] = whatever
to work as expected, without raising TypeError just because the
sequence is heterogeneous, or the dict has mixed-type keys. [This
seems like a good idea to implement for all mixed-type comparisons
that don't want to allow falling back to address comparison.]
datetime_from_timet_and_us(): ignore leap seconds if the platform localtime()/gmtime() insists on delivering them, + associated doc changes. Redid the docs for datetimtez.astimezone().
2003-01-04 14:17:36 -04:00
The constructors building a datetime from a timestamp could raise
ValueError if the platform C localtime()/gmtime() inserted "leap
seconds". Leap seconds are ignored now. On such platforms, it's
possible to have timestamps that differ by a second, yet where
datetimes constructed from them are equal.
The various datetime object __setstate__() methods are no longer public (pickling no longer needs them, and immutable objects shouldn't have visible __setstate__() methods regardless). Rearranged the code to put the internal setstate functions in the constructor sections. Repaired the timedelta reduce() method, which was still producing stuff that required a public timedelta.__setstate__() when unpickling.
2003-01-31 18:27:17 -04:00
The pickle format of date, time and datetime objects has changed
completely. The undocumented pickler and unpickler functions no
There's no good reason for datetime objects to expose __getstate__() anymore either, so don't. This also allows to get rid of obscure code making __getnewargs__ identical to __getstate__ (hmm ... hope there wasn't more to this than I realize!).
2003-01-31 22:54:15 -04:00
longer exist. The undocumented __setstate__() and __getstate__()
methods no longer exist either.
The various datetime object __setstate__() methods are no longer public (pickling no longer needs them, and immutable objects shouldn't have visible __setstate__() methods regardless). Rearranged the code to put the internal setstate functions in the constructor sections. Repaired the timedelta reduce() method, which was still producing stuff that required a public timedelta.__setstate__() when unpickling.
2003-01-31 18:27:17 -04:00
Expose I_ constants. Auto-detect stropts.h. Properly configure the slave terminal.
2003-01-01 05:51:12 -04:00
Library
-------
Merge in changes made to the 2.3a2 release.
2003-02-19 21:38:31 -04:00
- The logging module was updated slightly; the WARN level was renamed
to WARNING, and the matching function/method warn() to warning().
- The pickle and cPickle modules were updated with a new pickling
protocol (documented by pickletools.py, see below) and several
extensions to the pickle customization API (__reduce__, __setstate__
etc.). The copy module now uses more of the pickle customization
API to copy objects that don't implement __copy__ or __deepcopy__.
See PEP 307 for details.
- The distutils "register" command now uses http://www.python.org/pypi
as the default repository. (See PEP 301.)
Patch 686397: move definition of platform dependent path related variables from os.py to platform dependent path modules (ntpath, etc).
2003-02-17 05:20:23 -04:00
- the platform dependent path related variables sep, altsep, extsep,
pathsep, curdir, pardir and defpath are now defined in the platform
Reword section about moving variables to os.path to match intent (or at least, what I thought the intent was).
2003-02-17 08:26:23 -04:00
dependent path modules (e.g. ntpath.py) rather than os.py, so these
SF bug 693121: Set == non-Set is a TypeError. Allow mixed-type __eq__ and __ne__ for Set objects. This is messier than I'd like because Set *also* implements __cmp__. I know of one glitch now: cmp(s, t) returns 0 now when s and t are both Sets and s == t, despite that Set.__cmp__ unconditionally raises TypeError (and by intent). The rub is that __eq__ gets tried first, and the x.__eq__(y) True result convinces Python that cmp(x, y) is 0 without even calling Set.__cmp__.
2003-03-01 20:19:49 -04:00
variables are now available via os.path. They continue to be
available from the os module.
Reword section about moving variables to os.path to match intent (or at least, what I thought the intent was).
2003-02-17 08:26:23 -04:00
(see <http://www.python.org/sf/680789>).
Patch 686397: move definition of platform dependent path related variables from os.py to platform dependent path modules (ntpath, etc).
2003-02-17 05:20:23 -04:00
[680789] Debug with long array takes forever Added array.array to the types repr.py knows about, after a suggestion from Jurjen N.E. Bos.
2003-02-05 14:29:34 -04:00
- array.array was added to the types repr.py knows about (see
<http://www.python.org/sf/680789>).
Moving pickletools.py from the sandbox into the std library. I started this over the weekend, and it made faster & better progress than I expected -- it's already useful <wink>.
2003-01-27 14:51:48 -04:00
- The new pickletools.py contains lots of documentation about pickle
internals, and supplies some helpers for working with pickles, such as
a symbolic pickle disassembler.
add support for Python's bool type to xmlrpclib - patch # 559288
2003-01-22 14:17:25 -04:00
- Xmlrpclib.py now supports the builtin boolean type.
Patch #661719: Expose compilation errors as exceptions on request.
2003-01-15 07:51:06 -04:00
- py_compile has a new 'doraise' flag and a new PyCompileError
exception.
Patch #473586: Implement CGIXMLRPCRequestHandler.
2003-01-15 07:37:23 -04:00
- SimpleXMLRPCServer now supports CGI through the CGIXMLRPCRequestHandler
class.
Explicitly raise an exception in __cmp__ -- this clarifies that cmp() is not supported on sets. (Unfortunately, sorting a list of sets may still return random results because it uses < exclusively, but for sets that inly implements a partial ordering. Oh well.)
2003-01-14 12:45:04 -04:00
- The sets module now raises TypeError in __cmp__, to clarify that
sets are not intended to be three-way-compared; the comparison
operators are overloaded as subset/superset tests.
Note about rexec.py and Bastion.py. This requires doc changes and whatsnew updates as well.
2003-01-07 19:03:05 -04:00
- Bastion.py and rexec.py are disabled. These modules are not safe in
Python 2.2. or 2.3.
fixed markup
2003-02-19 19:31:51 -04:00
- realpath is now exported when doing ``from poxixpath import *``.
Fix SF #659228, 'realpath' function missing from os.path Also added realpath = abspath for os2emx, similar to windows/mac which also don't really implement realpath. Backport candidate, I think?
2003-01-03 14:12:28 -04:00
It is also exported for ntpath, macpath, and os2emxpath.
See SF bug #659228.
SF #651082, tarfile module implementation from Lars Gustäbel
2003-01-05 19:19:43 -04:00
- New module tarfile from Lars Gust<73>bel provides a comprehensive interface
to tar archive files with transparent gzip and bzip2 compression.
See SF patch #651082.
SF feature #618024, urlparse fails on imap://
2003-01-06 02:51:36 -04:00
- urlparse can now parse imap:// URLs. See SF feature request #618024.
Fixed markup.
2003-01-02 23:30:21 -04:00
Fix SF bug # 602259, 3rd parameter for Tkinter.scan_dragto Add the optional gain parameter and pass it to Tk.
2003-01-10 19:24:32 -04:00
- Tkinter.Canvas.scan_dragto() provides an optional parameter to support
the gain value which is passed to Tk. SF bug# 602259.
SF #642974, logging SysLogHandler proto type wrong Syslog uses UDP (SOCK_DGRAM)
2003-01-25 22:45:47 -04:00
- Fix logging.handlers.SysLogHandler protocol when using UNIX domain sockets.
Moving pickletools.py from the sandbox into the std library. I started this over the weekend, and it made faster & better progress than I expected -- it's already useful <wink>.
2003-01-27 14:51:48 -04:00
See SF patch #642974.
SF #642974, logging SysLogHandler proto type wrong Syslog uses UDP (SOCK_DGRAM)
2003-01-25 22:45:47 -04:00
note the demise of the dospath module (was actually in 2.3a2)
2003-02-25 13:46:20 -04:00
- The dospath module was deleted. Use the ntpath module when manipulating
DOS paths from other platforms.
Expose I_ constants. Auto-detect stropts.h. Properly configure the slave terminal.
2003-01-01 05:51:12 -04:00
Tools/Demos
-----------
add note about new db2pickle.py and pickle2db.py scripts
2003-02-03 11:17:25 -04:00
- Two new scripts (db2pickle.py and pickle2db.py) were added to the
Tools/scripts directory to facilitate conversion from the old bsddb module
to the new one. While the user-visible API of the new module is
compatible with the old one, it's likely that the version of the
underlying database library has changed. To convert from the old library,
run the db2pickle.py script using the old version of Python to convert it
to a pickle file. After upgrading Python, run the pickle2db.py script
using the new version of Python to reconstitute your database. For
example:
braino
2003-02-03 11:48:10 -04:00
% python2.2 db2pickle.py -h some.db > some.pickle
% python2.3 pickle2db.py -h some.db.new < some.pickle
add note about new db2pickle.py and pickle2db.py scripts
2003-02-03 11:17:25 -04:00
Run the scripts without any args to get a usage message.
Fixed markup.
2003-01-02 23:30:21 -04:00
Expose I_ constants. Auto-detect stropts.h. Properly configure the slave terminal.
2003-01-01 05:51:12 -04:00
Build
-----
- The audio driver tests (test_ossaudiodev.py and test_linuxaudiodev.py) are no longer run by default. This is because they don't always work, depending on your hardware and software. To run these tests, you must use an invocation like ./python Lib/test/regrtest.py -u audio test_ossaudiodev
2003-02-14 15:29:22 -04:00
- The audio driver tests (test_ossaudiodev.py and
test_linuxaudiodev.py) are no longer run by default. This is
because they don't always work, depending on your hardware and
fixed markup
2003-02-19 19:31:51 -04:00
software. To run these tests, you must use an invocation like ::
- The audio driver tests (test_ossaudiodev.py and test_linuxaudiodev.py) are no longer run by default. This is because they don't always work, depending on your hardware and software. To run these tests, you must use an invocation like ./python Lib/test/regrtest.py -u audio test_ossaudiodev
2003-02-14 15:29:22 -04:00
./python Lib/test/regrtest.py -u audio test_ossaudiodev
Split OPT make variable into OPT and BASECFLAGS. The latter contains those compiler flags which are necessary to get a clean compile. The former is for user-specified optimizer, debug, trace fiddling. See patch 640843. Add /sw/lib and /sw/include to setup.py search paths on Darwin to take advantage of fink goodies. Add scriptsinstall target to Makefile to install certain scripts from Tools/scripts directory.
2003-01-01 16:07:49 -04:00
- On systems which build using the configure script, compiler flags which
used to be lumped together using the OPT flag have been split into two
groups, OPT and BASECFLAGS. OPT is meant to carry just optimization- and
debug-related flags like "-g" and "-O3". BASECFLAGS is meant to carry
compiler flags that are required to get a clean compile. On some
platforms (many Linux flavors in particular) BASECFLAGS will be empty by
default. On others, such as Mac OS X and SCO, it will contain required
flags. This change allows people building Python to override OPT without
fear of clobbering compiler flags which are required to get a clean build.
- On Darwin/Mac OS X platforms, /sw/lib and /sw/include are added to the
relevant search lists in setup.py. This allows users building Python to
take advantage of the many packages available from the fink project
<http://fink.sf.net/>.
- A new Makefile target, scriptsinstall, installs a number of useful scripts
from the Tools/scripts directory.
Expose I_ constants. Auto-detect stropts.h. Properly configure the slave terminal.
2003-01-01 05:51:12 -04:00
C API
-----
fixed markup
2003-02-19 19:31:51 -04:00
- PyEval_GetFrame() is now declared to return a ``PyFrameObject *``
instead of a plain ``PyObject *``. (SF patch #686601.)
- PyEval_GetFrame() is now declared to return a PyFrameObject * instead of a plain PyObject *. (SF patch #686601 by Ben Laurie.)
2003-02-19 11:53:17 -04:00
Make PyNumber_Check() a bit more careful, since all sorts of things now have tp_as_number. Check for nb_int or nb_float.
2003-02-18 12:36:28 -04:00
- PyNumber_Check() now checks that the object has a nb_int or nb_float
slot, rather than simply checking whether it has a non-NULL
tp_as_number pointer.
Fix from SF #681367: inherit tp_as_buffer. This only applies to C types -- Python types already inherited this.
2003-02-11 16:39:59 -04:00
- A C type that inherits from a base type that defines tp_as_buffer
will now inherit the tp_as_buffer pointer if it doesn't define one.
(SF #681367)
If a float is passed where a int is expected, issue a DeprecationWarning instead of raising a TypeError. Closes #660144 (again).
2003-02-04 16:59:40 -04:00
- The PyArg_Parse functions now issue a DeprecationWarning if a float
argument is provided when an integer is specified (this affects the 'b',
'B', 'h', 'H', 'i', and 'l' codes). Future versions of Python will
raise a TypeError.
Add news about getargs change.
2003-01-24 18:15:53 -04:00
Expose I_ constants. Auto-detect stropts.h. Properly configure the slave terminal.
2003-01-01 05:51:12 -04:00
Tests
-----
Fix typo.
2003-03-26 12:03:16 -04:00
- Several tests weren't being run from regrtest.py (test_timeout.py,
Merge in changes made to the 2.3a2 release.
2003-02-19 21:38:31 -04:00
test_tarfile.py, test_netrc.py, test_multifile.py,
test_importhooks.py and test_imp.py). Now they are. (Note to
developers: please read Lib/test/README when creating a new test, to
make sure to do it right! All tests need to use either unittest or
pydoc.)
- Added test_posix.py, a test suite for the posix module.
- Added test_hexoct.py, a test suite for hex/oct constant folding.
Fixed markup.
2003-01-02 23:30:21 -04:00
Expose I_ constants. Auto-detect stropts.h. Properly configure the slave terminal.
2003-01-01 05:51:12 -04:00
Windows
-------
Update versions/dates for release of 2.3a2. Added some last-minute news.
2003-02-19 14:18:47 -04:00
- The timeout code for socket connect() didn't work right; this has
now been fixed. test_timeout.py should pass (at least most of the
time).
Patch #669198: Add cflags to RC compile.
2003-01-31 16:45:41 -04:00
- distutils' msvccompiler class now passes the preprocessor options to
the resource compiler. See SF patch #669198.
Bump the Windows build to use Sleepycat's 4.1.25.NC release (the latest bsddb release without strong cryptography).
2003-01-24 11:31:31 -04:00
- The bsddb module now ships with Sleepycat's 4.1.25.NC, the latest
release without strong cryptography.
Mention the change from patch #664376.
2003-01-08 11:14:55 -04:00
- sys.path[0], if it contains a directory name, is now always an
Merge in changes made to the 2.3a2 release.
2003-02-19 21:38:31 -04:00
absolute pathname. (SF patch #664376.)
Mention the change from patch #664376.
2003-01-08 11:14:55 -04:00
SF bug 660795: logging missing from Python 2.3a1 for Windows. Added the logging package. In the meantime, Neal Norwitz added a test_logging.py to the std test suite, which would have caught this oversight in the Windows installer.
2003-01-02 12:02:27 -04:00
- The new logging package is now installed by the Windows installer. It
wasn't in 2.3a1 due to oversight.
Expose I_ constants. Auto-detect stropts.h. Properly configure the slave terminal.
2003-01-01 05:51:12 -04:00
Mac
---
Attempting to keep the Mac section of the NEWS file up-to-date, in stead of the usual frantic editing at the last moment:-)
2003-01-27 11:21:39 -04:00
- There are new dialogs EasyDialogs.AskFileForOpen, AskFileForSave
and AskFolder. The old macfs.StandardGetFile and friends are deprecated.
Comparison for timedelta, time, date and datetime objects: __eq__ and __ne__ no longer complain if they don't know how to compare to the other thing. If no meaningful way to compare is known, saying "not equal" is sensible. This allows things like if adatetime in some_sequence: and somedict[adatetime] = whatever to work as expected even if some_sequence contains non-datetime objects, or somedict non-datetime keys, because they only call __eq__. It still complains (raises TypeError) for mixed-type comparisons in contexts that require a total ordering, such as list.sort(), use as a key in a BTree-based data structure, and cmp().
2003-02-07 18:50:28 -04:00
Added a note about getting rid of macfs usage (MacPython).
2003-02-06 19:10:45 -04:00
- Most of the standard library now uses pathnames or FSRefs in preference
of FSSpecs, and use the underlying Carbon.File and Carbon.Folder modules
in stead of macfs. macfs will probably be deprecated in the future.
Moving pickletools.py from the sandbox into the std library. I started this over the weekend, and it made faster & better progress than I expected -- it's already useful <wink>.
2003-01-27 14:51:48 -04:00
Attempting to keep the Mac section of the NEWS file up-to-date, in stead of the usual frantic editing at the last moment:-)
2003-01-27 11:21:39 -04:00
- Type Carbon.File.FSCatalogInfo and supporting methods have been implemented.
This also makes macfs.FSSpec.SetDates() work again.
SF bug 693121: Set == non-Set is a TypeError. Allow mixed-type __eq__ and __ne__ for Set objects. This is messier than I'd like because Set *also* implements __cmp__. I know of one glitch now: cmp(s, t) returns 0 now when s and t are both Sets and s == t, despite that Set.__cmp__ unconditionally raises TypeError (and by intent). The rub is that __eq__ gets tried first, and the x.__eq__(y) True result convinces Python that cmp(x, y) is 0 without even calling Set.__cmp__.
2003-03-01 20:19:49 -04:00
Added notes about pimp and bundlebuilder to the Mac section.
2003-02-16 19:00:53 -04:00
- There is a new module pimp, the package install manager for Python, and
accompanying applet PackageManager. These allow you to easily download
and install pretested extension packages either in source or binary
form. Only in MacPython-OSX.
SF bug 693121: Set == non-Set is a TypeError. Allow mixed-type __eq__ and __ne__ for Set objects. This is messier than I'd like because Set *also* implements __cmp__. I know of one glitch now: cmp(s, t) returns 0 now when s and t are both Sets and s == t, despite that Set.__cmp__ unconditionally raises TypeError (and by intent). The rub is that __eq__ gets tried first, and the x.__eq__(y) True result convinces Python that cmp(x, y) is 0 without even calling Set.__cmp__.
2003-03-01 20:19:49 -04:00
Added notes about pimp and bundlebuilder to the Mac section.
2003-02-16 19:00:53 -04:00
- Applets are now built with bundlebuilder in MacPython-OSX, which should make
Added a note that MacOSX applets can no longer be run from a terminal window.
2003-02-18 19:32:47 -04:00
them more robust and also provides a path towards BuildApplication. The
downside of this change is that applets can no longer be run from the
Terminal window, this will hopefully be fixed in the 2.3b1.
Fixed markup.
2003-01-02 23:30:21 -04:00
Expose I_ constants. Auto-detect stropts.h. Properly configure the slave terminal.
2003-01-01 05:51:12 -04:00
Added 2.3a1 section.
2001-12-21 17:36:50 -04:00
What's New in Python 2.3 alpha 1?
=================================
Set the release date.
2002-12-31 11:47:36 -04:00
*Release date: 31-Dec-2002*
ReST-ification of the NEWS file. While the total number of changes are fairly large, most are caused by reformatting section and subsection headings. The changes fall into the following categories: * reformatted section and subsection headers. * escaped isolated asterisks which would be interpreted as starting bold or italic text (e.g. "void (*)(PyObject \*)"). * quoted stuff that looks like internal references but isn't (e.g. ``PyCmp_``). * changed visually balanced quotes to just use apostrophes (e.g. "'string'" instead of "`string'"). * introduced and indenting multiline chunks of code. * created one table (search for "New codecs").
2002-09-20 11:16:59 -03:00
Added 2.3a1 section.
2001-12-21 17:36:50 -04:00
Type/class unification and new-style classes
ReST-ification of the NEWS file. While the total number of changes are fairly large, most are caused by reformatting section and subsection headings. The changes fall into the following categories: * reformatted section and subsection headers. * escaped isolated asterisks which would be interpreted as starting bold or italic text (e.g. "void (*)(PyObject \*)"). * quoted stuff that looks like internal references but isn't (e.g. ``PyCmp_``). * changed visually balanced quotes to just use apostrophes (e.g. "'string'" instead of "`string'"). * introduced and indenting multiline chunks of code. * created one table (search for "New codecs").
2002-09-20 11:16:59 -03:00
--------------------------------------------
Touch up the news for dict() keyword args.
2002-11-23 12:28:12 -04:00
This is not part of my patch [ 635933 ] make some type attrs writable but should have been! News about the above.
2002-11-26 10:48:23 -04:00
- One can now assign to __bases__ and __name__ of new-style classes.
Touch up the news for dict() keyword args.
2002-11-23 12:28:12 -04:00
- dict() now accepts keyword arguments so that dict(one=1, two=2)
is the equivalent of {"one": 1, "two": 2}. Accordingly,
Patch #642500 with slight modifications: allow keyword arguments in dict() constructor. Example: >>> dict(a=1, b=2) {'a': 1, 'b': 2} >>>
2002-11-23 05:45:04 -04:00
the existing (but undocumented) 'items' keyword argument has
Touch up the news for dict() keyword args.
2002-11-23 12:28:12 -04:00
been eliminated. This means that dict(items=someMapping) now has
Patch #642500 with slight modifications: allow keyword arguments in dict() constructor. Example: >>> dict(a=1, b=2) {'a': 1, 'b': 2} >>>
2002-11-23 05:45:04 -04:00
a different meaning than before.
Change int() so that passing a string, unicode, float or long argument that is outside the integer range no longer raises OverflowError, but returns a long object instead. This fixes SF bug http://www.python.org/sf/635115
2002-11-19 16:49:15 -04:00
- int() now returns a long object if the argument is outside the
Fixed markup.
2003-01-02 23:30:21 -04:00
integer range, so int("4" * 1000), int(1e200) and int(1L<<1000) will
Change int() so that passing a string, unicode, float or long argument that is outside the integer range no longer raises OverflowError, but returns a long object instead. This fixes SF bug http://www.python.org/sf/635115
2002-11-19 16:49:15 -04:00
all return long objects instead of raising an OverflowError.
Added 2.3a1 section.
2001-12-21 17:36:50 -04:00
Fix minor nits Trim excess whitespace off one line
2002-11-15 10:42:34 -04:00
- Assignment to __class__ is disallowed if either the old or the new
New news about __class__ assignment restrictions and speed-up of new-style object creation/deallocation. Moved all news about type/class unification and new-stype classes to a separate section at the top.
2002-08-12 00:42:03 -03:00
class is a statically allocated type object (such as defined by an
Fix spelling errors and note the addition of operator.pow()
2002-08-19 11:25:03 -03:00
extension module). This prevents anomalies like 2.__class__ = bool.
New news about __class__ assignment restrictions and speed-up of new-style object creation/deallocation. Moved all news about type/class unification and new-stype classes to a separate section at the top.
2002-08-12 00:42:03 -03:00
- New-style object creation and deallocation have been sped up
significantly; they are now faster than classic instance creation
and deallocation.
- The __slots__ variable can now mention "private" names, and the
right thing will happen (e.g. __slots__ = ["__foo"]).
- The built-ins slice() and buffer() are now callable types. The
types classobj (formerly class), code, function, instance, and
instancemethod (formerly instance-method), which have no built-in
names but are accessible through the types module, are now also
callable. The type dict-proxy is renamed to dictproxy.
- Cycles going through the __class__ link of a new-style instance are
now detected by the garbage collector.
- Classes using __slots__ are now properly garbage collected.
[SF bug 519621]
- Tightened the __slots__ rules: a slot name must be a valid Python
identifier.
- The constructor for the module type now requires a name argument and
takes an optional docstring argument. Previously, this constructor
ignored its arguments. As a consequence, deriving a class from a
module (not from the module type) is now illegal; previously this
created an unnamed module, just like invoking the module type did.
[SF bug 563060]
- A new type object, 'basestring', is added. This is a common base type
for 'str' and 'unicode', and can be used instead of
types.StringTypes, e.g. to test whether something is "a string":
isinstance(x, basestring) is True for Unicode and 8-bit strings. This
is an abstract base class and cannot be instantiated directly.
- Changed new-style class instantiation so that when C's __new__
method returns something that's not a C instance, its __init__ is
not called. [SF bug #537450]
- Fixed super() to work correctly with class methods. [SF bug #535444]
- If you try to pickle an instance of a class that has __slots__ but
doesn't define or override __getstate__, a TypeError is now raised.
This is done by adding a bozo __getstate__ to the class that always
raises TypeError. (Before, this would appear to be pickled, but the
state of the slots would be lost.)
Added 2.3a1 section.
2001-12-21 17:36:50 -04:00
Core and builtins
ReST-ification of the NEWS file. While the total number of changes are fairly large, most are caused by reformatting section and subsection headings. The changes fall into the following categories: * reformatted section and subsection headers. * escaped isolated asterisks which would be interpreted as starting bold or italic text (e.g. "void (*)(PyObject \*)"). * quoted stuff that looks like internal references but isn't (e.g. ``PyCmp_``). * changed visually balanced quotes to just use apostrophes (e.g. "'string'" instead of "`string'"). * introduced and indenting multiline chunks of code. * created one table (search for "New codecs").
2002-09-20 11:16:59 -03:00
-----------------
Added 2.3a1 section.
2001-12-21 17:36:50 -04:00
News about zipimport.
2002-12-30 18:59:32 -04:00
- Import from zipfiles is now supported. The name of a zipfile placed
Broke the zipimport/PEP 302 news item into two separate items.
2002-12-31 06:22:38 -04:00
on sys.path causes the import statement to look for importable Python
modules (with .py, pyc and .pyo extensions) and packages inside the
zipfile. The zipfile import follows the specification (though not
the sample implementation) of PEP 273. The semantics of __path__ are
News about zipimport.
2002-12-30 18:59:32 -04:00
compatible with those that have been implemented in Jython since
Jython 2.1.
Fix spelling.
2003-03-11 17:43:55 -04:00
- PEP 302 has been accepted. Although it was initially developed to
SF bug 660795: logging missing from Python 2.3a1 for Windows. Added the logging package. In the meantime, Neal Norwitz added a test_logging.py to the std test suite, which would have caught this oversight in the Windows installer.
2003-01-02 12:02:27 -04:00
support zipimport, it offers a new, general import hook mechanism.
Broke the zipimport/PEP 302 news item into two separate items.
2002-12-31 06:22:38 -04:00
Several new variables have been added to the sys module:
sys.meta_path, sys.path_hooks, and sys.path_importer_cache; these
make extending the import statement much more convenient than
overriding the __import__ built-in function. For a description of
these, see PEP 302.
This is Richie Hindle's patch [ 643835 ] Set Next Statement for Python debuggers with a few tweaks by me: adding an unsigned or two, mentioning that not all jumps are allowed in the doc for pdb, adding a NEWS item and a note to whatsnew, and AuCTeX doing something cosmetic to libpdb.tex.
2002-12-17 12:15:34 -04:00
- A frame object's f_lineno attribute can now be written to from a
trace function to change which line will execute next. A command to
exploit this from pdb has been added. [SF patch #643835]
News item for the change to turn _codecs into a builtin module.
2002-12-12 14:01:43 -04:00
- The _codecs support module for codecs.py was turned into a builtin
module to assure that at least the builtin codecs are available
to the Python parser for source code decoding according to PEP 263.
Enhance issubclass() and PyObject_IsSubclass() so that a tuple is supported as the second argument. This has the same meaning as for isinstance(), i.e. issubclass(X, (A, B)) is equivalent to issubclass(X, A) or issubclass(X, B). Compared to isinstance(), this patch does not search the tuple recursively for classes, i.e. any entry in the tuple that is not a class, will result in a TypeError. This closes SF patch #649608.
2002-12-12 12:41:44 -04:00
- issubclass now supports a tuple as the second argument, just like
isinstance does. ``issubclass(X, (A, B))`` is equivalent to
``issubclass(X, A) or issubclass(X, B)``.
SF patch 637176: list.sort crasher Armin Rigo's Draconian but effective fix for SF bug 453523: list.sort crasher slightly fiddled to catch more cases of list mutation. The dreaded internal "immutable list type" is gone! OTOH, if you look at a list *while* it's being sorted now, it will appear to be empty. Better than a core dump.
2002-11-12 18:08:10 -04:00
- Thanks to Armin Rigo, the last known way to provoke a system crash
by cleverly arranging for a comparison function to mutate a list
during a list.sort() operation has been fixed. The effect of
attempting to mutate a list, or even to inspect its contents or
length, while a sort is in progress, is not defined by the language.
The C implementation of Python 2.3 attempts to detect mutations,
and raise ValueError if one occurs, but there's no guarantee that
all mutations will be caught, or that any will be caught across
releases or implementations.
Document patch #594001.
2002-10-05 06:46:48 -03:00
- Unicode file name processing for Windows (PEP 277) is implemented.
Add os.path.supports_unicode_filenames for all platforms, sys.getwindowsversion() on Windows (new enahanced Tim-proof <wink> version), and fix test_pep277.py in a few minor ways. Including doc and NEWS entries.
2002-10-07 23:44:31 -03:00
All platforms now have an os.path.supports_unicode_filenames attribute,
which is set to True on Windows NT/2000/XP, and False elsewhere.
Document patch #594001.
2002-10-05 06:46:48 -03:00
PEP 293 implemention (from SF patch http://www.python.org/sf/432401)
2002-09-02 10:14:32 -03:00
- Codec error handling callbacks (PEP 293) are implemented.
Error handling in unicode.encode or str.decode can now be customized.
SF patch 576101, by Oren Tirosh: alternative implementation of interning. I modified Oren's patch significantly, but the basic idea and most of the implementation is unchanged. Interned strings created with PyString_InternInPlace() are now mortal, and you must keep a reference to the resulting string around; use the new function PyString_InternImmortal() to create immortal interned strings.
2002-08-19 18:43:18 -03:00
- A subtle change to the semantics of the built-in function intern():
interned strings are no longer immortal. You must keep a reference
to the return value intern() around to get the benefit.
Mention warnings about defining None.
2002-08-16 00:38:10 -03:00
- Use of 'None' as a variable, argument or attribute name now
issues a SyntaxWarning. In the future, None may become a keyword.
This is my patch [ 587993 ] SET_LINENO killer Remove SET_LINENO. Tracing is now supported by inspecting co_lnotab. Many sundry changes to document and adapt to this change.
2002-08-15 11:59:02 -03:00
- SET_LINENO is gone. co_lnotab is now consulted to determine when to
call the trace function. C code that accessed f_lineno should call
This is Richie Hindle's patch [ 643835 ] Set Next Statement for Python debuggers with a few tweaks by me: adding an unsigned or two, mentioning that not all jumps are allowed in the doc for pdb, adding a NEWS item and a note to whatsnew, and AuCTeX doing something cosmetic to libpdb.tex.
2002-12-17 12:15:34 -04:00
PyCode_Addr2Line instead (f_lineno is still there, but only kept up
to date when there is a trace function set).
This is my patch [ 587993 ] SET_LINENO killer Remove SET_LINENO. Tracing is now supported by inspecting co_lnotab. Many sundry changes to document and adapt to this change.
2002-08-15 11:59:02 -03:00
Add news about FutureWarning and PEP 237 stage B0. Tim predicts that we might as well call this CassandraWarning.
2002-08-14 13:11:30 -03:00
- There's a new warning category, FutureWarning. This is used to warn
about a number of situations where the value or sign of an integer
result will change in Python 2.4 as a result of PEP 237 (integer
unification). The warnings implement stage B0 mentioned in that
PEP. The warnings are about the following situations:
- Octal and hex literals without 'L' prefix in the inclusive range
[0x80000000..0xffffffff]; these are currently negative ints, but
in Python 2.4 they will be positive longs with the same bit
pattern.
- Left shifts on integer values that cause the outcome to lose
bits or have a different sign than the left operand. To be
precise: x<<n where this currently doesn't yield the same value
as long(x)<<n; in Python 2.4, the outcome will be long(x)<<n.
- Conversions from ints to string that show negative values as
unsigned ints in the inclusive range [0x80000000..0xffffffff];
this affects the functions hex() and oct(), and the string
formatting codes %u, %o, %x, and %X. In Python 2.4, these will
show signed values (e.g. hex(-1) currently returns "0xffffffff";
in Python 2.4 it will return "-0x1").
Dedent a paragraph that was accidentally aligned with a preceding nested list.
2002-12-30 22:12:42 -04:00
- The bits manipulated under the cover by sys.setcheckinterval() have
been changed. Both the check interval and the ticker used to be
per-thread values. They are now just a pair of global variables.
In addition, the default check interval was boosted from 10 to 100
bytecode instructions. This may have some effect on systems that
relied on the old default value. In particular, in multi-threaded
applications which try to be highly responsive, response time will
increase by some (perhaps imperceptible) amount.
added a bit about the change to the thread ticker
2002-09-03 18:25:14 -03:00
k_mul() and long_mul(): I'm confident that the Karatsuba algorithm is correct now, so added some final comments, did some cleanup, and enabled it for all long-int multiplies. The KARAT envar no longer matters, although I left some #if 0'ed code in there for my own use (temporary). k_mul() is still much slower than x_mul() if the inputs have very differenent sizes, and that still needs to be addressed.
2002-08-12 14:36:03 -03:00
- When multiplying very large integers, a version of the so-called
Karatsuba algorithm is now used. This is most effective if the
inputs have roughly the same size. If they both have about N digits,
Karatsuba multiplication has O(N**1.58) runtime (the exponent is
log_base_2(3)) instead of the previous O(N**2). Measured results may
Newly-relaxed limits on random.randrange(). Also added some info about Karatsuba's better cache behavior with extremely large multiplicands.
2002-08-16 00:40:07 -03:00
be better or worse than that, depending on platform quirks. Besides
the O() improvement in raw instruction count, the Karatsuba algorithm
appears to have much better cache behavior on extremely large integers
(starting in the ballpark of a million bits). Note that this is a
simple implementation, and there's no intent here to compete with,
e.g., GMP. It gives a very nice speedup when it applies, but a package
devoted to fast large-integer arithmetic should run circles around it.
Cautious introduction of a patch that started from SF 560379: Karatsuba multiplication. Lots of things were changed from that. This needs a lot more testing, for correctness and speed, the latter especially when bit lengths are unbalanced. For now, the Karatsuba code gets invoked if and only if envar KARAT exists.
2002-08-11 23:31:19 -03:00
Add C API PyUnicode_FromOrdinal() which exposes unichr() at C level. u'%c' will now raise a ValueError in case the argument is an integer outside the valid range of Unicode code point ordinals. Closes SF bug #593581.
2002-08-11 09:23:04 -03:00
- u'%c' will now raise a ValueError in case the argument is an
integer outside the valid range of Unicode code point ordinals.
News about the tempfile rewrite.
2002-08-09 14:16:30 -03:00
- The tempfile module has been overhauled for enhanced security. The
mktemp() function is now deprecated; new, safe replacements are
mkstemp() (for files) and mkdtemp() (for directories), and the
higher-level functions NamedTemporaryFile() and TemporaryFile().
Use of some global variables in this module is also deprecated; the
new functions have keyword arguments to provide the same
functionality. All Lib, Tools and Demo modules that used the unsafe
interfaces have been updated to use the safe replacements. Thanks
to Zack Weinberg!
News about Neil's fix to correctly invoke __rmul__.
2002-08-09 12:57:34 -03:00
- When x is an object whose class implements __mul__ and __rmul__,
1.0*x would correctly invoke __rmul__, but 1*x would erroneously
invoke __mul__. This was due to the sequence-repeat code in the int
type. This has been fixed now.
Describe new "str1 in str2" behavior.
2002-08-06 14:01:51 -03:00
- Previously, "str1 in str2" required str1 to be a string of length 1.
This restriction has been relaxed to allow str1 to be a string of
any length. Thus "'el' in 'hello world'" returns True now.
Files are now their own iterator. The xreadlines method and module are obsolete.
2002-08-06 13:20:26 -03:00
- File objects are now their own iterators. For a file f, iter(f) now
returns f (unless f is closed), and f.next() is similar to
f.readline() when EOF is not reached; however, f.next() uses a
readahead buffer that messes up the file position, so mixing
f.next() and f.readline() (or other methods) doesn't work right.
Calling f.seek() drops the readahead buffer, but other operations
don't. It so happens that this gives a nice additional speed boost
to "for line in file:"; the xreadlines method and corresponding
Credit to Oren for the file-iterator patch.
2002-08-09 14:17:07 -03:00
module are now obsolete. Thanks to Oren Tirosh!
Files are now their own iterator. The xreadlines method and module are obsolete.
2002-08-06 13:20:26 -03:00
Add a small description of PEP 263.
2002-08-05 11:17:20 -03:00
- Encoding declarations (PEP 263, phase 1) have been implemented. A
comment of the form "# -*- coding: <encodingname> -*-" in the first
or second line of a Python source file indicates the encoding.
Patch #534304: Implement phase 1 of PEP 263.
2002-08-04 14:29:52 -03:00
A blurb about the sort implementation.
2002-07-31 23:34:51 -03:00
- list.sort() has a new implementation. While cross-platform results
may vary, and in data-dependent ways, this is much faster on many
kinds of partially ordered lists than the previous implementation,
and reported to be just as fast on randomly ordered lists on
several major platforms. This sort is also stable (if A==B and A
precedes B in the list at the start, A precedes B after the sort too),
although the language definition does not guarantee stability. A
potential drawback is that list.sort() may require temp space of
fix a couple nits with my use of ReST
2002-09-30 12:23:01 -03:00
len(list)*2 bytes (``*4`` on a 64-bit machine). It's therefore possible
A blurb about the sort implementation.
2002-07-31 23:34:51 -03:00
for list.sort() to raise MemoryError now, even if a comparison function
does not. See <http://www.python.org/sf/587076> for full details.
News about StopIteration as a "sink state".
2002-07-23 00:44:35 -03:00
- All standard iterators now ensure that, once StopIteration has been
raised, all future calls to next() on the same iterator will also
raise StopIteration. There used to be various counterexamples to
this behavior, which could caused confusion or subtle program
breakage, without any benefits. (Note that this is still an
iterator's responsibility; the iterator framework does not enforce
this.)
Add a blurb on the 3 Windows bugs I worked on over the last couple of days.
2002-07-15 22:32:30 -03:00
- Ctrl+C handling on Windows has been made more consistent with
other platforms. KeyboardInterrupt can now reliably be caught,
Fix spelling errors and note the addition of operator.pow()
2002-08-19 11:25:03 -03:00
and Ctrl+C at an interactive prompt no longer terminates the
Add a blurb on the 3 Windows bugs I worked on over the last couple of days.
2002-07-15 22:32:30 -03:00
process under NT/2k/XP (it never did under Win9x). Ctrl+C will
Cautious introduction of a patch that started from SF 560379: Karatsuba multiplication. Lots of things were changed from that. This needs a lot more testing, for correctness and speed, the latter especially when bit lengths are unbalanced. For now, the Karatsuba code gets invoked if and only if envar KARAT exists.
2002-08-11 23:31:19 -03:00
interrupt time.sleep() in the main thread, and any child processes
created via the popen family (on win2k; we can't make win9x work
Clarify that the interruptable popen fixes aren't used under Win9x.
2002-08-10 03:26:31 -03:00
reliably) are also interrupted (as generally happens on for Linux/Unix.)
[SF bugs 231273, 439992 and 581232]
Add a blurb on the 3 Windows bugs I worked on over the last couple of days.
2002-07-15 22:32:30 -03:00
Add os.path.supports_unicode_filenames for all platforms, sys.getwindowsversion() on Windows (new enahanced Tim-proof <wink> version), and fix test_pep277.py in a few minor ways. Including doc and NEWS entries.
2002-10-07 23:44:31 -03:00
- sys.getwindowsversion() has been added on Windows. This
returns a tuple with information about the version of Windows
currently running.
Fix SF bug 546434 -- buffer slice type inconsistent.
2002-06-24 21:25:30 -03:00
- Slices and repetitions of buffer objects now consistently return
a string. Formerly, strings would be returned most of the time,
but a buffer object would be returned when the repetition count
was one or when the slice range was all inclusive.
Apply diff2.txt from SF patch http://www.python.org/sf/566999 This patch enhances Python/import.c/find_module() so that unicode objects found in sys.path will be treated as legal directory names (The current code ignores anything that is not a str). The unicode name is converted to str using Py_FileSystemDefaultEncoding.
2002-06-17 07:43:59 -03:00
- Unicode objects in sys.path are no longer ignored but treated
as directory names.
SF bug # 493951 string.{starts,ends}with vs slices Handle negative indices similar to slices.
2002-06-13 21:50:42 -03:00
- Fixed string.startswith and string.endswith builtin methods
so they accept negative indices. [SF bug 493951]
SF bug 567538: Generator can crash the interpreter (Finn Bock). This was a simple typo. Strange that the compiler didn't catch it! Instead of WHY_CONTINUE, two tests used CONTINUE_LOOP, which isn't a why_code at all, but an opcode; but even though 'why' is declared as an enum, comparing it to an int is apparently not even worth a warning -- not in gcc, and not in VC++. :-( Will fix in 2.2 too.
2002-06-12 00:45:21 -03:00
- Fixed a bug with a continue inside a try block and a yield in the
finally clause. [SF bug 567538]
This is my nearly two year old patch [ 400998 ] experimental support for extended slicing on lists somewhat spruced up and better tested than it was when I wrote it. Includes docs & tests. The whatsnew section needs expanding, and arrays should support extended slices -- later.
2002-06-11 07:55:12 -03:00
- Most builtin sequences now support "extended slices", i.e. slices
Changed the extended slice example to show that you can reverse a string with a [::-1] slice.
2002-06-13 08:41:07 -03:00
with a third "stride" parameter. For example, "hello world"[::-1]
gives "dlrow olleh".
This is my nearly two year old patch [ 400998 ] experimental support for extended slicing on lists somewhat spruced up and better tested than it was when I wrote it. Includes docs & tests. The whatsnew section needs expanding, and arrays should support extended slices -- later.
2002-06-11 07:55:12 -03:00
As discussed on python-dev, add a mechanism to indicate features that are in the process of deprecation (PendingDeprecationWarning). Docs could be improved.
2002-05-29 12:54:55 -03:00
- A new warning PendingDeprecationWarning was added to provide
direction on features which are in the process of being deprecated.
The warning will not be printed by default. To see the pending
deprecations, use -Walways::PendingDeprecationWarning::
as a command line option or warnings.filterwarnings() in code.
Added notes related to the removal of deprecated features of the xrange type.
2002-05-02 18:28:26 -03:00
- Deprecated features of xrange objects have been removed as
promised. The start, stop, and step attributes and the tolist()
method no longer exist. xrange repetition and slicing have been
removed.
- New builtin function enumerate(x), from PEP 279. Example: enumerate("abc") is an iterator returning (0,"a"), (1,"b"), (2,"c"). The argument can be an arbitrary iterable object.
2002-04-26 16:40:56 -03:00
- New builtin function enumerate(x), from PEP 279. Example:
enumerate("abc") is an iterator returning (0,"a"), (1,"b"), (2,"c").
The argument can be an arbitrary iterable object.
If Py_OptimizeFlag is false then always evaluate assert conditions, don't test __debug__ at runtime. Closes SF patch #548833.
2002-04-25 22:58:53 -03:00
- The assert statement no longer tests __debug__ at runtime. This means
that assert statements cannot be disabled by assigning a false value
to __debug__.
Apply the second version of SF patch http://www.python.org/sf/536241 Add a method zfill to str, unicode and UserString and change Lib/string.py accordingly. This activates the zfill version in unicodeobject.c that was commented out and implements the same in stringobject.c. It also adds the test for unicode support in Lib/string.py back in and uses repr() instead() of str() (as it was before Lib/string.py 1.62)
2002-04-15 10:36:47 -03:00
- A method zfill() was added to str and unicode, that fills a numeric
string to the left with zeros. For example,
"+123".zfill(6) -> "+00123".
Add news about deprecated complex ops.
2002-04-15 09:36:47 -03:00
- Complex numbers supported divmod() and the // and % operators, but
these make no sense. Since this was documented, they're being
deprecated now.
Clarify that the strip changes also apply to Unicode.
2002-04-26 17:11:29 -03:00
- String and unicode methods lstrip(), rstrip() and strip() now take
an optional argument that specifies the characters to strip. For
example, "Foo!!!?!?!?".rstrip("?!") -> "Foo".
News for strip methods.
2002-04-12 21:59:05 -03:00
Rephrase dict.fromkeys() news.
2002-11-27 09:10:40 -04:00
- There's a new dictionary constructor (a class method of the dict
class), dict.fromkeys(iterable, value=None). It constructs a
dictionary with keys taken from the iterable and all values set to a
single value. It can be used for building sets and for removing
duplicates from sequences.
SF Patch 643443. Added dict.fromkeys(iterable, value=None), a class method for constructing new dictionaries from sequences of keys.
2002-11-27 03:29:33 -04:00
News about dict.pop().
2002-04-12 16:22:48 -03:00
- Added a new dict method pop(key). This removes and returns the
value corresponding to key. [SF patch #539949]
Add a note about bool.
2002-04-04 11:21:33 -04:00
- A new built-in type, bool, has been added, as well as built-in
names for its two values, True and False. Comparisons and sundry
other operations that return a truth value have been changed to
Fix typos
2002-05-07 17:58:03 -03:00
return a bool instead. Read PEP 285 for an explanation of why this
Add a note about bool.
2002-04-04 11:21:33 -04:00
is backward compatible.
News for SF #535905.
2002-03-28 21:07:24 -04:00
- Fixed two bugs reported as SF #535905: under certain conditions,
deallocating a deeply nested structure could cause a segfault in the
garbage collector, due to interaction with the "trashcan" code;
access to the current frame during destruction of a local variable
could access a pointer to freed memory.
Mention pymemcompat.h.
2002-06-18 18:20:13 -03:00
- The optional object allocator ("pymalloc") has been enabled by
default. The recommended practice for memory allocation and
deallocation has been streamlined. A header file is included,
Misc/pymemcompat.h, which can be bundled with 3rd party extensions
and lets them use the same API with Python versions from 1.5.2
onwards.
Add news about pymalloc being enabled.
2002-03-22 13:06:59 -04:00
Patch #50002: Display line information for bad \x escapes: - recognize "SyntaxError"s by the print_file_and_line attribute. - add the syntaxerror attributes to all exceptions in compile.c. Fixes #221791
2002-03-03 17:30:27 -04:00
- PyErr_Display will provide file and line information for all exceptions
that have an attribute print_file_and_line, not just SyntaxErrors.
Add news about PYC magic and changes to UTF-8 codec.
2002-02-09 07:28:43 -04:00
- The UTF-8 codec will now encode and decode Unicode surrogates
correctly and without raising exceptions for unpaired ones.
Add notes about universal newlines.
2002-08-15 11:01:14 -03:00
- Universal newlines (PEP 278) is implemented. Briefly, using 'U'
instead of 'r' when opening a text file for reading changes the line
ending convention so that any of '\r', '\r\n', and '\n' is
recognized (even mixed in one file); all three are converted to
'\n', the standard Python line end character.
SF Patch #494863, file.xreadlines() should raise ValueError if file is closed This makes xreadlines behave like all other file methods (other than close() which just returns).
2002-01-01 15:07:13 -04:00
- file.xreadlines() now raises a ValueError if the file is closed:
Previously, an xreadlines object was returned which would raise
a ValueError when the xreadlines.next() method was called.
Fix typos
2002-05-07 17:58:03 -03:00
- sys.exit() inadvertently allowed more than one argument.
Change sys_exit to use METH_VARARGS. sys.exit() now requires 0-1 arguments. Previously 2+ arguments were allowed.
2002-03-27 09:03:09 -04:00
An exception will now be raised if more than one argument is used.
Use "dictionary literals" instead of "dictionaries", as suggested by Just.
2002-12-16 10:09:22 -04:00
- Changed evaluation order of dictionary literals to conform to the
general left to right evaluation order rule. Now {f1(): f2()} will
evaluate f1 first.
Fixing bug [#448679] Left to right * Python/compile.c (com_dictmaker): Reordered evaluation of dictionaries to follow strict LTR evaluation. * Lib/compiler/pycodegen.py (CodeGenerator.visitDict): Reordered evaluation of dictionaries to follow strict LTR evaluation. * Doc/ref/ref5.tex Documented the general LTR evaluation order idea. * Misc/NEWS Documented change in evaluation order of dictionaries.
2002-12-16 09:54:02 -04:00
Fixed bug [#521782] unreliable file.read() error handling * Objects/fileobject.c (file_read): Clear errors before leaving the loop in all situations, and also check if some data was read before exiting the loop with an EWOULDBLOCK exception. * Doc/lib/libstdtypes.tex * Objects/fileobject.c Document that sometimes a read() operation can return less data than what the user asked, if running in non-blocking mode. * Misc/NEWS Document the fix.
2002-12-16 14:12:53 -04:00
- Fixed bug #521782: when a file was in non-blocking mode, file.read()
could silently lose data or wrongly throw an unknown error.
Add news about fix for bug #624807.
2002-12-30 16:22:23 -04:00
- The sq_repeat, sq_inplace_repeat, sq_concat and sq_inplace_concat
slots are now always tried after trying the corresponding nb_* slots.
This fixes a number of minor bugs (see bug #624807).
SF #639945 was fixed in alpha 1
2003-01-10 19:29:48 -04:00
- Fix problem with dynamic loading on 64-bit AIX (see bug #639945).
Added 2.3a1 section.
2001-12-21 17:36:50 -04:00
Extension modules
ReST-ification of the NEWS file. While the total number of changes are fairly large, most are caused by reformatting section and subsection headings. The changes fall into the following categories: * reformatted section and subsection headers. * escaped isolated asterisks which would be interpreted as starting bold or italic text (e.g. "void (*)(PyObject \*)"). * quoted stuff that looks like internal references but isn't (e.g. ``PyCmp_``). * changed visually balanced quotes to just use apostrophes (e.g. "'string'" instead of "`string'"). * introduced and indenting multiline chunks of code. * created one table (search for "New codecs").
2002-09-20 11:16:59 -03:00
-----------------
Added 2.3a1 section.
2001-12-21 17:36:50 -04:00
SF patch #670423: Add missing identity tests to operator.c
2003-01-18 19:22:20 -04:00
- Added three operators to the operator module:
operator.pow(a,b) which is equivalent to: a**b.
operator.is_(a,b) which is equivalent to: a is b.
operator.is_not(a,b) which is equivalent to: a is not b.
Patch #656590: /dev/ptmx support for ptys.
2002-12-31 08:55:15 -04:00
- posix.openpty now works on all systems that have /dev/ptmx.
News about zipimport.
2002-12-30 18:59:32 -04:00
- A module zipimport exists to support importing code from zip
archives.
Blurb about new datetime module.
2002-12-16 16:57:22 -04:00
- The new datetime module supplies classes for manipulating dates and
times. The basic design came from the Zope "fishbowl process", and
favors practical commercial applications over calendar esoterica. See
http://www.zope.org/Members/fdrake/DateTimeWiki/FrontPage
Patch #518625: Return objects in Tkinter.
2002-11-26 05:28:05 -04:00
- _tkinter now returns Tcl objects, instead of strings. Objects which
have Python equivalents are converted to Python objects, other objects
are wrapped. This can be configured through the wantobjects method,
Rename want_objects to wantobjects throughout, for consistency.
2002-11-26 17:39:48 -04:00
or Tkinter.wantobjects.
Patch #518625: Return objects in Tkinter.
2002-11-26 05:28:05 -04:00
A short note about the versions of BerkeleyDB we now support
2002-12-30 17:03:26 -04:00
- The PyBSDDB wrapper around the Sleepycat Berkeley DB library has
been added as the package bsddb. The traditional bsddb module is
still available in source code, but not built automatically anymore,
and is now named bsddb185. This supports Berkeley DB versions from
add note about new db2pickle.py and pickle2db.py scripts
2003-02-03 11:17:25 -04:00
3.0 to 4.1. For help converting your databases from the old module (which
probably used an obsolete version of Berkeley DB) to the new module, see
the db2pickle.py and pickle2db.py scripts described in the Tools/Demos
section above.
Document PyBSDDB import.
2002-11-19 04:12:57 -04:00
Patch #626485: Support Unicode normalization.
2002-11-23 18:08:15 -04:00
- unicodedata was updated to Unicode 3.2. It supports normalization
and names for Hangul syllables and CJK unified ideographs.
Patch #626548: Support Hangul syllable names.
2002-11-23 08:22:32 -04:00
Fix SF #632624, test_resource failure on alpha/64bit Return PyLongs instead ot PyInts. On alphas, 9223372036854775807 became -1.
2002-11-02 13:46:24 -04:00
- resource.getrlimit() now returns longs instead of ints.
Document patch #512981.
2002-10-26 11:42:02 -03:00
- readline now dynamically adjusts its input/output stream if
sys.stdin/stdout changes.
Mention droped support for Tcl/Tk 8.0 and 8.1.
2002-10-01 15:18:58 -03:00
- The _tkinter module (and hence Tkinter) has dropped support for
Tcl/Tk 8.0 and 8.1. Only Tcl/Tk versions 8.2, 8.3 and 8.4 are
supported.
Make BadPickleGet a class. Fixes #609164.
2002-09-16 14:26:24 -03:00
- cPickle.BadPickleGet is now a class.
Correct stat_result float time stamps entry.
2002-10-16 15:28:36 -03:00
- The time stamps in os.stat_result are floating point numbers
after stat_float_times has been called.
Patch #606592: Subsecond timestamps in stat_result.
2002-09-09 11:24:16 -03:00
SF bug # 585792, Invalid mmap crashes Python interpreter Raise ValueError if user passes a size to mmap which is larger than the file.
2002-09-05 18:48:07 -03:00
- If the size passed to mmap.mmap() is larger than the length of the
file on non-Windows platforms, a ValueError is raised. [SF bug 585792]
Files are now their own iterator. The xreadlines method and module are obsolete.
2002-08-06 13:20:26 -03:00
- The xreadlines module is slated for obsolescence.
Add news about strptime and socket.setdefaulttimeout().
2002-07-23 00:32:08 -03:00
- The strptime function in the time module is now always available (a
Python implementation is used when the C library doesn't define it).
Add Oren Tirosh and news about his patch.
2002-06-14 18:31:18 -03:00
- The 'new' module is no longer an extension, but a Python module that
only exists for backwards compatibility. Its contents are no longer
functions but callable type objects.
Mostly in SequenceMatcher.{__chain_b, find_longest_match}: This now does a dynamic analysis of which elements are so frequently repeated as to constitute noise. The primary benefit is an enormous speedup in find_longest_match, as the innermost loop can have factors of 100s less potential matches to worry about, in cases where the sequences have many duplicate elements. In effect, this zooms in on sequences of non-ubiquitous elements now. While I like what I've seen of the effects so far, I still consider this experimental. Please give it a try!
2002-04-28 22:37:32 -03:00
- The bsddb.*open functions can now take 'None' as a filename.
SF patch [ 545523 ] patch for 514433 bsddb.dbopen (NULL) closes SF #514433 can now pass 'None' as the filename for the bsddb.*open functions, and you'll get an in-memory temporary store. docs are ripped out of the bsddb dbopen man page. Fred may want to clean them up. Considering this for 2.2, but not 2.1.
2002-04-22 23:11:05 -03:00
This will create a temporary in-memory bsddb that won't be
Mostly in SequenceMatcher.{__chain_b, find_longest_match}: This now does a dynamic analysis of which elements are so frequently repeated as to constitute noise. The primary benefit is an enormous speedup in find_longest_match, as the innermost loop can have factors of 100s less potential matches to worry about, in cases where the sequences have many duplicate elements. In effect, this zooms in on sequences of non-ubiquitous elements now. While I like what I've seen of the effects so far, I still consider this experimental. Please give it a try!
2002-04-28 22:37:32 -03:00
written to disk.
SF patch [ 545523 ] patch for 514433 bsddb.dbopen (NULL) closes SF #514433 can now pass 'None' as the filename for the bsddb.*open functions, and you'll get an in-memory temporary store. docs are ripped out of the bsddb dbopen man page. Fred may want to clean them up. Considering this for 2.2, but not 2.1.
2002-04-22 23:11:05 -03:00
Add getloadavg.
2002-12-31 09:20:15 -04:00
- posix.getloadavg, posix.lchown, posix.killpg, posix.mknod, and
posix.getpgid have been added where available.
Patch #543447: Add posix.mknod.
2002-04-14 07:19:44 -03:00
Add getpreferredencoding. Support @euro modifiers. Fixes #554676. The @euro part is backported to 2.2.3.
2002-11-03 13:20:12 -04:00
- The locale module now exposes the C library's gettext interface. It
also has a new function getpreferredencoding.
Expose C library's gettext. Fixes #516412.
2002-03-27 14:49:02 -04:00
News about zlib-1.1.4.
2002-03-14 15:06:01 -04:00
- A security hole ("double free") was found in zlib-1.1.3, a popular
third party compression library used by some Python modules. The
hole was quickly plugged in zlib-1.1.4, and the Windows build of
Python now ships with zlib-1.1.4.
Patch #512005: getrusage() returns struct-like object.
2002-04-08 18:28:20 -03:00
- pwd, grp, and resource return enhanced tuples now, with symbolic
field names.
Patch #523268, #522027: return enhanced tuples.
2002-03-01 06:47:37 -04:00
Patch 520694: arraymodule.c improvements: - make array.array a type - add Py_UNICODE arrays - support +=, *=
2002-03-01 06:27:01 -04:00
- array.array is now a type object. A new format character
'u' indicates Py_UNICODE arrays. For those, .tounicode and
.fromunicode methods are available. Arrays now support __iadd__
and __imul__.
Improve grammar
2002-01-01 17:14:12 -04:00
- dl now builds on every system that has dlfcn.h. Failure in case
Patch #497126: Always compile dl.
2002-01-01 16:18:30 -04:00
of sizeof(int)!=sizeof(long)!=sizeof(void*) is delayed until dl.open
is called.
expose PYTHON_API_VERSION macro as sys.api_version. Closes patch # 601456.
2002-09-03 10:25:17 -03:00
- The sys module acquired a new attribute, api_version, which evaluates
to the value of the PYTHON_API_VERSION macro with which the
interpreter was compiled.
Fixed bug #470582, using a modified version of patch #527371, from Greg Chapman. * Modules/_sre.c (lastmark_restore): New function, implementing algorithm to restore a state to a given lastmark. In addition to the similar algorithm used in a few places of SRE_MATCH, restore lastindex when restoring lastmark. (SRE_MATCH): Replace lastmark inline restoring by lastmark_restore(), function. Also include it where missing. In SRE_OP_MARK, set lastindex only if i > lastmark. * Lib/test/re_tests.py * Lib/test/test_sre.py Included regression tests for the fixed bugs. * Misc/NEWS Mention fixes.
2002-11-06 10:06:53 -04:00
- Fixed bug #470582: sre module would return a tuple (None, 'a', 'ab')
when applying the regular expression '^((a)c)?(ab)$' on 'ab'. It now
returns (None, None, 'ab'), as expected. Also fixed handling of
Fixed bug "[#466200] ability to specify a 'verify' script". * Lib/distutils/command/bdist_rpm.py (bdist_rpm.initialize_options): Included verify_script attribute. (bdist_rpm.finalize_package_data): Ensure that verify_script is a filename. (bdist_rpm._make_spec_file): Included verify_script in script_options tuple. * Misc/NEWS Mention change.
2002-11-06 14:44:26 -04:00
lastindex/lastgroup match attributes in similar cases. For example,
Fixed bug #470582, using a modified version of patch #527371, from Greg Chapman. * Modules/_sre.c (lastmark_restore): New function, implementing algorithm to restore a state to a given lastmark. In addition to the similar algorithm used in a few places of SRE_MATCH, restore lastindex when restoring lastmark. (SRE_MATCH): Replace lastmark inline restoring by lastmark_restore(), function. Also include it where missing. In SRE_OP_MARK, set lastindex only if i > lastmark. * Lib/test/re_tests.py * Lib/test/test_sre.py Included regression tests for the fixed bugs. * Misc/NEWS Mention fixes.
2002-11-06 10:06:53 -04:00
when running the expression r'(a)(b)?b' over 'ab', lastindex must be
1, not 2.
Fixed sre bug "[#581080] Provoking infinite scanner loops". This bug happened because: 1) the scanner_search and scanner_match methods were not checking the buffer limits before increasing the current pointer; and 2) SRE_SEARCH was using "if (ptr == end)" as a loop break, instead of "if (ptr >= end)". * Modules/_sre.c (SRE_SEARCH): Check for "ptr >= end" to break loops, so that we don't hang forever if a pointer passing the buffer limit is used. (scanner_search,scanner_match): Don't increment the current pointer if we're going to pass the buffer limit. * Misc/NEWS Mention the fix.
2002-11-06 23:28:56 -04:00
- Fixed bug #581080: sre scanner was not checking the buffer limit
before increasing the current pointer. This was creating an infinite
loop in the search function, once the pointer exceeded the buffer
limit.
NEWS entry for the changed fdopen function.
2002-11-07 12:23:55 -04:00
- The os.fdopen function now enforces a file mode starting with the
letter 'r', 'w' or 'a', otherwise a ValueError is raised. This fixes
bug #623464.
Mention ossaudiodev.
2003-01-03 14:02:15 -04:00
- The linuxaudiodev module is now deprecated; it is being replaced by
ossaudiodev. The interface has been extended to cover a lot more of
OSS (see www.opensound.com), including most DSP ioctls and the
OSS mixer API. Documentation forthcoming in 2.3a2.
Added 2.3a1 section.
2001-12-21 17:36:50 -04:00
Library
ReST-ification of the NEWS file. While the total number of changes are fairly large, most are caused by reformatting section and subsection headings. The changes fall into the following categories: * reformatted section and subsection headers. * escaped isolated asterisks which would be interpreted as starting bold or italic text (e.g. "void (*)(PyObject \*)"). * quoted stuff that looks like internal references but isn't (e.g. ``PyCmp_``). * changed visually balanced quotes to just use apostrophes (e.g. "'string'" instead of "`string'"). * introduced and indenting multiline chunks of code. * created one table (search for "New codecs").
2002-09-20 11:16:59 -03:00
-------
Added 2.3a1 section.
2001-12-21 17:36:50 -04:00
Mention that imaplib now supports SSL -- this wasn't noted before.
2003-01-03 12:33:49 -04:00
- imaplib.py now supports SSL (Tino Lange and Piers Lauder).
modulefinder.py moved to Lib/
2002-12-31 12:38:01 -04:00
- Freeze's modulefinder.py has been moved to the standard library;
slightly improved so it will issue less false missing submodule
reports (see sf path #643711 for details). Documentation will follow
with Python 2.3a2.
Patch #658927: Add getctime to os.path. Document that getatime and getmtime may return floats.
2002-12-31 09:11:54 -04:00
- os.path exposes getctime.
Add newsitem for the two new unittest methods. Also, made some whitespace cleanup.
2002-12-29 16:14:11 -04:00
- unittest.py now has two additional methods called assertAlmostEqual()
Fix spelling.
2003-03-11 17:43:55 -04:00
and failIfAlmostEqual(). They implement an approximate comparison
Add newsitem for the two new unittest methods. Also, made some whitespace cleanup.
2002-12-29 16:14:11 -04:00
by rounding the difference between the two arguments and comparing
Fix spelling.
2003-03-11 17:43:55 -04:00
the result to zero. Approximate comparison is essential for
Add newsitem for the two new unittest methods. Also, made some whitespace cleanup.
2002-12-29 16:14:11 -04:00
unit tests of floating point results.
SF 658405: calendar.py to rely on the datetime module instead of the time module. The code is shorter, more readable, faster, and dramatically increases the range of acceptable dates. Also, used the floor division operator in leapdays().
2002-12-25 12:37:19 -04:00
- calendar.py now depends on the new datetime module rather than
the time module. As a result, the range of allowable dates
has been increased.
This is Richie Hindle's patch [ 643835 ] Set Next Statement for Python debuggers with a few tweaks by me: adding an unsigned or two, mentioning that not all jumps are allowed in the doc for pdb, adding a NEWS item and a note to whatsnew, and AuCTeX doing something cosmetic to libpdb.tex.
2002-12-17 12:15:34 -04:00
- pdb has a new 'j(ump)' command to select the next line to be
executed.
Mention the bdist_wininst postinstall script.
2002-12-12 15:13:44 -04:00
- The distutils created windows installers now can run a
postinstallation script.
Patch #486438: Make module argument to testmod optional.
2002-11-22 04:23:09 -04:00
- doctest.testmod can now be called without argument, which means to
test the current module.
Fix spelling.
2003-03-11 17:43:55 -04:00
- When canceling a server that implemented threading with a keyboard
Patch #550765: Add daemon_threads flag.
2002-11-22 04:08:44 -04:00
interrupt, the server would shut down but not terminate (waiting on
client threads). A new member variable, daemon_threads, was added to
the ThreadingMixIn class in SocketServer.py to make it explicit that
this behavior needs to be controlled.
Add Optik news.
2002-11-15 09:19:58 -04:00
- A new module, optparse, provides a fancy alternative to getopt for
Fix minor nits Trim excess whitespace off one line
2002-11-15 10:42:34 -04:00
command line parsing. It is a slightly modified version of Greg
Add Optik news.
2002-11-15 09:19:58 -04:00
Ward's Optik package.
SF patch #520382: Expand shelve.py to have a full dictionary interface and add a mixin to UserDict.py to make it easier to implement a full dictionary interface.
2002-11-15 02:46:14 -04:00
- UserDict.py now defines a DictMixin class which defines all dictionary
methods for classes that already have a minimum mapping interface.
This greatly simplifies writing classes that need to be substitutable
for dictionaries (such as the shelve module).
- shelve.py now subclasses from UserDict.DictMixin. Now shelve supports
all dictionary methods. This eases the transition to persistent
Fix minor nits Trim excess whitespace off one line
2002-11-15 10:42:34 -04:00
storage for scripts originally written with dictionaries in mind.
SF patch #520382: Expand shelve.py to have a full dictionary interface and add a mixin to UserDict.py to make it easier to implement a full dictionary interface.
2002-11-15 02:46:14 -04:00
Add support for binary pickles to the shelve module. In some situations this can result in significantly smaller files. All classes as well as the open function now accept an optional binary parameter, which defaults to False for backward compatibility. Added a small test suite, updated the libref documentation (including documenting the exported classes and fixing a few other nits) and added a note about the change to Misc/NEWS.
2002-12-08 14:36:24 -04:00
- shelve.open and the various classes in shelve.py now accept an optional
binary flag, which defaults to False. If True, the values stored in the
shelf are binary pickles.
News about the logging module.
2002-11-13 12:29:18 -04:00
- A new package, logging, implements the logging API defined by PEP
282. The code is written by Vinay Sajip.
Add next() and __iter__() methods to StreamReader, StreamReaderWriter and StreamRecoder. This closes SF bug #634246.
2002-11-06 12:53:44 -04:00
- StreamReader, StreamReaderWriter and StreamRecoder in the codecs
modules are iterators now.
Another round on SF patch 618135: gzip.py and files > 2G The last round boosted "the limit" from 2GB to 4GB. This round gets rid of the 4GB limit. For files > 4GB, gzip stores just the last 32 bits of the file size, and now we play along with that too. Tested by hand (on a 6+GB file) on Win2K. Boosting from 2GB to 4GB was arguably enough "a bugfix". Going beyond that smells more like "new feature" to me.
2002-11-05 16:38:55 -04:00
- gzip.py now handles files exceeding 2GB. Files over 4GB also work
now (provided the OS supports it, and Python is configured with large
file support), but in that case the underlying gzip file format can
record only the least-significant 32 bits of the file size, so that
some tools working with gzipped files may report an incorrect file
size.
Related to SF patch 618135: gzip.py and files > 2G. Fixed the signed/unsigned confusions when dealing with files >= 2GB. 4GB is still a hard limitation of the gzip file format, though. Testing this was a bitch on Win98SE due to frequent system freezes. It didn't freeze while running gzip, it kept freezing while trying to *create* a > 2GB test file! This wasn't Python's doing. I don't know of a reasonable way to test this functionality in regrtest.py, so I'm not checking in a test case (a test case would necessarily require creating a 2GB+ file first, using gzip to zip it, using gzip to unzip it again, and then compare before-and-after; so >4GB free space would be required, and a loooong time; I did all this "by hand" once). Bugfix candidate, I guess.
2002-11-04 15:50:11 -04:00
Patch #613256: Add nescape method to xml.sax.saxutils.
2002-10-26 11:50:45 -03:00
- xml.sax.saxutils.unescape has been added, to replace entity references
with their entity value.
Patch #572628: Optional timeouts for put and get.
2002-10-15 12:11:13 -03:00
- Queue.Queue.{put,get} now support an optional timeout argument.
Patch #621891: Add askopenfile{name}s.
2002-10-13 07:28:04 -03:00
- Various features of Tk 8.4 are exposed in Tkinter.py. The multiple
option of tkFileDialog is exposed as function askopenfile{,name}s.
Patch #621205: Tkinter updates for tk8.4.
2002-10-13 07:22:08 -03:00
Patch #621891: Add askopenfile{name}s.
2002-10-13 07:28:04 -03:00
- Various configure methods of Tkinter have been stream-lined, so that
tag_configure, image_configure, window_configure now return a
Related to SF patch 618135: gzip.py and files > 2G. Fixed the signed/unsigned confusions when dealing with files >= 2GB. 4GB is still a hard limitation of the gzip file format, though. Testing this was a bitch on Win98SE due to frequent system freezes. It didn't freeze while running gzip, it kept freezing while trying to *create* a > 2GB test file! This wasn't Python's doing. I don't know of a reasonable way to test this functionality in regrtest.py, so I'm not checking in a test case (a test case would necessarily require creating a 2GB+ file first, using gzip to zip it, using gzip to unzip it again, and then compare before-and-after; so >4GB free space would be required, and a loooong time; I did all this "by hand" once). Bugfix candidate, I guess.
2002-11-04 15:50:11 -04:00
dictionary when invoked with no argument.
Patch #612602: Streamline configure methods.
2002-10-10 11:36:13 -03:00
News about repr() and 8-bit characters, and setlocale() in the readline module.
2002-10-09 18:40:48 -03:00
- Importing the readline module now no longer has the side effect of
calling setlocale(LC_CTYPE, ""). The initial "C" locale, or
whatever locale is explicitly set by the user, is preserved. If you
want repr() of 8-bit strings in your preferred encoding to preserve
all printable characters of that encoding, you have to add the
following code to your $PYTHONSTARTUP file or to your application's
main():
import locale
locale.setlocale(locale.LC_CTYPE, "")
Patch #448038: Add move(). Report errors from copytree as in shutil.Error.
2002-10-07 10:23:24 -03:00
- shutil.move was added. shutil.copytree now reports errors as an
exception at the end, instead of printing error messages.
News item about the new encoding normalization scheme.
2002-10-04 08:55:21 -03:00
- Encoding name normalization was generalized to not only
replace hyphens with underscores, but also all other non-alphanumeric
characters (with the exception of the dot which is used for Python
package names during lookup). The aliases.py mapping was updated
to the new standard.
Apply diff3.txt (plus additional documentation) from SF patch http://www.python.org/sf/554192 This adds two new functions to mimetypes: guess_all_extensions() which returns a list of all known extensions for a mime type, and add_type() which adds one mapping between a mime type and an extension.
2002-09-06 13:15:58 -03:00
- mimetypes has two new functions: guess_all_extensions() which
returns a list of all known extensions for a mime type, and
add_type() which adds one mapping between a mime type and
an extension to the database.
News about sets. (There's no documentation; if someone wants to convert the doc strings to LaTeX, be my guest.)
2002-08-19 13:25:46 -03:00
- New module: sets, defines the class Set that implements a mutable
set type using the keys of a dict to represent the set. There's
also a class ImmutableSet which is useful when you need sets of sets
or when you need to use sets as dict keys, and a class BaseSet which
Docs were added about a month ago
2002-12-09 04:56:06 -04:00
is the base class of the two.
News about sets. (There's no documentation; if someone wants to convert the doc strings to LaTeX, be my guest.)
2002-08-19 13:25:46 -03:00
SF patch 629637: Add sample(population, k) method to the random module. Used for random sampling without replacement.
2002-11-12 13:41:57 -04:00
- Added random.sample(population,k) for random sampling without replacement.
SF patch 637176: list.sort crasher Armin Rigo's Draconian but effective fix for SF bug 453523: list.sort crasher slightly fiddled to catch more cases of list mutation. The dreaded internal "immutable list type" is gone! OTOH, if you look at a list *while* it's being sorted now, it will appear to be empty. Better than a core dump.
2002-11-12 18:08:10 -04:00
Returns a k length list of unique elements chosen from the population.
SF patch 629637: Add sample(population, k) method to the random module. Used for random sampling without replacement.
2002-11-12 13:41:57 -04:00
Newly-relaxed limits on random.randrange(). Also added some info about Karatsuba's better cache behavior with extremely large multiplicands.
2002-08-16 00:40:07 -03:00
- random.randrange(-sys.maxint-1, sys.maxint) no longer raises
OverflowError. That is, it now accepts any combination of 'start'
and 'stop' arguments so long as each is in the range of Python's
bounded integers.
SF patch 658251: Install a C implementation of the Mersenne Twister as the core generator for random.py.
2002-12-29 19:03:38 -04:00
- Thanks to Raymond Hettinger, random.random() now uses a new core
generator. The Mersenne Twister algorithm is implemented in C,
threadsafe, faster than the previous generator, has an astronomically
large period (2**19937-1), creates random floats to full 53-bit
precision, and may be the most widely tested random number generator
in existence.
The random.jumpahead(n) method has different semantics for the new
generator. Instead of jumping n steps ahead, it uses n and the
existing state to create a new state. This means that jumpahead()
continues to support multi-threaded code needing generators of
non-overlapping sequences. However, it will break code which relies
on jumpahead moving a specific number of steps forward.
The attributes random.whseed and random.__whseed have no meaning for
the new generator. Code using these attributes should switch to a
new class, random.WichmannHill which is provided for backward
compatibility and to make an alternate generator available.
Adding the heap queue algorithm, per discussion in python-dev last week.
2002-08-02 15:05:20 -03:00
- New "algorithms" module: heapq, implements a heap queue. Thanks to
Kevin O'Connor for the code and Fran<61>ois Pinard for an entertaining
write-up explaining the theory and practical uses of heaps.
Mention new encoding.
2002-07-12 11:40:04 -03:00
- New encoding for the Palm OS character set: palmos.
Removed WITH_CYCLE_GC #ifdef-ery. Holes: + I'm not sure what to do about configure.in. Left it alone. + Ditto pyexpat.c. Fred or Martin will know what to do.
2002-07-07 00:59:34 -03:00
- binascii.crc32() and the zipfile module had problems on some 64-bit
platforms. These have been fixed. On a platform with 8-byte C longs,
crc32() now returns a signed-extended 4-byte result, so that its value
as a Python int is equal to the value computed a 32-bit platform.
Implement the encoding argument for toxml and toprettyxml. Document toprettyxml.
2002-06-30 12:05:00 -03:00
- xml.dom.minidom.toxml and toprettyxml now take an optional encoding
argument.
Record the latest fixes.
2002-06-10 18:39:42 -03:00
- Some fixes in the copy module: when an object is copied through its
__reduce__ method, there was no check for a __setstate__ method on
the result [SF patch 565085]; deepcopy should treat instances of
custom metaclasses the same way it treats instances of type 'type'
[SF patch 560794].
Add timeout mode. Clarify gnu_getopt.
2002-06-07 09:40:52 -03:00
- Sockets now support timeout mode. After s.settimeout(T), where T is
a float expressing seconds, subsequent operations raise an exception
if they cannot be completed within T seconds. To disable timeout
Add news about strptime and socket.setdefaulttimeout().
2002-07-23 00:32:08 -03:00
mode, use s.settimeout(None). There's also a module function,
socket.setdefaulttimeout(T), which sets the default for all sockets
created henceforth.
Add timeout mode. Clarify gnu_getopt.
2002-06-07 09:40:52 -03:00
- getopt.gnu_getopt was added. This supports GNU-style option
processing, where options can be mixed with non-option arguments.
Patch 473512: add GNU style scanning as gnu_getopt.
2002-06-06 07:58:36 -03:00
Fiddle wording.
2002-06-04 15:27:35 -03:00
- Stop using strings for exceptions. String objects used for
exceptions are now classes deriving from Exception. The objects
changed were: Tkinter.TclError, bdb.BdbQuit, macpath.norm_error,
tabnanny.NannyNag, and xdrlib.Error.
Fix SF bug #557436, TclError is a str should be an Exception Make Tkinter.TclError derive from Exception, it was a string.
2002-06-04 14:14:07 -03:00
Add constants BOM_UTF8, BOM_UTF16, BOM_UTF16_LE, BOM_UTF16_BE, BOM_UTF32, BOM_UTF32_LE and BOM_UTF32_BE that represent the Byte Order Mark in UTF-8, UTF-16 and UTF-32 encodings for little and big endian systems. The old names BOM32_* and BOM64_* were off by a factor of 2. This closes SF bug http://www.python.org/sf/555360
2002-06-04 12:16:29 -03:00
- Constants BOM_UTF8, BOM_UTF16, BOM_UTF16_LE, BOM_UTF16_BE,
BOM_UTF32, BOM_UTF32_LE and BOM_UTF32_BE that represent the Byte
Order Mark in UTF-8, UTF-16 and UTF-32 encodings for little and
big endian systems were added to the codecs module. The old names
BOM32_* and BOM64_* were off by a factor of 2.
Minor tweaks to existing items (radian/degree, and UTF-16 readers..
2002-06-18 17:43:18 -03:00
- Added conversion functions math.degrees() and math.radians().
Noted SF patch 552452 adding degree/radian conversions to mathmodule.c.
2002-05-13 01:17:32 -03:00
Apply SF patch 652930: Add optional base argument to math.log(x[, base]).
2002-12-14 15:51:34 -04:00
- math.log() now takes an optional argument: math.log(x[, base]).
Noted change in ftplib 1.68 closing SF patch 553277.
2002-05-12 03:07:21 -03:00
- ftplib.retrlines() now tests for callback is None rather than testing
for False. Was causing an error when given a callback object which
was callable but also returned len() as zero. The change may
create new breakage if the caller relied on the undocumented behavior
and called with callback set to [] or some other False value not
identical to None.
random.gauss() uses a piece of hidden state used by nothing else, and the .seed() and .whseed() methods failed to reset it. In other words, setting the seed didn't completely determine the sequence of results produced by random.gauss(). It does now. Programs repeatedly mixing calls to a seed method with calls to gauss() may see different results now. Bugfix candidate (random.gauss() has always been broken in this way), despite that it may change results.
2002-05-05 17:40:00 -03:00
- random.gauss() uses a piece of hidden state used by nothing else,
and the .seed() and .whseed() methods failed to reset it. In other
words, setting the seed didn't completely determine the sequence of
results produced by random.gauss(). It does now. Programs repeatedly
mixing calls to a seed method with calls to gauss() may see different
results now.
Add Pickler.clear_memo() so the pickle and cPickle modules are more similar.
2002-05-01 17:33:53 -03:00
- The pickle.Pickler class grew a clear_memo() method to mimic that
provided by cPickle.Pickler.
Mostly in SequenceMatcher.{__chain_b, find_longest_match}: This now does a dynamic analysis of which elements are so frequently repeated as to constitute noise. The primary benefit is an enormous speedup in find_longest_match, as the innermost loop can have factors of 100s less potential matches to worry about, in cases where the sequences have many duplicate elements. In effect, this zooms in on sequences of non-ubiquitous elements now. While I like what I've seen of the effects so far, I still consider this experimental. Please give it a try!
2002-04-28 22:37:32 -03:00
- difflib's SequenceMatcher class now does a dynamic analysis of
which elements are so frequent as to constitute noise. For
comparing files as sequences of lines, this generally works better
than the IS_LINE_JUNK function, and function ndiff's linejunk
argument defaults to None now as a result. A happy benefit is
that SequenceMatcher may run much faster now when applied
to large files with many duplicate lines (for example, C program
text with lots of repeated "}" and "return NULL;" lines).
SF patch 546244 by John Williams: add Text.dump() method.
2002-04-23 10:29:43 -03:00
- New Text.dump() method in Tkinter module.
Added note about new distutils commands.
2002-04-17 17:33:40 -03:00
- New distutils commands for building packagers were added to
support pkgtool on Solaris and swinstall on HP-UX.
- distutils now has a new abstract binary packager base class
command/bdist_packager, which simplifies writing packagers.
This will hopefully provide the missing bits to encourage
people to submit more packagers, e.g. for Debian, FreeBSD
and other systems.
Minor tweaks to existing items (radian/degree, and UTF-16 readers..
2002-06-18 17:43:18 -03:00
- The UTF-16, -LE and -BE stream readers now raise a
NotImplementedError for all calls to .readline(). Previously, they
used to just produce garbage or fail with an encoding error --
UTF-16 is a 2-byte encoding and the C lib's line reading APIs don't
Comment about UTF-16 changes.
2002-04-05 08:15:05 -04:00
work well with these.
Patch #495598: add an -q (quiet) option to pycompile.
2002-03-18 08:44:08 -04:00
- compileall now supports quiet operation.
Fix typos
2002-05-07 17:58:03 -03:00
- The BaseHTTPServer now implements optional HTTP/1.1 persistent
Patch #430706: Persistent connections in BaseHTTPServer.
2002-03-17 14:37:22 -04:00
connections.
Break SSL support out of _socket module and place it into a new helper module _ssl. The support for the RAND_* APIs in _ssl is now only enabled for OpenSSL 0.9.5 and up since they were added in that release. Note that socketmodule.* should really be renamed to _socket.* -- unfortunately, this seems to lose the CVS history of the file. Please review and test... I was only able to test the header file chaos in socketmodule.c/h on Linux. The test run through fine and compiles don't give errors or warnings. WARNING: This patch does *not* include changes to the various non-Unix build process files.
2002-02-16 14:23:30 -04:00
- socket module: the SSL support was broken out of the main
_socket module C helper and placed into a new _ssl helper
which now gets imported by socket.py if available and working.
News about the new alias support.
2002-02-10 17:42:47 -04:00
- encodings package: added aliases for all supported IANA character
sets
SF patch #497420 (Eduardo Pérez): ftplib: ftp anonymous password Instead of sending the real user and host, use "anonymous@" (i.e. no host name at all!) as the default anonymous FTP password. This avoids privacy violations.
2001-12-28 16:57:14 -04:00
- ftplib: to safeguard the user's privacy, anonymous login will use
"anonymous@" as default password, rather than the real user and host
name.
Added item about the webbrowser security fix.
2002-01-10 09:50:31 -04:00
- webbrowser: tightened up the command passed to os.system() so that
arbitrary shell code can't be executed because a bogus URL was
passed in.
New tempfile and os.open() gimmicks for Windows.
2002-01-31 20:52:29 -04:00
- gettext.translation has an optional fallback argument, and
Add a per-message fallback mechanism for translations.
2002-01-11 02:58:49 -04:00
gettext.find an optional all argument. Translations will now fallback
Patch #633547: Support plural forms. Do TODOs in test suite.
2002-11-21 17:45:32 -04:00
on a per-message basis. The module supports plural forms, by means
of gettext.[d]ngettext and Translation.[u]ngettext.
Add fallback argument to translation(). Request fallbacks on install. Fixes #500595.
2002-01-11 02:33:28 -04:00
Patch #414775: Add --skip-build option to bdist command.
2002-01-12 07:27:42 -04:00
- distutils bdist commands now offer a --skip-build option.
[Apply SF patch #504943] This patch makes it possible to pass Warning instances as the first argument to warnings.warn. In this case the category argument will be ignored. The message text used will be str(warninginstance).
2002-03-21 06:38:40 -04:00
- warnings.warn now accepts a Warning instance as first argument.
Add note about changes in xml.sax.expatreader.
2002-04-04 15:36:15 -04:00
- The xml.sax.expatreader.ExpatParser class will no longer create
circular references by using itself as the locator that gets passed
to the content handler implementation. [SF bug #535474]
Add a bit of news about the email package fixes.
2002-05-19 21:14:24 -03:00
- The email.Parser.Parser class now properly parses strings regardless
of their line endings, which can be any of \r, \n, or \r\n (CR, LF,
or CRLF). Also, the Header class's constructor default arguments
has changed slightly so that an explicit maxlinelen value is always
Update the email package news.
2002-12-30 15:27:08 -04:00
honored, and so unicode conversion error handling can be specified.
Add a bit of news about the email package fixes.
2002-05-19 21:14:24 -03:00
Fixed markup.
2003-01-02 23:30:21 -04:00
- distutils' build_ext command now links C++ extensions with the C++
Patch implementing bz2 module. * setup.py (PyBuildExt.detect_modules): Included bz2 module detection. * Modules/bz2module.c * Lib/test/test_bz2.py * Doc/lib/libbz2.tex Included files implementing, testing, and documenting bz2 module. * Doc/Makefile.deps * Doc/lib/lib.tex Include references to libbz2.tex. * Misc/NEWS (Library): Mention distutils' c++ linkage patch, and new bz2 module.
2002-11-05 12:50:05 -04:00
compiler available in the Makefile or CXX environment variable, if
Fixed markup.
2003-01-02 23:30:21 -04:00
running under \*nix.
Patch implementing bz2 module. * setup.py (PyBuildExt.detect_modules): Included bz2 module detection. * Modules/bz2module.c * Lib/test/test_bz2.py * Doc/lib/libbz2.tex Included files implementing, testing, and documenting bz2 module. * Doc/Makefile.deps * Doc/lib/lib.tex Include references to libbz2.tex. * Misc/NEWS (Library): Mention distutils' c++ linkage patch, and new bz2 module.
2002-11-05 12:50:05 -04:00
- New module bz2: provides a comprehensive interface for the bz2 compression
library. It implements a complete file interface, one-shot (de)compression
functions, and types for sequential (de)compression.
Fixed markup.
2003-01-02 23:30:21 -04:00
- New pdb command 'pp' which is like 'p' except that it pretty-prints
Add an entry for pdb's new `pp' command.
2002-11-05 18:41:33 -04:00
the value of its expression argument.
Fixed bug "[#466200] ability to specify a 'verify' script". * Lib/distutils/command/bdist_rpm.py (bdist_rpm.initialize_options): Included verify_script attribute. (bdist_rpm.finalize_package_data): Ensure that verify_script is a filename. (bdist_rpm._make_spec_file): Included verify_script in script_options tuple. * Misc/NEWS Mention change.
2002-11-06 14:44:26 -04:00
- Now bdist_rpm distutils command understands a verify_script option in
the config file, including the contents of the referred filename in
the "%verifyscript" section of the rpm spec file.
Fixed bug [#495695] webbrowser.py: selection of browser * Lib/webbrowser.py Only include graphic browsers in _tryorder if DISPLAY is set. Also, included skipstone support, as suggested by Fred in the mentioned bug. * Misc/NEWS Mention fix and skipstone inclusion.
2002-11-25 13:25:04 -04:00
- Fixed bug #495695: webbrowser module would run graphic browsers in a
unix environment even if DISPLAY was not set. Also, support for
skipstone browser was included.
Applying patch [#636769] Fix for major rexec bugs * Lib/rexec.py (FileBase): Added 'xreadlines' and '__iter__' to allowed file methods. (FileWrapper.__init__): Removed unnecessary self.f variable, which gave direct access to the file object. (RExec): Added 'xreadlines' and '_weakref' to allowed modules. (RExec.r_open): Convert string subclasses to a real string classes before doing comparisons with mode parameter. * Lib/ihooks.py (BasicModuleImporter.import_module/reload/unload): Convert the module name to a real string before working with it. (ModuleImporter.import_module/import_it/reload): Convert the module name to a real strings before working with it. * Misc/NEWS Document the change.
2002-12-16 09:11:57 -04:00
- Fixed bug #636769: rexec would run unallowed code if subclasses of
strings were used as parameters for certain functions.
Added 2.3a1 section.
2001-12-21 17:36:50 -04:00
Tools/Demos
ReST-ification of the NEWS file. While the total number of changes are fairly large, most are caused by reformatting section and subsection headings. The changes fall into the following categories: * reformatted section and subsection headers. * escaped isolated asterisks which would be interpreted as starting bold or italic text (e.g. "void (*)(PyObject \*)"). * quoted stuff that looks like internal references but isn't (e.g. ``PyCmp_``). * changed visually balanced quotes to just use apostrophes (e.g. "'string'" instead of "`string'"). * introduced and indenting multiline chunks of code. * created one table (search for "New codecs").
2002-09-20 11:16:59 -03:00
-----------
Added 2.3a1 section.
2001-12-21 17:36:50 -04:00
Patch #494845: Support string concatenation, detect non-string data, add globbing support, find modules by name instead of by file.
2002-11-22 04:36:54 -04:00
- pygettext.py now supports globbing on Windows, and accepts module
names in addition to accepting file names.
The SGI demos are gone.
2002-09-17 17:58:59 -03:00
- The SGI demos (Demo/sgi) have been removed. Nobody thought they
were interesting any more. (The SGI library modules and extensions
are still there; it is believed that at least some of these are
still used and useful.)
Typo: "now" --> "the new"
2002-08-05 12:24:19 -03:00
- IDLE supports the new encoding declarations (PEP 263); it can also
deal with legacy 8-bit files if they use the locale's encoding. It
allows non-ASCII strings in the interactive shell and executes them
in the locale's encoding.
IDLE support for PEP 263.
2002-08-05 12:11:26 -03:00
Added note about updated freeze.py Tool.
2002-04-04 12:17:11 -04:00
- freeze.py now produces binaries which can import shared modules,
unlike before when this failed due to missing symbol exports in
the generated binary.
Added 2.3a1 section.
2001-12-21 17:36:50 -04:00
Build
ReST-ification of the NEWS file. While the total number of changes are fairly large, most are caused by reformatting section and subsection headings. The changes fall into the following categories: * reformatted section and subsection headers. * escaped isolated asterisks which would be interpreted as starting bold or italic text (e.g. "void (*)(PyObject \*)"). * quoted stuff that looks like internal references but isn't (e.g. ``PyCmp_``). * changed visually balanced quotes to just use apostrophes (e.g. "'string'" instead of "`string'"). * introduced and indenting multiline chunks of code. * created one table (search for "New codecs").
2002-09-20 11:16:59 -03:00
-----
Added 2.3a1 section.
2001-12-21 17:36:50 -04:00
Add --check-tkinter to setup.py. Install IDLE. Fixes #634078.
2002-11-06 17:59:33 -04:00
- On Unix, IDLE is now installed automatically.
Disable building of the fpectl module -- it's dangerous or useless except in the hands of experts. Will backport to 2.2.2.
2002-09-25 12:02:44 -03:00
- The fpectl module is not built by default; it's dangerous or useless
except in the hands of experts.
A blurb about the sort implementation.
2002-07-31 23:34:51 -03:00
- The public Python C API will generally be declared using PyAPI_FUNC
Disable building of the fpectl module -- it's dangerous or useless except in the hands of experts. Will backport to 2.2.2.
2002-09-25 12:02:44 -03:00
and PyAPI_DATA macros, while Python extension module init functions
will be declared with PyMODINIT_FUNC. DL_EXPORT/DL_IMPORT macros
are deprecated.
Move DL_IMPORT/DL_EXPORT to Build section, I think this is the correct place
2002-07-22 10:21:10 -03:00
SF bug 578752: COUNT_ALLOCS vs heap types Repair segfaults and infinite loops in COUNT_ALLOCS builds in the presence of new-style (heap-allocated) classes/types. Bugfix candidate. I'll backport this to 2.2. It's irrelevant in 2.1.
2002-07-08 19:11:52 -03:00
- A bug was fixed that could cause COUNT_ALLOCS builds to segfault, or
get into infinite loops, when a new-style class got garbage-collected.
Unfortunately, to avoid this, the way COUNT_ALLOCS works requires
that new-style classes be immortal in COUNT_ALLOCS builds. Note that
COUNT_ALLOCS is not enabled by default, in either release or debug
builds, and that new-style classes are immortal only in COUNT_ALLOCS
builds.
Removed WITH_CYCLE_GC #ifdef-ery. Holes: + I'm not sure what to do about configure.in. Left it alone. + Ditto pyexpat.c. Fred or Martin will know what to do.
2002-07-07 00:59:34 -03:00
- Compiling out the cyclic garbage collector is no longer an option.
The old symbol WITH_CYCLE_GC is now ignored, and Python.h arranges
that it's always defined (for the benefit of any extension modules
that may be conditionalizing on it). A bonus is that any extension
type participating in cyclic gc can choose to participate in the
Py_TRASHCAN mechanism now too; in the absence of cyclic gc, this used
to require editing the core to teach the trashcan mechanism about the
new type.
Patch #573770: Implement lchown.
2002-07-28 13:33:45 -03:00
- According to Annex F of the current C standard,
Stop trying to cater to platforms with a broken HUGE_VAL definition. It breaks other platforms (in this case, the hack for broken Cray systems in turn caused failure on a Mac system broken in a different way).
2002-07-03 00:31:20 -03:00
The Standard C macro HUGE_VAL and its float and long double analogs,
HUGE_VALF and HUGE_VALL, expand to expressions whose values are
positive infinities.
Python only uses the double HUGE_VAL, and only to #define its own symbol
Py_HUGE_VAL. Some platforms have incorrect definitions for HUGE_VAL.
pyport.h used to try to worm around that, but the workarounds triggered
other bugs on other platforms, so we gave up. If your platform defines
HUGE_VAL incorrectly, you'll need to #define Py_HUGE_VAL to something
that works on your platform. The only instance of this I'm sure about
is on an unknown subset of Cray systems, described here:
http://www.cray.com/swpubs/manuals/SN-2194_2.0/html-SN-2194_2.0/x3138.htm
Presumably 2.3a1 breaks such systems. If anyone uses such a system, help!
Patch #505375: Make doc strings optional.
2002-06-09 10:33:54 -03:00
- The configure option --without-doc-strings can be used to remove the
doc strings from the builtin functions and modules; this reduces the
size of the executable.
Add notes about universal newlines.
2002-08-15 11:01:14 -03:00
- The universal newlines option (PEP 278) is on by default. On Unix
it can be disabled by passing --without-universal-newlines to the
configure script. On other platforms, remove
WITH_UNIVERSAL_NEWLINES from pyconfig.h.
Enable universal newlines on Windows. Note that NEWS needs more words!
2002-04-21 04:30:30 -03:00
Patch #527027: Allow building python as shared library.
2002-03-29 12:28:31 -04:00
- On Unix, a shared libpython2.3.so can be created with --enable-shared.
Eliminate DONT_SHARE_SHORT_STRINGS.
2002-03-30 06:06:07 -04:00
- All uses of the CACHE_HASH, INTERN_STRINGS, and DONT_SHARE_SHORT_STRINGS
preprocessor symbols were eliminated. The internal decisions they
controlled stopped being experimental long ago.
Remove the CACHE_HASH and INTERN_STRINGS preprocessor symbols.
2002-03-28 23:29:08 -04:00
Added note about using the documentation build tools under Cygwin.
2002-05-02 18:17:00 -03:00
- The tools used to build the documentation now work under Cygwin as
well as Unix.
This introduces stricter library/header file checking for the Berkeley DB library. Since multiple versions can be installed simultaneously, it's crucial that you only select libraries and header files which are compatible with each other. Version checking is done from highest version to lowest. Building using version 1 of Berkeley DB is disabled by default because of the hash file bugs people keep rediscovering. It can be enabled by uncommenting a few lines in setup.py. Closes patch 553108.
2002-06-14 17:30:31 -03:00
- The bsddb and dbm module builds have been changed to try and avoid version
skew problems and disable linkage with Berkeley DB 1.85 unless the
installer knows what s/he's doing. See the section on building these
modules in the README file for details.
Added 2.3a1 section.
2001-12-21 17:36:50 -04:00
C API
ReST-ification of the NEWS file. While the total number of changes are fairly large, most are caused by reformatting section and subsection headings. The changes fall into the following categories: * reformatted section and subsection headers. * escaped isolated asterisks which would be interpreted as starting bold or italic text (e.g. "void (*)(PyObject \*)"). * quoted stuff that looks like internal references but isn't (e.g. ``PyCmp_``). * changed visually balanced quotes to just use apostrophes (e.g. "'string'" instead of "`string'"). * introduced and indenting multiline chunks of code. * created one table (search for "New codecs").
2002-09-20 11:16:59 -03:00
-----
Added 2.3a1 section.
2001-12-21 17:36:50 -04:00
Note that PyNumber_Check() returns true for string and unicode objects.
2002-11-18 12:19:39 -04:00
- PyNumber_Check() now returns true for string and unicode objects.
This is a result of these types having a partially defined
Comment on PyNumber_Check().
2002-11-18 12:27:16 -04:00
tp_as_number slot. (This is not a feature, but an indication that
Fix typo.
2002-11-19 17:20:25 -04:00
PyNumber_Check() is not very useful to determine numeric behavior.
Comment on PyNumber_Check().
2002-11-18 12:27:16 -04:00
It may be deprecated.)
Note that PyNumber_Check() returns true for string and unicode objects.
2002-11-18 12:19:39 -04:00
SF patch 576101, by Oren Tirosh: alternative implementation of interning. I modified Oren's patch significantly, but the basic idea and most of the implementation is unchanged. Interned strings created with PyString_InternInPlace() are now mortal, and you must keep a reference to the resulting string around; use the new function PyString_InternImmortal() to create immortal interned strings.
2002-08-19 18:43:18 -03:00
- The string object's layout has changed: the pointer member
ob_sinterned has been replaced by an int member ob_sstate. On some
platforms (e.g. most 64-bit systems) this may change the offset of
the ob_sval member, so as a precaution the API_VERSION has been
incremented. The apparently unused feature of "indirect interned
strings", supported by the ob_sinterned member, is gone. Interned
Fix spelling.
2003-03-11 17:43:55 -04:00
strings are now usually mortal; there is a new API,
SF patch 576101, by Oren Tirosh: alternative implementation of interning. I modified Oren's patch significantly, but the basic idea and most of the implementation is unchanged. Interned strings created with PyString_InternInPlace() are now mortal, and you must keep a reference to the resulting string around; use the new function PyString_InternImmortal() to create immortal interned strings.
2002-08-19 18:43:18 -03:00
PyString_InternImmortal() that creates immortal interned strings.
(The ob_sstate member can only take three values; however, while
making it a char saves a few bytes per string object on average, in
it also slowed things down a bit because ob_sval was no longer
aligned.)
Add news about Fred's change to Py_InitModule4().
2002-08-14 18:20:32 -03:00
- The Py_InitModule*() functions now accept NULL for the 'methods'
argument. Modules without global functions are becoming more common
now that factories can be types rather than functions.
Add C API PyUnicode_FromOrdinal() which exposes unichr() at C level. u'%c' will now raise a ValueError in case the argument is an integer outside the valid range of Unicode code point ordinals. Closes SF bug #593581.
2002-08-11 09:23:04 -03:00
- New C API PyUnicode_FromOrdinal() which exposes unichr() at C
level.
New functions for extension writers on Windows: PyErr_SetExcFromWindowsErr(), PyErr_SetExcFromWindowsErrWithFilename(). Similar to PyErr_SetFromWindowsErrWithFilename() and PyErr_SetFromWindowsErr(), but they allow to specify the exception type to raise. Available on Windows. See SF patch #576458.
2002-07-29 11:27:41 -03:00
- New functions PyErr_SetExcFromWindowsErr() and
PyErr_SetExcFromWindowsErrWithFilename(). Similar to
PyErr_SetFromWindowsErrWithFilename() and
PyErr_SetFromWindowsErr(), but they allow to specify
the exception type to raise. Available on Windows.
The Py_REF_DEBUG/COUNT_ALLOCS/Py_TRACE_REFS macro minefield: added more trivial lexical helper macros so that uses of these guys expand to nothing at all when they're not enabled. This should help sub- standard compilers that can't do a good job of optimizing away the previous "(void)0" expressions. Py_DECREF: There's only one definition of this now. Yay! That was that last one in the family defined multiple times in an #ifdef maze. Py_FatalError(): Changed the char* signature to const char*. _Py_NegativeRefcount(): New helper function for the Py_REF_DEBUG expansion of Py_DECREF. Calling an external function cuts down on the volume of generated code. The previous inline expansion of abort() didn't work as intended on Windows (the program often kept going, and the error msg scrolled off the screen unseen). _Py_NegativeRefcount calls Py_FatalError instead, which captures our best knowledge of how to abort effectively across platforms.
2002-07-08 23:57:01 -03:00
- Py_FatalError() is now declared as taking a const char* argument. It
was previously declared without const. This should not affect working
code.
Patch #552433: Special-case tuples. Avoid sub-type checking for lists. Avoid checks for negative indices and duplicate checks for support of the sequence protocol.
2002-05-08 05:44:21 -03:00
- Added new macro PySequence_ITEM(o, i) that directly calls
sq_item without rechecking that o is a sequence and without
adjusting for negative indices.
Added notes related to the removal of deprecated features of the xrange type.
2002-05-02 18:28:26 -03:00
- PyRange_New() now raises ValueError if the fourth argument is not 1.
This is part of the removal of deprecated features of the xrange
object.
PyNumber_CoerceEx: this took a shortcut (not doing anything) when the left and right type were of the same type and not classic instances. This shortcut is dangerous for proxy types, because it means that coerce(Proxy(1), Proxy(2.1)) leaves Proxy(1) unchanged rather than turning it into Proxy(1.0). In an ever-so-slight change of semantics, I now only take the shortcut when the left and right types are of the same type and don't have the CHECKTYPES feature. It so happens that classic instances have this flag, so the shortcut is still skipped in this case (i.e. nothing changes for classic instances). Proxies also have this flag set (otherwise implementing numeric operations on proxies would become nightmarish) and this means that the shortcut is also skipped there, as desired. It so happens that int, long and float also have this flag set; that means that e.g. coerce(1, 1) will now invoke int_coerce(). This is fine: int_coerce() can deal with this, and I'm not worried about the performance; int_coerce() is only invoked when the user explicitly calls coerce(), which should be rarer than rare.
2002-04-25 23:49:14 -03:00
- PyNumber_Coerce() and PyNumber_CoerceEx() now also invoke the type's
coercion if both arguments have the same type but this type has the
CHECKTYPES flag set. This is to better support proxies.
fix a couple nits with my use of ReST
2002-09-30 12:23:01 -03:00
- The type of tp_free has been changed from "``void (*)(PyObject *)``" to
"``void (*)(void *)``".
Add news about memory managent APIs changing.
2002-04-12 20:00:08 -03:00
- PyObject_Del, PyObject_GC_Del are now functions instead of macros.
- A type can now inherit its metatype from its base type. Previously, when PyType_Ready() was called, if ob_type was found to be NULL, it was always set to &PyType_Type; now it is set to base->ob_type, where base is tp_base, defaulting to &PyObject_Type. - PyType_Ready() accidentally did not inherit tp_is_gc; now it does. Bugfix candidate.
2002-04-07 22:38:42 -03:00
- A type can now inherit its metatype from its base type. Previously,
when PyType_Ready() was called, if ob_type was found to be NULL, it
was always set to &PyType_Type; now it is set to base->ob_type,
where base is tp_base, defaulting to &PyObject_Type.
- PyType_Ready() accidentally did not inherit tp_is_gc; now it does.
Remove news about PyMalloc_*. Do we need to say anything about pymalloc?
2002-05-08 11:14:41 -03:00
- The PyCore_* family of APIs have been removed.
Add news about pymalloc being enabled.
2002-03-22 13:06:59 -04:00
Fix typos
2002-05-07 17:58:03 -03:00
- The "u#" parser marker will now pass through Unicode objects as-is
Fixed "u#" parser marker to pass through Unicode objects as-is without going through the buffer interface API. Added tests for this to the _testcapi module and updated docs.
2002-01-09 12:21:27 -04:00
without going through the buffer API.
ReST-ification of the NEWS file. While the total number of changes are fairly large, most are caused by reformatting section and subsection headings. The changes fall into the following categories: * reformatted section and subsection headers. * escaped isolated asterisks which would be interpreted as starting bold or italic text (e.g. "void (*)(PyObject \*)"). * quoted stuff that looks like internal references but isn't (e.g. ``PyCmp_``). * changed visually balanced quotes to just use apostrophes (e.g. "'string'" instead of "`string'"). * introduced and indenting multiline chunks of code. * created one table (search for "New codecs").
2002-09-20 11:16:59 -03:00
- The enumerators of cmp_op have been renamed to use the prefix ``PyCmp_``.
Patch #494783: Rename cmp_op enumerators.
2002-01-01 15:59:11 -04:00
SF bug #495548: troublesome #define in pyport.h Removed the ancient "#define ANY void". Bugfix candidate? Hard call. The bug report claims the existence of this #define creates conflicts with other packages, which is easy to believe. OTOH, some extension authors may still be relying on its presence. I'm afraid you can't win on this one.
2001-12-25 15:07:38 -04:00
- An old #define of ANY as void has been removed from pyport.h. This
hasn't been used since Python's pre-ANSI days, and the #define has
been marked as obsolete since then. SF bug 495548 says it created
conflicts with other packages, so keeping it around wasn't harmless.
Added 2.3a1 section.
2001-12-21 17:36:50 -04:00
- Because Python's magic number scheme broke on January 1st, we decided
to stop Python development. Thanks for all the fish!
file_truncate(): provide full "large file" support on Windows, by dropping MS's inadequate _chsize() function. This was inspired by SF patch 498109 ("fileobject truncate support for win32"), which I rejected. libstdtypes.tex: Someone who knows should update the availability blurb. For example, if it's available on Linux, it would be good to say so. test_largefile: Uncommented the file.truncate() tests, and reworked to do more. The old comment about "permission errors" in the truncation tests under Windows was almost certainly due to that the file wasn't open for *write* access at this point, so of course MS wouldn't let you truncate it. I'd be appalled if a Unixish system did. CAUTION: Someone should run this test on Linux (etc) too. The truncation part was commented out before. Note that test_largefile isn't run by default.
2002-03-10 20:24:00 -04:00
- Some of us don't like fish, so we changed Python's magic number
Add news about PYC magic and changes to UTF-8 codec.
2002-02-09 07:28:43 -04:00
scheme to a new one. See Python/import.c for details.
Added 2.3a1 section.
2001-12-21 17:36:50 -04:00
New platforms
ReST-ification of the NEWS file. While the total number of changes are fairly large, most are caused by reformatting section and subsection headings. The changes fall into the following categories: * reformatted section and subsection headers. * escaped isolated asterisks which would be interpreted as starting bold or italic text (e.g. "void (*)(PyObject \*)"). * quoted stuff that looks like internal references but isn't (e.g. ``PyCmp_``). * changed visually balanced quotes to just use apostrophes (e.g. "'string'" instead of "`string'"). * introduced and indenting multiline chunks of code. * created one table (search for "New codecs").
2002-09-20 11:16:59 -03:00
-------------
Added 2.3a1 section.
2001-12-21 17:36:50 -04:00
Patch #614055: Support OpenVMS.
2002-12-06 08:48:53 -04:00
- OpenVMS is now supported.
Patch #488073: AtheOS port.
2002-06-11 03:22:31 -03:00
- AtheOS is now supported.
OS/2 EMX now supported
2002-08-04 04:25:58 -03:00
- the EMX runtime environment on OS/2 is now supported.
Patch #497098: build support for GNU/Hurd.
2002-01-01 14:41:33 -04:00
- GNU/Hurd is now supported.
Added 2.3a1 section.
2001-12-21 17:36:50 -04:00
Tests
ReST-ification of the NEWS file. While the total number of changes are fairly large, most are caused by reformatting section and subsection headings. The changes fall into the following categories: * reformatted section and subsection headers. * escaped isolated asterisks which would be interpreted as starting bold or italic text (e.g. "void (*)(PyObject \*)"). * quoted stuff that looks like internal references but isn't (e.g. ``PyCmp_``). * changed visually balanced quotes to just use apostrophes (e.g. "'string'" instead of "`string'"). * introduced and indenting multiline chunks of code. * created one table (search for "New codecs").
2002-09-20 11:16:59 -03:00
-----
Add a way to say "use any resource except A". For example, to run allow the use of any resource except bsddb, give the option "-uall,-bsddb".
2002-11-26 17:44:56 -04:00
- The regrtest.py script's -u option now provides a way to say "allow
all resources except this one." For example, to allow everything
except bsddb, give the option '-uall,-bsddb'.
Added 2.3a1 section.
2001-12-21 17:36:50 -04:00
Windows
ReST-ification of the NEWS file. While the total number of changes are fairly large, most are caused by reformatting section and subsection headings. The changes fall into the following categories: * reformatted section and subsection headers. * escaped isolated asterisks which would be interpreted as starting bold or italic text (e.g. "void (*)(PyObject \*)"). * quoted stuff that looks like internal references but isn't (e.g. ``PyCmp_``). * changed visually balanced quotes to just use apostrophes (e.g. "'string'" instead of "`string'"). * introduced and indenting multiline chunks of code. * created one table (search for "New codecs").
2002-09-20 11:16:59 -03:00
-------
Added 2.3a1 section.
2001-12-21 17:36:50 -04:00
More bsddb-on-Windows fiddling: + News blurb, but as much XXX as news. + Updated installer (install the new bsddb package, and the Berkeley DLL; still don't know how to fold that into _bsddb.pyd). + Fleshed out build instructions. + Debug Python still blows up.
2002-11-22 23:49:08 -04:00
- The Windows distribution now ships with version 4.0.14 of the
Sleepycat Berkeley database library. This should be a huge
improvement over the previous Berkeley DB 1.85, which had many
bugs.
XXX What are the licensing issues here?
Fix spelling.
2003-03-11 17:43:55 -04:00
XXX If a user has a database created with a previous version of
Try linking the static Sleepycat lib into _bsddb.pyd. Hard to say whether this is a correct thing to do: + There are linker warnings (see PCbuild\readme.txt). + test_bsddb passes, in both release and debug builds now. + test_bsddb3 has several failures, but it did before too. Also made pythoncore a dependency of the _bsddb project, updated build instructions, added database conversion XXX to NEWS, and fiddled the Windows installer accordingly.
2002-11-23 14:48:06 -04:00
XXX Python, what must they do to convert it?
XXX I'm still not sure how to link this thing (see PCbuild/readme.txt).
More bsddb-on-Windows fiddling: + News blurb, but as much XXX as news. + Updated installer (install the new bsddb package, and the Berkeley DLL; still don't know how to fold that into _bsddb.pyd). + Fleshed out build instructions. + Debug Python still blows up.
2002-11-22 23:49:08 -04:00
XXX The version # is likely to change before 2.3a1.
Blurb about new datetime module.
2002-12-16 16:57:22 -04:00
- The Windows distribution now ships with a Secure Sockets Library (SLL)
_ssl.pyd added for Windows.
2002-12-03 02:16:08 -04:00
module (_ssl.pyd)
More bsddb-on-Windows fiddling: + News blurb, but as much XXX as news. + Updated installer (install the new bsddb package, and the Berkeley DLL; still don't know how to fold that into _bsddb.pyd). + Fleshed out build instructions. + Debug Python still blows up.
2002-11-22 23:49:08 -04:00
Windows blurb about new Tcl/Tk release shipped on Windows.
2002-11-14 19:31:58 -04:00
- The Windows distribution now ships with Tcl/Tk version 8.4.1 (it
previously shipped with Tcl/Tk 8.3.2).
Added a blurb about the change to sys.version under MSVC.
2002-11-11 15:51:33 -04:00
- When Python is built under a Microsoft compiler, sys.version now
includes the compiler version number (_MSC_VER). For example, under
Fix spelling.
2003-03-11 17:43:55 -04:00
MSVC 6, sys.version contains the substring "MSC v.1200 ". 1200 is
Added a blurb about the change to sys.version under MSVC.
2002-11-11 15:51:33 -04:00
the value of _MSC_VER under MSVC 6.
Windows installer: disabled Wise's "delete in-use files" uninstall option. It was the cause of at least one way UNWISE.EXE could vanish (install a python; uninstall it; install it again; reboot the machine; abracadabra the uinstaller is gone). Bugfix candidate, but I'll backport it myself.
2002-04-16 17:48:01 -03:00
- Sometimes the uninstall executable (UNWISE.EXE) vanishes. One cause
of that has been fixed in the installer (disabled Wise's "delete in-
use files" uninstall option).
Some more news.
2002-04-05 20:23:25 -04:00
- Fixed a bug in urllib's proxy handling in Windows. [SF bug #503031]
SF bug 497854: Short-cuts missing for All Users Fix Windows-specific install glitch. Tested on Win2K, but I can't test on XP. Already checked in to the release22-maint branch.
2002-04-04 16:02:04 -04:00
- The installer now installs Start menu shortcuts under (the local
equivalent of) "All Users" when doing an Admin install.
file_truncate(): provide full "large file" support on Windows, by dropping MS's inadequate _chsize() function. This was inspired by SF patch 498109 ("fileobject truncate support for win32"), which I rejected. libstdtypes.tex: Someone who knows should update the availability blurb. For example, if it's available on Linux, it would be good to say so. test_largefile: Uncommented the file.truncate() tests, and reworked to do more. The old comment about "permission errors" in the truncation tests under Windows was almost certainly due to that the file wasn't open for *write* access at this point, so of course MS wouldn't let you truncate it. I'd be appalled if a Unixish system did. CAUTION: Someone should run this test on Linux (etc) too. The truncation part was commented out before. Note that test_largefile isn't run by default.
2002-03-10 20:24:00 -04:00
- file.truncate([newsize]) now works on Windows for all newsize values.
It used to fail if newsize didn't fit in 32 bits, reflecting a
limitation of MS _chsize (which is no longer used).
Implement os.waitpid() for Windows, in a way that's compatible with Linux where their capabilities intersect. Would be nice if people using non- MSVC compilers (Borland etc) took a whack at doing something similar for them (this code relies on the MS _cwait function).
2002-02-01 07:27:43 -04:00
- os.waitpid() is now implemented for Windows, and can be used to block
until a specified process exits. This is similar to, but not exactly
the same as, os.waitpid() on POSIX systems. If you're waiting for
a specific process whose pid was obtained from one of the spawn()
functions, the same Python os.waitpid() code works across platforms.
SF bug 497854: Short-cuts missing for All Users Fix Windows-specific install glitch. Tested on Win2K, but I can't test on XP. Already checked in to the release22-maint branch.
2002-04-04 16:02:04 -04:00
See the docs for details. The docs were changed to clarify that
spawn functions return, and waitpid requires, a process handle on
Windows (not the same thing as a Windows process id).
Implement os.waitpid() for Windows, in a way that's compatible with Linux where their capabilities intersect. Would be nice if people using non- MSVC compilers (Borland etc) took a whack at doing something similar for them (this code relies on the MS _cwait function).
2002-02-01 07:27:43 -04:00
New tempfile and os.open() gimmicks for Windows.
2002-01-31 20:52:29 -04:00
- New tempfile.TemporaryFile implementation for Windows: this doesn't
Fix typos
2002-05-07 17:58:03 -03:00
need a TemporaryFileWrapper wrapper anymore, and should be immune
New tempfile and os.open() gimmicks for Windows.
2002-01-31 20:52:29 -04:00
to a nasty problem: before 2.3, if you got a temp file on Windows, it
got wrapped in an object whose close() method first closed the
underlying file, then deleted the file. This usually worked fine.
However, the spawn family of functions on Windows create (at a low C
level) the same set of open files in the spawned process Q as were
open in the spawning process P. If a temp file f was among them, then
doing f.close() in P first closed P's C-level file handle on f, but Q's
C-level file handle on f remained open, so the attempt in P to delete f
blew up with a "Permission denied" error (Windows doesn't allow
deleting open files). This was surprising, subtle, and difficult to
work around.
- The os module now exports all the symbolic constants usable with the
low-level os.open() on Windows: the new constants in 2.3 are
O_NOINHERIT, O_SHORT_LIVED, O_TEMPORARY, O_RANDOM and O_SEQUENTIAL.
The others were also available in 2.2: O_APPEND, O_BINARY, O_CREAT,
O_EXCL, O_RDONLY, O_RDWR, O_TEXT, O_TRUNC and O_WRONLY. Contrary
to Microsoft docs, O_SHORT_LIVED does not seem to imply O_TEMPORARY
(so specify both if you want both; note that neither is useful unless
specified with O_CREAT too).
Added 2.3a1 section.
2001-12-21 17:36:50 -04:00
Mac
ReST-ification of the NEWS file. While the total number of changes are fairly large, most are caused by reformatting section and subsection headings. The changes fall into the following categories: * reformatted section and subsection headers. * escaped isolated asterisks which would be interpreted as starting bold or italic text (e.g. "void (*)(PyObject \*)"). * quoted stuff that looks like internal references but isn't (e.g. ``PyCmp_``). * changed visually balanced quotes to just use apostrophes (e.g. "'string'" instead of "`string'"). * introduced and indenting multiline chunks of code. * created one table (search for "New codecs").
2002-09-20 11:16:59 -03:00
----
Got rid of Mac/Relnotes, and started on mac-specific release notes in NEWS.
2002-12-23 07:25:49 -04:00
- Mac/Relnotes is gone, the release notes are now here.
mention unicode file name support on OSX
2003-02-10 06:06:18 -04:00
- Python (the OSX-only, unix-based version, not the OS9-compatible CFM
version) now fully supports unicode strings as arguments to various file
system calls, eg. open(), file(), os.stat() and os.listdir().
Got rid of Mac/Relnotes, and started on mac-specific release notes in NEWS.
2002-12-23 07:25:49 -04:00
- The current naming convention for Python on the Macintosh is that MacPython
refers to the unix-based OSX-only version, and MacPython-OS9 refers to the
CFM-based version that runs on both OS9 and OSX.
- All MacPython-OS9 functionality is now available in an OSX unix build,
including the Carbon modules, the IDE, OSA support, etc. A lot of this
will only work correctly in a framework build, though, because you cannot
talk to the window manager unless your application is run from a .app
bundle. There is a command line tool "pythonw" that runs your script
with an interpreter living in such a .app bundle, this interpreter should
be used to run any Python script using the window manager (including
Tkinter or wxPython scripts).
SF bug 660795: logging missing from Python 2.3a1 for Windows. Added the logging package. In the meantime, Neal Norwitz added a test_logging.py to the std test suite, which would have caught this oversight in the Windows installer.
2003-01-02 12:02:27 -04:00
Added a note about the move of Mac/Lib to Lib/plat-mac.
2002-12-30 18:42:43 -04:00
- Most of Mac/Lib has moved to Lib/plat-mac, which is again used both in
MacPython-OSX and MacPython-OS9. The only modules remaining in Mac/Lib
are specifically for MacPython-OS9 (CFM support, preference resources, etc).
Add newsitem for the two new unittest methods. Also, made some whitespace cleanup.
2002-12-29 16:14:11 -04:00
Got rid of Mac/Relnotes, and started on mac-specific release notes in NEWS.
2002-12-23 07:25:49 -04:00
- A new utility PythonLauncher will start a Python interpreter when a .py or
.pyw script is double-clicked in the Finder. By default .py scripts are
run with a normal Python interpreter in a Terminal window and .pyw
files are run with a window-aware pythonw interpreter without a Terminal
window, but all this can be customized.
Add newsitem for the two new unittest methods. Also, made some whitespace cleanup.
2002-12-29 16:14:11 -04:00
Got rid of Mac/Relnotes, and started on mac-specific release notes in NEWS.
2002-12-23 07:25:49 -04:00
- MacPython-OS9 is now Carbon-only, so it runs on Mac OS 9 or Mac OS X and
possibly on Mac OS 8.6 with the right CarbonLib installed, but not on earlier
releases.
Add newsitem for the two new unittest methods. Also, made some whitespace cleanup.
2002-12-29 16:14:11 -04:00
Got rid of Mac/Relnotes, and started on mac-specific release notes in NEWS.
2002-12-23 07:25:49 -04:00
- Many tools such as BuildApplet.py and gensuitemodule.py now support a command
line interface too.
Add newsitem for the two new unittest methods. Also, made some whitespace cleanup.
2002-12-29 16:14:11 -04:00
Got rid of Mac/Relnotes, and started on mac-specific release notes in NEWS.
2002-12-23 07:25:49 -04:00
- All the Carbon classes are now PEP253 compliant, meaning that you can
subclass them from Python. Most of the attributes have gone, you should
now use the accessor function call API, which is also what Apple's
documentation uses. Some attributes such as grafport.visRgn are still
available for convenience.
Add newsitem for the two new unittest methods. Also, made some whitespace cleanup.
2002-12-29 16:14:11 -04:00
Got rid of Mac/Relnotes, and started on mac-specific release notes in NEWS.
2002-12-23 07:25:49 -04:00
- New Carbon modules File (implementing the APIs in Files.h and Aliases.h)
and Folder (APIs from Folders.h). The old macfs builtin module is
gone, and replaced by a Python wrapper around the new modules.
- Pathname handling should now be fully consistent: MacPython-OSX always uses
unix pathnames and MacPython-OS9 always uses colon-separated Mac pathnames
(also when running on Mac OS X).
Add newsitem for the two new unittest methods. Also, made some whitespace cleanup.
2002-12-29 16:14:11 -04:00
Got rid of Mac/Relnotes, and started on mac-specific release notes in NEWS.
2002-12-23 07:25:49 -04:00
- New Carbon modules Help and AH give access to the Carbon Help Manager.
There are hooks in the IDE to allow accessing the Python documentation
(and Apple's Carbon and Cocoa documentation) through the Help Viewer.
See Mac/OSX/README for converting the Python documentation to a
Fix spelling.
2003-03-11 17:43:55 -04:00
Help Viewer compatible form and installing it.
Add newsitem for the two new unittest methods. Also, made some whitespace cleanup.
2002-12-29 16:14:11 -04:00
Got rid of Mac/Relnotes, and started on mac-specific release notes in NEWS.
2002-12-23 07:25:49 -04:00
- OSA support has been redesigned and the generated Python classes now
mirror the inheritance defined by the underlying OSA classes.
Add newsitem for the two new unittest methods. Also, made some whitespace cleanup.
2002-12-29 16:14:11 -04:00
Got rid of Mac/Relnotes, and started on mac-specific release notes in NEWS.
2002-12-23 07:25:49 -04:00
- MacPython no longer maps both \r and \n to \n on input for any text file.
This feature has been replaced by universal newline support (PEP278).
Utterly minimal changes to collapse datetimetz into datetime, and timetz into time. This is little more than *exporting* the datetimetz object under the name "datetime", and similarly for timetz. A good implementation of this change requires more work, but this is fully functional if you don't stare too hard at the internals (e.g., right now a type named "datetime" shows up as a base class of the type named "datetime"). The docs also need extensive revision, not part of this checkin.
2003-01-08 16:40:01 -04:00
Made "ascii" the default encoding for MacPython, as suggested by MvL, and ripped out my previous changes to test_unicode. Doing this for 2.3a1 should give people enough time to complain, if they want to, and then we can see whether we want to do anything about it.
2003-01-08 12:29:17 -04:00
- The default encoding for Python sourcefiles in MacPython-OS9 is no longer
Match parentheses.
2003-02-19 21:52:48 -04:00
mac-roman (or whatever your local Mac encoding was) but "ascii", like on
Made "ascii" the default encoding for MacPython, as suggested by MvL, and ripped out my previous changes to test_unicode. Doing this for 2.3a1 should give people enough time to complain, if they want to, and then we can see whether we want to do anything about it.
2003-01-08 12:29:17 -04:00
other platforms. If you really need sourcefiles with Mac characters in them
you can change this in site.py.
Added 2.3a1 section.
2001-12-21 17:36:50 -04:00
Prepped for 2.3b1. Added an extra blank line before "What's New in Python 2.2 final?".
2003-02-19 21:56:17 -04:00
Post-release fiddling -- prep for 2.2 final.
2001-12-14 19:16:18 -04:00
What's New in Python 2.2 final?
===============================
ReST-ification of the NEWS file. While the total number of changes are fairly large, most are caused by reformatting section and subsection headings. The changes fall into the following categories: * reformatted section and subsection headers. * escaped isolated asterisks which would be interpreted as starting bold or italic text (e.g. "void (*)(PyObject \*)"). * quoted stuff that looks like internal references but isn't (e.g. ``PyCmp_``). * changed visually balanced quotes to just use apostrophes (e.g. "'string'" instead of "`string'"). * introduced and indenting multiline chunks of code. * created one table (search for "New codecs").
2002-09-20 11:16:59 -03:00
*Release date: 21-Dec-2001*
Post-release fiddling -- prep for 2.2 final.
2001-12-14 19:16:18 -04:00
Type/class unification and new-style classes
ReST-ification of the NEWS file. While the total number of changes are fairly large, most are caused by reformatting section and subsection headings. The changes fall into the following categories: * reformatted section and subsection headers. * escaped isolated asterisks which would be interpreted as starting bold or italic text (e.g. "void (*)(PyObject \*)"). * quoted stuff that looks like internal references but isn't (e.g. ``PyCmp_``). * changed visually balanced quotes to just use apostrophes (e.g. "'string'" instead of "`string'"). * introduced and indenting multiline chunks of code. * created one table (search for "New codecs").
2002-09-20 11:16:59 -03:00
--------------------------------------------
Post-release fiddling -- prep for 2.2 final.
2001-12-14 19:16:18 -04:00
Merge of the release22 branch changes back into the trunk.
2001-12-21 16:04:22 -04:00
- pickle.py, cPickle: allow pickling instances of new-style classes
with a custom metaclass.
Post-release fiddling -- prep for 2.2 final.
2001-12-14 19:16:18 -04:00
Core and builtins
ReST-ification of the NEWS file. While the total number of changes are fairly large, most are caused by reformatting section and subsection headings. The changes fall into the following categories: * reformatted section and subsection headers. * escaped isolated asterisks which would be interpreted as starting bold or italic text (e.g. "void (*)(PyObject \*)"). * quoted stuff that looks like internal references but isn't (e.g. ``PyCmp_``). * changed visually balanced quotes to just use apostrophes (e.g. "'string'" instead of "`string'"). * introduced and indenting multiline chunks of code. * created one table (search for "New codecs").
2002-09-20 11:16:59 -03:00
-----------------
Post-release fiddling -- prep for 2.2 final.
2001-12-14 19:16:18 -04:00
Merge of the release22 branch changes back into the trunk.
2001-12-21 16:04:22 -04:00
- weakref proxy object: when comparing, unwrap both arguments if both
are proxies.
Post-release fiddling -- prep for 2.2 final.
2001-12-14 19:16:18 -04:00
Extension modules
ReST-ification of the NEWS file. While the total number of changes are fairly large, most are caused by reformatting section and subsection headings. The changes fall into the following categories: * reformatted section and subsection headers. * escaped isolated asterisks which would be interpreted as starting bold or italic text (e.g. "void (*)(PyObject \*)"). * quoted stuff that looks like internal references but isn't (e.g. ``PyCmp_``). * changed visually balanced quotes to just use apostrophes (e.g. "'string'" instead of "`string'"). * introduced and indenting multiline chunks of code. * created one table (search for "New codecs").
2002-09-20 11:16:59 -03:00
-----------------
Post-release fiddling -- prep for 2.2 final.
2001-12-14 19:16:18 -04:00
Merge of the release22 branch changes back into the trunk.
2001-12-21 16:04:22 -04:00
- binascii.b2a_base64(): fix a potential buffer overrun when encoding
very short strings.
- cPickle: the obscure "fast" mode was suspected of causing stack
overflows on the Mac. Hopefully fixed this by setting the recursion
limit much smaller. If the limit is too low (it only affects
performance), you can change it by defining PY_CPICKLE_FAST_LIMIT
when compiling cPickle.c (or in pyconfig.h).
Post-release fiddling -- prep for 2.2 final.
2001-12-14 19:16:18 -04:00
Library
ReST-ification of the NEWS file. While the total number of changes are fairly large, most are caused by reformatting section and subsection headings. The changes fall into the following categories: * reformatted section and subsection headers. * escaped isolated asterisks which would be interpreted as starting bold or italic text (e.g. "void (*)(PyObject \*)"). * quoted stuff that looks like internal references but isn't (e.g. ``PyCmp_``). * changed visually balanced quotes to just use apostrophes (e.g. "'string'" instead of "`string'"). * introduced and indenting multiline chunks of code. * created one table (search for "New codecs").
2002-09-20 11:16:59 -03:00
-------
Post-release fiddling -- prep for 2.2 final.
2001-12-14 19:16:18 -04:00
Merge of the release22 branch changes back into the trunk.
2001-12-21 16:04:22 -04:00
- dumbdbm.py: fixed a dumb old bug (the file didn't get synched at
close or delete time).
- rfc822.py: fixed a bug where the address '<>' was converted to None
instead of an empty string (also fixes the email.Utils module).
- xmlrpclib.py: version 1.0.0; uses precision for doubles.
- test suite: the pickle and cPickle tests were not executing any code
Fix typos
2002-05-07 17:58:03 -03:00
when run from the standard regression test.
Merge of the release22 branch changes back into the trunk.
2001-12-21 16:04:22 -04:00
Post-release fiddling -- prep for 2.2 final.
2001-12-14 19:16:18 -04:00
Tools/Demos
ReST-ification of the NEWS file. While the total number of changes are fairly large, most are caused by reformatting section and subsection headings. The changes fall into the following categories: * reformatted section and subsection headers. * escaped isolated asterisks which would be interpreted as starting bold or italic text (e.g. "void (*)(PyObject \*)"). * quoted stuff that looks like internal references but isn't (e.g. ``PyCmp_``). * changed visually balanced quotes to just use apostrophes (e.g. "'string'" instead of "`string'"). * introduced and indenting multiline chunks of code. * created one table (search for "New codecs").
2002-09-20 11:16:59 -03:00
-----------
Post-release fiddling -- prep for 2.2 final.
2001-12-14 19:16:18 -04:00
Build
ReST-ification of the NEWS file. While the total number of changes are fairly large, most are caused by reformatting section and subsection headings. The changes fall into the following categories: * reformatted section and subsection headers. * escaped isolated asterisks which would be interpreted as starting bold or italic text (e.g. "void (*)(PyObject \*)"). * quoted stuff that looks like internal references but isn't (e.g. ``PyCmp_``). * changed visually balanced quotes to just use apostrophes (e.g. "'string'" instead of "`string'"). * introduced and indenting multiline chunks of code. * created one table (search for "New codecs").
2002-09-20 11:16:59 -03:00
-----
Post-release fiddling -- prep for 2.2 final.
2001-12-14 19:16:18 -04:00
C API
ReST-ification of the NEWS file. While the total number of changes are fairly large, most are caused by reformatting section and subsection headings. The changes fall into the following categories: * reformatted section and subsection headers. * escaped isolated asterisks which would be interpreted as starting bold or italic text (e.g. "void (*)(PyObject \*)"). * quoted stuff that looks like internal references but isn't (e.g. ``PyCmp_``). * changed visually balanced quotes to just use apostrophes (e.g. "'string'" instead of "`string'"). * introduced and indenting multiline chunks of code. * created one table (search for "New codecs").
2002-09-20 11:16:59 -03:00
-----
Post-release fiddling -- prep for 2.2 final.
2001-12-14 19:16:18 -04:00
New platforms
ReST-ification of the NEWS file. While the total number of changes are fairly large, most are caused by reformatting section and subsection headings. The changes fall into the following categories: * reformatted section and subsection headers. * escaped isolated asterisks which would be interpreted as starting bold or italic text (e.g. "void (*)(PyObject \*)"). * quoted stuff that looks like internal references but isn't (e.g. ``PyCmp_``). * changed visually balanced quotes to just use apostrophes (e.g. "'string'" instead of "`string'"). * introduced and indenting multiline chunks of code. * created one table (search for "New codecs").
2002-09-20 11:16:59 -03:00
-------------
Post-release fiddling -- prep for 2.2 final.
2001-12-14 19:16:18 -04:00
Tests
ReST-ification of the NEWS file. While the total number of changes are fairly large, most are caused by reformatting section and subsection headings. The changes fall into the following categories: * reformatted section and subsection headers. * escaped isolated asterisks which would be interpreted as starting bold or italic text (e.g. "void (*)(PyObject \*)"). * quoted stuff that looks like internal references but isn't (e.g. ``PyCmp_``). * changed visually balanced quotes to just use apostrophes (e.g. "'string'" instead of "`string'"). * introduced and indenting multiline chunks of code. * created one table (search for "New codecs").
2002-09-20 11:16:59 -03:00
-----
Post-release fiddling -- prep for 2.2 final.
2001-12-14 19:16:18 -04:00
Windows
ReST-ification of the NEWS file. While the total number of changes are fairly large, most are caused by reformatting section and subsection headings. The changes fall into the following categories: * reformatted section and subsection headers. * escaped isolated asterisks which would be interpreted as starting bold or italic text (e.g. "void (*)(PyObject \*)"). * quoted stuff that looks like internal references but isn't (e.g. ``PyCmp_``). * changed visually balanced quotes to just use apostrophes (e.g. "'string'" instead of "`string'"). * introduced and indenting multiline chunks of code. * created one table (search for "New codecs").
2002-09-20 11:16:59 -03:00
-------
Post-release fiddling -- prep for 2.2 final.
2001-12-14 19:16:18 -04:00
Merge of the release22 branch changes back into the trunk.
2001-12-21 16:04:22 -04:00
- distutils package: fixed broken Windows installers (bdist_wininst).
- tempfile.py: prevent mysterious warnings when TemporaryFileWrapper
instances are deleted at process exit time.
- socket.py: prevent mysterious warnings when socket instances are
deleted at process exit time.
- posixmodule.c: fix a Windows crash with stat() of a filename ending
in backslash.
Post-release fiddling -- prep for 2.2 final.
2001-12-14 19:16:18 -04:00
Mac
ReST-ification of the NEWS file. While the total number of changes are fairly large, most are caused by reformatting section and subsection headings. The changes fall into the following categories: * reformatted section and subsection headers. * escaped isolated asterisks which would be interpreted as starting bold or italic text (e.g. "void (*)(PyObject \*)"). * quoted stuff that looks like internal references but isn't (e.g. ``PyCmp_``). * changed visually balanced quotes to just use apostrophes (e.g. "'string'" instead of "`string'"). * introduced and indenting multiline chunks of code. * created one table (search for "New codecs").
2002-09-20 11:16:59 -03:00
----
Post-release fiddling -- prep for 2.2 final.
2001-12-14 19:16:18 -04:00
Merge of the release22 branch changes back into the trunk.
2001-12-21 16:04:22 -04:00
- The Carbon toolbox modules have been upgraded to Universal Headers
3.4, and experimental CoreGraphics and CarbonEvents modules have
been added. All only for framework-enabled MacOSX.
Post-release fiddling -- prep for 2.2 final.
2001-12-14 19:16:18 -04:00
Update Windows buildno for 2.2c1. Update 2.2c1 release data in NEWS.
2001-12-13 15:34:00 -04:00
What's New in Python 2.2c1?
Add skeleton for 2.2c1 news.
2001-11-16 20:21:57 -04:00
===========================
ReST-ification of the NEWS file. While the total number of changes are fairly large, most are caused by reformatting section and subsection headings. The changes fall into the following categories: * reformatted section and subsection headers. * escaped isolated asterisks which would be interpreted as starting bold or italic text (e.g. "void (*)(PyObject \*)"). * quoted stuff that looks like internal references but isn't (e.g. ``PyCmp_``). * changed visually balanced quotes to just use apostrophes (e.g. "'string'" instead of "`string'"). * introduced and indenting multiline chunks of code. * created one table (search for "New codecs").
2002-09-20 11:16:59 -03:00
*Release date: 14-Dec-2001*
Add skeleton for 2.2c1 news.
2001-11-16 20:21:57 -04:00
Type/class unification and new-style classes
ReST-ification of the NEWS file. While the total number of changes are fairly large, most are caused by reformatting section and subsection headings. The changes fall into the following categories: * reformatted section and subsection headers. * escaped isolated asterisks which would be interpreted as starting bold or italic text (e.g. "void (*)(PyObject \*)"). * quoted stuff that looks like internal references but isn't (e.g. ``PyCmp_``). * changed visually balanced quotes to just use apostrophes (e.g. "'string'" instead of "`string'"). * introduced and indenting multiline chunks of code. * created one table (search for "New codecs").
2002-09-20 11:16:59 -03:00
--------------------------------------------
Add skeleton for 2.2c1 news.
2001-11-16 20:21:57 -04:00
Merge last minute 2.2c1 changes from branch to trunk.
2001-12-14 16:47:12 -04:00
- Guido's tutorial introduction to the new type/class features has
been extensively updated. See
http://www.python.org/2.2/descrintro.html
That remains the primary documentation in this area.
Fix SF bug #489581: __slots__ leak. It was easier than I thought, assuming that no other things contribute to the instance size besides slots -- a pretty good bet. With a test suite, no less!
2001-12-05 18:45:48 -04:00
- Fixed a leak: instance variables declared with __slots__ were never
deleted!
Fix for SF bug #485678. slot_tp_descr_set(): When deleting an attribute described by a descriptor implemented in Python, the descriptor's __del__ method is called by the slot_tp_descr_set dispatch function. This is bogus -- __del__ already has a different meaning. Renaming this use of __del__ is renamed to __delete__.
2001-12-02 20:54:52 -04:00
- The "delete attribute" method of descriptor objects is called
__delete__, not __del__. In previous releases, it was mistakenly
called __del__, which created an unfortunate overloading condition
with finalizers. (The "get attribute" and "set attribute" methods
are still called __get__ and __set__, respectively.)
New about super.
2001-12-03 11:46:59 -04:00
- Some subtle issues with the super built-in were fixed:
(a) When super itself is subclassed, its __get__ method would still
return an instance of the base class (i.e., of super).
(b) super(C, C()).__class__ would return C rather than super. This
is confusing. To fix this, I decided to change the semantics of
super so that it only applies to code attributes, not to data
attributes. After all, overriding data attributes is not
supported anyway.
(c) The __get__ method didn't check whether the argument was an
instance of the type used in creation of the super instance.
Add note about fixed hash() of mutable objects.
2001-12-04 17:02:07 -04:00
- Previously, hash() of an instance of a subclass of a mutable type
(list or dictionary) would return some value, rather than raising
TypeError. This has been fixed. Also, directly calling
dict.__hash__ and list.__hash__ now raises the same TypeError
(previously, these were the same as object.__hash__).
New about super.
2001-12-03 11:46:59 -04:00
At the PythonLabs meeting someone mentioned it would make Jim really happy if one could delete the __dict__ attribute of an instance. I love to make Jim happy, so here goes... - New-style objects now support deleting their __dict__. This is for all intents and purposes equivalent to assigning a brand new empty dictionary, but saves space if the object is not used further.
2001-12-05 15:46:42 -04:00
- New-style objects now support deleting their __dict__. This is for
all intents and purposes equivalent to assigning a brand new empty
dictionary, but saves space if the object is not used further.
Add skeleton for 2.2c1 news.
2001-11-16 20:21:57 -04:00
Core and builtins
ReST-ification of the NEWS file. While the total number of changes are fairly large, most are caused by reformatting section and subsection headings. The changes fall into the following categories: * reformatted section and subsection headers. * escaped isolated asterisks which would be interpreted as starting bold or italic text (e.g. "void (*)(PyObject \*)"). * quoted stuff that looks like internal references but isn't (e.g. ``PyCmp_``). * changed visually balanced quotes to just use apostrophes (e.g. "'string'" instead of "`string'"). * introduced and indenting multiline chunks of code. * created one table (search for "New codecs").
2002-09-20 11:16:59 -03:00
-----------------
Add skeleton for 2.2c1 news.
2001-11-16 20:21:57 -04:00
SF bug #488514: -Qnew needs work Big Hammer to implement -Qnew as PEP 238 says it should work (a global option affecting all instances of "/"). pydebug.h, main.c, pythonrun.c: define a private _Py_QnewFlag flag, true iff -Qnew is passed on the command line. This should go away (as the comments say) when true division becomes The Rule. This is deliberately not exposed to runtime inspection or modification: it's a one-way one-shot switch to pretend you're using Python 3. ceval.c: when _Py_QnewFlag is set, treat BINARY_DIVIDE as BINARY_TRUE_DIVIDE. test_{descr, generators, zipfile}.py: fiddle so these pass under -Qnew too. This was just a matter of s!/!//! in test_generators and test_zipfile. test_descr was trickier, as testbinop() is passed assumptions that "/" is the same as calling a "__div__" method; put a temporary hack there to call "__truediv__" instead when the method name is "__div__" and 1/2 evaluates to 0.5. Three standard tests still fail under -Qnew (on Windows; somebody please try the Linux tests with -Qnew too! Linux runs a whole bunch of tests Windows doesn't): test_augassign test_class test_coercion I can't stay awake longer to stare at this (be my guest). Offhand cures weren't obvious, nor was it even obvious that cures are possible without major hackery. Question: when -Qnew is in effect, should calls to __div__ magically change into calls to __truediv__? See "major hackery" at tail end of last paragraph <wink>.
2001-12-06 02:23:26 -04:00
- -Qnew now works as documented in PEP 238: when -Qnew is passed on
the command line, all occurrences of "/" use true division instead
of classic division. See the PEP for details. Note that "all"
means all instances in library and 3rd-party modules, as well as in
your own code. As the PEP says, -Qnew is intended for use only in
educational environments with control over the libraries in use.
Added -Qnew news about the test_coercion.py failure. That's the only test that still fails under -Qnew, and is so tied to details of current behavior that fixing it before new division becomes the default is impractical.
2001-12-11 17:43:14 -04:00
Note that test_coercion.py in the standard Python test suite fails
under -Qnew; this is expected, and won't be repaired until true
division becomes the default (in the meantime, test_coercion is
testing the current rules).
SF bug #488514: -Qnew needs work Big Hammer to implement -Qnew as PEP 238 says it should work (a global option affecting all instances of "/"). pydebug.h, main.c, pythonrun.c: define a private _Py_QnewFlag flag, true iff -Qnew is passed on the command line. This should go away (as the comments say) when true division becomes The Rule. This is deliberately not exposed to runtime inspection or modification: it's a one-way one-shot switch to pretend you're using Python 3. ceval.c: when _Py_QnewFlag is set, treat BINARY_DIVIDE as BINARY_TRUE_DIVIDE. test_{descr, generators, zipfile}.py: fiddle so these pass under -Qnew too. This was just a matter of s!/!//! in test_generators and test_zipfile. test_descr was trickier, as testbinop() is passed assumptions that "/" is the same as calling a "__div__" method; put a temporary hack there to call "__truediv__" instead when the method name is "__div__" and 1/2 evaluates to 0.5. Three standard tests still fail under -Qnew (on Windows; somebody please try the Linux tests with -Qnew too! Linux runs a whole bunch of tests Windows doesn't): test_augassign test_class test_coercion I can't stay awake longer to stare at this (be my guest). Offhand cures weren't obvious, nor was it even obvious that cures are possible without major hackery. Question: when -Qnew is in effect, should calls to __div__ magically change into calls to __truediv__? See "major hackery" at tail end of last paragraph <wink>.
2001-12-06 02:23:26 -04:00
Note the tighter complex() parameter checking.
2001-12-14 13:08:12 -04:00
- complex() now only allows the first argument to be a string
argument, and raises TypeError if either the second arg is a string
or if the second arg is specified when the first is a string.
Add skeleton for 2.2c1 news.
2001-11-16 20:21:57 -04:00
Extension modules
ReST-ification of the NEWS file. While the total number of changes are fairly large, most are caused by reformatting section and subsection headings. The changes fall into the following categories: * reformatted section and subsection headers. * escaped isolated asterisks which would be interpreted as starting bold or italic text (e.g. "void (*)(PyObject \*)"). * quoted stuff that looks like internal references but isn't (e.g. ``PyCmp_``). * changed visually balanced quotes to just use apostrophes (e.g. "'string'" instead of "`string'"). * introduced and indenting multiline chunks of code. * created one table (search for "New codecs").
2002-09-20 11:16:59 -03:00
-----------------
Add skeleton for 2.2c1 news.
2001-11-16 20:21:57 -04:00
Rename get_referents to get_referrers. Fixes #483815.
2001-11-24 05:24:51 -04:00
- gc.get_referents was renamed to gc.get_referrers.
Add skeleton for 2.2c1 news.
2001-11-16 20:21:57 -04:00
Library
ReST-ification of the NEWS file. While the total number of changes are fairly large, most are caused by reformatting section and subsection headings. The changes fall into the following categories: * reformatted section and subsection headers. * escaped isolated asterisks which would be interpreted as starting bold or italic text (e.g. "void (*)(PyObject \*)"). * quoted stuff that looks like internal references but isn't (e.g. ``PyCmp_``). * changed visually balanced quotes to just use apostrophes (e.g. "'string'" instead of "`string'"). * introduced and indenting multiline chunks of code. * created one table (search for "New codecs").
2002-09-20 11:16:59 -03:00
-------
Add skeleton for 2.2c1 news.
2001-11-16 20:21:57 -04:00
SF patch #489173: Make os.spawnv not block the interpreter, from Anthony Roach. Release the global interpreter lock around platform spawn calls. Bugfix candidate? Hard to say; I favor "yes, bugfix". These clearly *should* have been releasing the GIL all along, if for no other reason than compatibility with the similar os.system(). But it's possible some program out there is (a) multithreaded, (b) calling a spawn function with P_WAIT, and (c) relying on the spawn call to block all their threads until the spawned program completes. I think it's very unlikely anyone is doing that on purpose, but someone may be doing so by accident.
2001-12-07 16:35:43 -04:00
- Functions in the os.spawn() family now release the global interpreter
lock around calling the platform spawn. They should always have done
this, but did not before 2.2c1. Multithreaded programs calling
an os.spawn function with P_WAIT will no longer block all Python threads
until the spawned program completes. It's possible that some programs
relies on blocking, although more likely by accident than by design.
Patch #484847: Default to netscape.exe on OS/2.
2001-11-25 10:35:58 -04:00
- webbrowser defaults to netscape.exe on OS/2 now.
Properly set static options for tixBalloon and tixResizeHandle. Expose Tix.ResizeHandle.{detach_widget,hide,show}. Update Tix demos.
2001-11-25 10:50:56 -04:00
- Tix.ResizeHandle exposes detach_widget, hide, and show.
Patch #487275: windows-1251 charset alias.
2001-12-02 08:26:03 -04:00
- The charset alias windows_1252 has been added.
Merge last minute 2.2c1 changes from branch to trunk.
2001-12-14 16:47:12 -04:00
- types.StringTypes is a tuple containing the defined string types;
usually this will be (str, unicode), but if Python was compiled
without Unicode support it will be just (str,).
- The pulldom and minidom modules were synchronized to PyXML.
Add skeleton for 2.2c1 news.
2001-11-16 20:21:57 -04:00
Tools/Demos
ReST-ification of the NEWS file. While the total number of changes are fairly large, most are caused by reformatting section and subsection headings. The changes fall into the following categories: * reformatted section and subsection headers. * escaped isolated asterisks which would be interpreted as starting bold or italic text (e.g. "void (*)(PyObject \*)"). * quoted stuff that looks like internal references but isn't (e.g. ``PyCmp_``). * changed visually balanced quotes to just use apostrophes (e.g. "'string'" instead of "`string'"). * introduced and indenting multiline chunks of code. * created one table (search for "New codecs").
2002-09-20 11:16:59 -03:00
-----------
Add skeleton for 2.2c1 news.
2001-11-16 20:21:57 -04:00
Merge last minute 2.2c1 changes from branch to trunk.
2001-12-14 16:47:12 -04:00
- A new script called Tools/scripts/google.py was added, which fires
off a search on Google.
Add skeleton for 2.2c1 news.
2001-11-16 20:21:57 -04:00
Build
ReST-ification of the NEWS file. While the total number of changes are fairly large, most are caused by reformatting section and subsection headings. The changes fall into the following categories: * reformatted section and subsection headers. * escaped isolated asterisks which would be interpreted as starting bold or italic text (e.g. "void (*)(PyObject \*)"). * quoted stuff that looks like internal references but isn't (e.g. ``PyCmp_``). * changed visually balanced quotes to just use apostrophes (e.g. "'string'" instead of "`string'"). * introduced and indenting multiline chunks of code. * created one table (search for "New codecs").
2002-09-20 11:16:59 -03:00
-----
Add skeleton for 2.2c1 news.
2001-11-16 20:21:57 -04:00
Merge last minute 2.2c1 changes from branch to trunk.
2001-12-14 16:47:12 -04:00
- Note that release builds of Python should arrange to define the
preprocessor symbol NDEBUG on the command line (or equivalent).
In the 2.2 pre-release series we tried to define this by magic in
Python.h instead, but it proved to cause problems for extension
authors. The Unix, Windows and Mac builds now all define NDEBUG in
release builds via cmdline (or equivalent) instead. Ports to
other platforms should do likewise.
Test wether we are building on a case-insensitive filesystem (such as OSX HFS+) and if so add an extension to the python executable, but only in the build directory, not on the installed python.
2001-12-06 17:47:20 -04:00
- It is no longer necessary to use --with-suffix when building on a
case-insensitive file system (such as Mac OS X HFS+). In the build
directory an extension is used, but not in the installed python.
Add skeleton for 2.2c1 news.
2001-11-16 20:21:57 -04:00
C API
ReST-ification of the NEWS file. While the total number of changes are fairly large, most are caused by reformatting section and subsection headings. The changes fall into the following categories: * reformatted section and subsection headers. * escaped isolated asterisks which would be interpreted as starting bold or italic text (e.g. "void (*)(PyObject \*)"). * quoted stuff that looks like internal references but isn't (e.g. ``PyCmp_``). * changed visually balanced quotes to just use apostrophes (e.g. "'string'" instead of "`string'"). * introduced and indenting multiline chunks of code. * created one table (search for "New codecs").
2002-09-20 11:16:59 -03:00
-----
Add skeleton for 2.2c1 news.
2001-11-16 20:21:57 -04:00
SF bug #491415 PyDict_UpdateFromSeq2() unused PyDict_UpdateFromSeq2(): removed it. PyDict_MergeFromSeq2(): made it public and documented it. PyDict_Merge() docs: updated to reveal <wink> that the second argument can be any mapping object.
2001-12-11 14:51:08 -04:00
- New function PyDict_MergeFromSeq2() exposes the builtin dict
constructor's logic for updating a dictionary from an iterable object
producing key-value pairs.
SF bug 486278 SystemError: Python/getargs.c:1086: bad. vgetargskeywords(): Now that this routine is checking for bad input (rather than dump core in some cases), some bad calls are raising errors that previously "worked". This patch makes the error strings more revealing, and changes the exceptions from SystemError to RuntimeError (under the theory that SystemError is more of a "can't happen!" assert- like thing, and so inappropriate for bad arguments to a public C API function).
2001-11-28 23:26:37 -04:00
- PyArg_ParseTupleAndKeywords() requires that the number of entries in
SF bug #491415 PyDict_UpdateFromSeq2() unused PyDict_UpdateFromSeq2(): removed it. PyDict_MergeFromSeq2(): made it public and documented it. PyDict_Merge() docs: updated to reveal <wink> that the second argument can be any mapping object.
2001-12-11 14:51:08 -04:00
the keyword list equal the number of argument specifiers. This
SF bug 486278 SystemError: Python/getargs.c:1086: bad. vgetargskeywords(): Now that this routine is checking for bad input (rather than dump core in some cases), some bad calls are raising errors that previously "worked". This patch makes the error strings more revealing, and changes the exceptions from SystemError to RuntimeError (under the theory that SystemError is more of a "can't happen!" assert- like thing, and so inappropriate for bad arguments to a public C API function).
2001-11-28 23:26:37 -04:00
wasn't checked correctly, and PyArg_ParseTupleAndKeywords could even
dump core in some bad cases. This has been repaired. As a result,
PyArg_ParseTupleAndKeywords may raise RuntimeError in bad cases that
previously went unchallenged.
Add skeleton for 2.2c1 news.
2001-11-16 20:21:57 -04:00
New platforms
ReST-ification of the NEWS file. While the total number of changes are fairly large, most are caused by reformatting section and subsection headings. The changes fall into the following categories: * reformatted section and subsection headers. * escaped isolated asterisks which would be interpreted as starting bold or italic text (e.g. "void (*)(PyObject \*)"). * quoted stuff that looks like internal references but isn't (e.g. ``PyCmp_``). * changed visually balanced quotes to just use apostrophes (e.g. "'string'" instead of "`string'"). * introduced and indenting multiline chunks of code. * created one table (search for "New codecs").
2002-09-20 11:16:59 -03:00
-------------
Add skeleton for 2.2c1 news.
2001-11-16 20:21:57 -04:00
Tests
ReST-ification of the NEWS file. While the total number of changes are fairly large, most are caused by reformatting section and subsection headings. The changes fall into the following categories: * reformatted section and subsection headers. * escaped isolated asterisks which would be interpreted as starting bold or italic text (e.g. "void (*)(PyObject \*)"). * quoted stuff that looks like internal references but isn't (e.g. ``PyCmp_``). * changed visually balanced quotes to just use apostrophes (e.g. "'string'" instead of "`string'"). * introduced and indenting multiline chunks of code. * created one table (search for "New codecs").
2002-09-20 11:16:59 -03:00
-----
Add skeleton for 2.2c1 news.
2001-11-16 20:21:57 -04:00
Windows
ReST-ification of the NEWS file. While the total number of changes are fairly large, most are caused by reformatting section and subsection headings. The changes fall into the following categories: * reformatted section and subsection headers. * escaped isolated asterisks which would be interpreted as starting bold or italic text (e.g. "void (*)(PyObject \*)"). * quoted stuff that looks like internal references but isn't (e.g. ``PyCmp_``). * changed visually balanced quotes to just use apostrophes (e.g. "'string'" instead of "`string'"). * introduced and indenting multiline chunks of code. * created one table (search for "New codecs").
2002-09-20 11:16:59 -03:00
-------
Add skeleton for 2.2c1 news.
2001-11-16 20:21:57 -04:00
Mac
ReST-ification of the NEWS file. While the total number of changes are fairly large, most are caused by reformatting section and subsection headings. The changes fall into the following categories: * reformatted section and subsection headers. * escaped isolated asterisks which would be interpreted as starting bold or italic text (e.g. "void (*)(PyObject \*)"). * quoted stuff that looks like internal references but isn't (e.g. ``PyCmp_``). * changed visually balanced quotes to just use apostrophes (e.g. "'string'" instead of "`string'"). * introduced and indenting multiline chunks of code. * created one table (search for "New codecs").
2002-09-20 11:16:59 -03:00
----
Add skeleton for 2.2c1 news.
2001-11-16 20:21:57 -04:00
sys.platform is now "darwin" without digits appended.
2001-12-06 17:14:00 -04:00
- In unix-Python on Mac OS X (and darwin) sys.platform is now "darwin",
without any trailing digits.
Add skeleton for 2.2c1 news.
2001-11-16 20:21:57 -04:00
Merge last minute 2.2c1 changes from branch to trunk.
2001-12-14 16:47:12 -04:00
- Changed logic for finding python home in Mac OS X framework Pythons.
Now sys.executable points to the executable again, in stead of to
the shared library. The latter is used only for locating the python
home.
The usual post-release fiddling.
2001-10-19 14:55:30 -03:00
What's New in Python 2.2b2?
===========================
ReST-ification of the NEWS file. While the total number of changes are fairly large, most are caused by reformatting section and subsection headings. The changes fall into the following categories: * reformatted section and subsection headers. * escaped isolated asterisks which would be interpreted as starting bold or italic text (e.g. "void (*)(PyObject \*)"). * quoted stuff that looks like internal references but isn't (e.g. ``PyCmp_``). * changed visually balanced quotes to just use apostrophes (e.g. "'string'" instead of "`string'"). * introduced and indenting multiline chunks of code. * created one table (search for "New codecs").
2002-09-20 11:16:59 -03:00
*Release date: 16-Nov-2001*
The usual post-release fiddling.
2001-10-19 14:55:30 -03:00
Type/class unification and new-style classes
ReST-ification of the NEWS file. While the total number of changes are fairly large, most are caused by reformatting section and subsection headings. The changes fall into the following categories: * reformatted section and subsection headers. * escaped isolated asterisks which would be interpreted as starting bold or italic text (e.g. "void (*)(PyObject \*)"). * quoted stuff that looks like internal references but isn't (e.g. ``PyCmp_``). * changed visually balanced quotes to just use apostrophes (e.g. "'string'" instead of "`string'"). * introduced and indenting multiline chunks of code. * created one table (search for "New codecs").
2002-09-20 11:16:59 -03:00
--------------------------------------------
The usual post-release fiddling.
2001-10-19 14:55:30 -03:00
Correct the description of mixed multiple inheritance: the code special-cases classic classes, it doesn't do anything about other cases where different metaclasses are involved (except for the trivial case where one metaclass is a subclass of the others). Also note that it's metaclass, not metatype.
2001-11-15 16:27:54 -04:00
- Multiple inheritance mixing new-style and classic classes in the
list of base classes is now allowed, so this works now:
News about mixing classic and new-style classes in MI.
2001-11-15 16:02:21 -04:00
class Classic: pass
Correct the description of mixed multiple inheritance: the code special-cases classic classes, it doesn't do anything about other cases where different metaclasses are involved (except for the trivial case where one metaclass is a subclass of the others). Also note that it's metaclass, not metatype.
2001-11-15 16:27:54 -04:00
class Mixed(Classic, object): pass
News about mixing classic and new-style classes in MI.
2001-11-15 16:02:21 -04:00
The MRO (method resolution order) for each base class is respected
according to its kind, but the MRO for the derived class is computed
Fix typos
2002-05-07 17:58:03 -03:00
using new-style MRO rules if any base class is a new-style class.
News about mixing classic and new-style classes in MI.
2001-11-15 16:02:21 -04:00
This needs to be documented.
Rename "dictionary" (type and constructor) to "dict".
2001-10-29 18:25:45 -04:00
- The new builtin dictionary() constructor, and dictionary type, have
been renamed to dict. This reflects a decade of common usage.
Group dict[ionary] news together; and use dict() instead of dictionary().
2001-11-15 16:33:10 -04:00
- dict() now accepts an iterable object producing 2-sequences. For
example, dict(d.items()) == d for any dictionary d. The argument,
and the elements of the argument, can be any iterable objects.
Add __del__ callbacks. They are too useful to leave out. XXX Remaining problems: - The GC module doesn't know about these; I think it has its reasons to disallow calling __del__, but for now, __del__ on new-style objects is called when the GC module discards an object, for better or for worse. - The code to call a __del__ handler is really ridiculously complicated, due to all the different debug #ifdefs. I've copied this from the similar code in classobject.c, so I'm pretty sure I did it right, but it's not pretty. :-( - No tests yet.
2001-10-29 18:11:00 -04:00
- New-style classes can now have a __del__ method, which is called
when the instance is deleted (just like for classic classes).
Some news.
2001-10-26 11:56:06 -03:00
- Assignment to object.__dict__ is now possible, for objects that are
instances of new-style classes that have a __dict__ (unless the base
class forbids it).
Methods of built-in types now properly check for keyword arguments (formerly these were silently ignored). The only built-in methods that take keyword arguments are __call__, __init__ and __new__.
2001-10-21 21:43:43 -03:00
- Methods of built-in types now properly check for keyword arguments
(formerly these were silently ignored). The only built-in methods
that take keyword arguments are __call__, __init__ and __new__.
News about the socket type and the HP-UX port.
2001-10-27 19:28:54 -03:00
- The socket function has been converted to a type; see below.
The usual post-release fiddling.
2001-10-19 14:55:30 -03:00
Core and builtins
ReST-ification of the NEWS file. While the total number of changes are fairly large, most are caused by reformatting section and subsection headings. The changes fall into the following categories: * reformatted section and subsection headers. * escaped isolated asterisks which would be interpreted as starting bold or italic text (e.g. "void (*)(PyObject \*)"). * quoted stuff that looks like internal references but isn't (e.g. ``PyCmp_``). * changed visually balanced quotes to just use apostrophes (e.g. "'string'" instead of "`string'"). * introduced and indenting multiline chunks of code. * created one table (search for "New codecs").
2002-09-20 11:16:59 -03:00
-----------------
The usual post-release fiddling.
2001-10-19 14:55:30 -03:00
Add note about assignment to __debug__ being an error.
2001-11-09 17:06:24 -04:00
- Assignment to __debug__ raises SyntaxError at compile-time. This
was promised when 2.1c1 was released as "What's New in Python 2.1c1"
Merged in NEWS changes from the r22b2 branch.
2001-11-16 12:17:27 -04:00
(see below) says.
Add note about assignment to __debug__ being an error.
2001-11-09 17:06:24 -04:00
Some news.
2001-10-26 11:56:06 -03:00
- Clarified the error messages for unsupported operands to an operator
(like 1 + '').
The usual post-release fiddling.
2001-10-19 14:55:30 -03:00
Extension modules
ReST-ification of the NEWS file. While the total number of changes are fairly large, most are caused by reformatting section and subsection headings. The changes fall into the following categories: * reformatted section and subsection headers. * escaped isolated asterisks which would be interpreted as starting bold or italic text (e.g. "void (*)(PyObject \*)"). * quoted stuff that looks like internal references but isn't (e.g. ``PyCmp_``). * changed visually balanced quotes to just use apostrophes (e.g. "'string'" instead of "`string'"). * introduced and indenting multiline chunks of code. * created one table (search for "New codecs").
2002-09-20 11:16:59 -03:00
-----------------
The usual post-release fiddling.
2001-10-19 14:55:30 -03:00
CVS patch #477161: New "access" keyword for mmap, from Jay T Miller. This gives mmap() on Windows the ability to create read-only, write- through and copy-on-write mmaps. A new keyword argument is introduced because the mmap() signatures diverged between Windows and Unix, so while they (now) both support this functionality, there wasn't a way to spell it in a common way without introducing a new spelling gimmick. The old spellings are still accepted, so there isn't a backward- compatibility issue here.
2001-11-13 19:11:19 -04:00
- mmap has a new keyword argument, "access", allowing a uniform way for
both Windows and Unix users to create read-only, write-through and
copy-on-write memory mappings. This was previously possible only on
Unix. A new keyword argument was required to support this in a
Fix typos
2002-05-07 17:58:03 -03:00
uniform way because the mmap() signatures had diverged across
CVS patch #477161: New "access" keyword for mmap, from Jay T Miller. This gives mmap() on Windows the ability to create read-only, write- through and copy-on-write mmaps. A new keyword argument is introduced because the mmap() signatures diverged between Windows and Unix, so while they (now) both support this functionality, there wasn't a way to spell it in a common way without introducing a new spelling gimmick. The old spellings are still accepted, so there isn't a backward- compatibility issue here.
2001-11-13 19:11:19 -04:00
platforms. Thanks to Jay T Miller for repairing this!
Finish SF patch 477059: __del__ on new classes vs. GC. Just doc and NEWS here, about the change in gc.garbage meaning.
2001-11-03 15:57:21 -04:00
- By default, the gc.garbage list now contains only those instances in
unreachable cycles that have __del__ methods; in 2.1 it contained all
instances in unreachable cycles. "Instances" here has been generalized
to include instances of both new-style and old-style classes.
Some news.
2001-10-26 11:56:06 -03:00
- The socket module defines a new method for socket objects,
sendall(). This is like send() but may make multiple calls to
News about the socket type and the HP-UX port.
2001-10-27 19:28:54 -03:00
send() until all data has been sent. Also, the socket function has
been converted to a subclassable type, like list and tuple (etc.)
before it; socket and SocketType are now the same thing.
Some news.
2001-10-26 11:56:06 -03:00
- Various bugfixes to the curses module. There is now a test suite
for the curses module (you have to run it manually).
Add curses-related news items
2001-10-22 13:37:10 -03:00
News and attribution for SF bug #473009.
2001-10-29 23:03:03 -04:00
- binascii.b2a_base64 no longer places an arbitrary restriction of 57
bytes on its input.
The usual post-release fiddling.
2001-10-19 14:55:30 -03:00
Library
ReST-ification of the NEWS file. While the total number of changes are fairly large, most are caused by reformatting section and subsection headings. The changes fall into the following categories: * reformatted section and subsection headers. * escaped isolated asterisks which would be interpreted as starting bold or italic text (e.g. "void (*)(PyObject \*)"). * quoted stuff that looks like internal references but isn't (e.g. ``PyCmp_``). * changed visually balanced quotes to just use apostrophes (e.g. "'string'" instead of "`string'"). * introduced and indenting multiline chunks of code. * created one table (search for "New codecs").
2002-09-20 11:16:59 -03:00
-------
The usual post-release fiddling.
2001-10-19 14:55:30 -03:00
CVS patch #477161: New "access" keyword for mmap, from Jay T Miller. This gives mmap() on Windows the ability to create read-only, write- through and copy-on-write mmaps. A new keyword argument is introduced because the mmap() signatures diverged between Windows and Unix, so while they (now) both support this functionality, there wasn't a way to spell it in a common way without introducing a new spelling gimmick. The old spellings are still accepted, so there isn't a backward- compatibility issue here.
2001-11-13 19:11:19 -04:00
- tkFileDialog exposes a Directory class and askdirectory
Patch #478654: Expose tk_chooseDirectory. Also delegate kw arguments through ** calls.
2001-11-07 18:38:08 -04:00
convenience function.
Improved error msg when a symbolic group name is redefined. Added docs and NEWS. Bugfix candidate? That's a dilemma for Anthony <wink>: /F did fix a longstanding bug here, but the fix can cause code to raise an exception that previously worked by accident.
2001-11-03 15:35:43 -04:00
- Symbolic group names in regular expressions must be unique. For
example, the regexp r'(?P<abc>)(?P<abc>)' is not allowed, because a
single name can't mean both "group 1" and "group 2" simultaneously.
Merged in NEWS changes from the r22b2 branch.
2001-11-16 12:17:27 -04:00
Python 2.2 detects this error at regexp compilation time;
previously, the error went undetected, and results were
unpredictable. Also in sre, the pattern.split(), pattern.sub(), and
pattern.subn() methods have been rewritten in C. Also, an
experimental function/method finditer() has been added, which works
like findall() but returns an iterator.
Improved error msg when a symbolic group name is redefined. Added docs and NEWS. Bugfix candidate? That's a dilemma for Anthony <wink>: /F did fix a longstanding bug here, but the fix can cause code to raise an exception that previously worked by accident.
2001-11-03 15:35:43 -04:00
Patch #471120: Improved doc strings and new wrappers.
2001-11-02 19:48:20 -04:00
- Tix exposes more commands through the classes DirSelectBox,
DirSelectDialog, ListNoteBook, Meter, CheckList, and the
methods tix_addbitmapdir, tix_cget, tix_configure, tix_filedialog,
tix_getbitmap, tix_getimage, tix_option_get, and tix_resetoptions.
Doc and NEWS changes due to Jeremy adding traceback objects to gc.
2001-10-22 22:59:54 -03:00
- Traceback objects are now scanned by cyclic garbage collection, so
cycles created by casual use of sys.exc_info() no longer cause
permanent memory leaks (provided garbage collection is enabled).
Note updated RISCOS port. Remove reference in the 2.1 release notes to os.extsep -- that variable actually didn't exist in that release!
2001-10-24 17:51:44 -03:00
- os.extsep -- a new variable needed by the RISCOS support. It is the
separator used by extensions, and is '.' on all platforms except
RISCOS, where it is '/'. There is no need to use this variable
unless you have a masochistic desire to port your code to RISCOS.
Merged in NEWS changes from the r22b2 branch.
2001-11-16 12:17:27 -04:00
- mimetypes.py has optional support for non-standard, but commonly
found types. guess_type() and guess_extension() now accept an
ReST-ification of the NEWS file. While the total number of changes are fairly large, most are caused by reformatting section and subsection headings. The changes fall into the following categories: * reformatted section and subsection headers. * escaped isolated asterisks which would be interpreted as starting bold or italic text (e.g. "void (*)(PyObject \*)"). * quoted stuff that looks like internal references but isn't (e.g. ``PyCmp_``). * changed visually balanced quotes to just use apostrophes (e.g. "'string'" instead of "`string'"). * introduced and indenting multiline chunks of code. * created one table (search for "New codecs").
2002-09-20 11:16:59 -03:00
optional 'strict' flag, defaulting to true, which controls whether
Merged in NEWS changes from the r22b2 branch.
2001-11-16 12:17:27 -04:00
recognize non-standard types or not. A few non-standard types we
know about have been added. Also, when run as a script, there are
new -l and -e options.
- statcache is now deprecated.
- email.Utils.formatdate() now produces the preferred RFC 2822 style
dates with numeric timezones (it used to produce obsolete dates
ReST-ification of the NEWS file. While the total number of changes are fairly large, most are caused by reformatting section and subsection headings. The changes fall into the following categories: * reformatted section and subsection headers. * escaped isolated asterisks which would be interpreted as starting bold or italic text (e.g. "void (*)(PyObject \*)"). * quoted stuff that looks like internal references but isn't (e.g. ``PyCmp_``). * changed visually balanced quotes to just use apostrophes (e.g. "'string'" instead of "`string'"). * introduced and indenting multiline chunks of code. * created one table (search for "New codecs").
2002-09-20 11:16:59 -03:00
hard coded to "GMT" timezone). An optional 'localtime' flag is
Merged in NEWS changes from the r22b2 branch.
2001-11-16 12:17:27 -04:00
added to produce dates in the local timezone, with daylight savings
time properly taken into account.
- In pickle and cPickle, instead of masking errors in load() by
transforming them into SystemError, we let the original exception
propagate out. Also, implement support for __safe_for_unpickling__
in pickle, as it already was supported in cPickle.
The usual post-release fiddling.
2001-10-19 14:55:30 -03:00
Tools/Demos
ReST-ification of the NEWS file. While the total number of changes are fairly large, most are caused by reformatting section and subsection headings. The changes fall into the following categories: * reformatted section and subsection headers. * escaped isolated asterisks which would be interpreted as starting bold or italic text (e.g. "void (*)(PyObject \*)"). * quoted stuff that looks like internal references but isn't (e.g. ``PyCmp_``). * changed visually balanced quotes to just use apostrophes (e.g. "'string'" instead of "`string'"). * introduced and indenting multiline chunks of code. * created one table (search for "New codecs").
2002-09-20 11:16:59 -03:00
-----------
The usual post-release fiddling.
2001-10-19 14:55:30 -03:00
Build
ReST-ification of the NEWS file. While the total number of changes are fairly large, most are caused by reformatting section and subsection headings. The changes fall into the following categories: * reformatted section and subsection headers. * escaped isolated asterisks which would be interpreted as starting bold or italic text (e.g. "void (*)(PyObject \*)"). * quoted stuff that looks like internal references but isn't (e.g. ``PyCmp_``). * changed visually balanced quotes to just use apostrophes (e.g. "'string'" instead of "`string'"). * introduced and indenting multiline chunks of code. * created one table (search for "New codecs").
2002-09-20 11:16:59 -03:00
-----
The usual post-release fiddling.
2001-10-19 14:55:30 -03:00
Merged in NEWS changes from the r22b2 branch.
2001-11-16 12:17:27 -04:00
- The dbm module is built using libdb1 if available. The bsddb module
is built with libdb3 if available.
- Misc/Makefile.pre.in has been removed by BDFL pronouncement.
The usual post-release fiddling.
2001-10-19 14:55:30 -03:00
C API
ReST-ification of the NEWS file. While the total number of changes are fairly large, most are caused by reformatting section and subsection headings. The changes fall into the following categories: * reformatted section and subsection headers. * escaped isolated asterisks which would be interpreted as starting bold or italic text (e.g. "void (*)(PyObject \*)"). * quoted stuff that looks like internal references but isn't (e.g. ``PyCmp_``). * changed visually balanced quotes to just use apostrophes (e.g. "'string'" instead of "`string'"). * introduced and indenting multiline chunks of code. * created one table (search for "New codecs").
2002-09-20 11:16:59 -03:00
-----
The usual post-release fiddling.
2001-10-19 14:55:30 -03:00
Generalize dictionary() to accept a sequence of 2-sequences. At the outer level, the iterator protocol is used for memory-efficiency (the outer sequence may be very large if fully materialized); at the inner level, PySequence_Fast() is used for time-efficiency (these should always be sequences of length 2). dictobject.c, new functions PyDict_{Merge,Update}FromSeq2. These are wholly analogous to PyDict_{Merge,Update}, but process a sequence-of-2- sequences argument instead of a mapping object. For now, I left these functions file static, so no corresponding doc changes. It's tempting to change dict.update() to allow a sequence-of-2-seqs argument too. Also changed the name of dictionary's keyword argument from "mapping" to "x". Got a better name? "mapping_or_sequence_of_pairs" isn't attractive, although more so than "mosop" <wink>. abstract.h, abstract.tex: Added new PySequence_Fast_GET_SIZE function, much faster than going thru the all-purpose PySequence_Size. libfuncs.tex: - Document dictionary(). - Fiddle tuple() and list() to admit that their argument is optional. - The long-winded repetitions of "a sequence, a container that supports iteration, or an iterator object" is getting to be a PITA. Many months ago I suggested factoring this out into "iterable object", where the definition of that could include being explicit about generators too (as is, I'm not sure a reader outside of PythonLabs could guess that "an iterator object" includes a generator call). - Please check my curly braces -- I'm going blind <0.9 wink>. abstract.c, PySequence_Tuple(): When PyObject_GetIter() fails, leave its error msg alone now (the msg it produces has improved since PySequence_Tuple was generalized to accept iterable objects, and PySequence_Tuple was also stomping on the msg in cases it shouldn't have even before PyObject_GetIter grew a better msg).
2001-10-26 02:06:50 -03:00
- New function PySequence_Fast_GET_SIZE() returns the size of a non-
NULL result from PySequence_Fast(), more quickly than calling
PySequence_Size().
Merged in NEWS changes from the r22b2 branch.
2001-11-16 12:17:27 -04:00
- New argument unpacking function PyArg_UnpackTuple() added.
- New functions PyObject_CallFunctionObjArgs() and
PyObject_CallMethodObjArgs() have been added to make it more
convenient and efficient to call functions and methods from C.
- PyArg_ParseTupleAndKeywords() no longer masks errors, so it's
possible that this will propagate errors it didn't before.
- New function PyObject_CheckReadBuffer(), which returns true if its
argument supports the single-segment readable buffer interface.
The usual post-release fiddling.
2001-10-19 14:55:30 -03:00
New platforms
ReST-ification of the NEWS file. While the total number of changes are fairly large, most are caused by reformatting section and subsection headings. The changes fall into the following categories: * reformatted section and subsection headers. * escaped isolated asterisks which would be interpreted as starting bold or italic text (e.g. "void (*)(PyObject \*)"). * quoted stuff that looks like internal references but isn't (e.g. ``PyCmp_``). * changed visually balanced quotes to just use apostrophes (e.g. "'string'" instead of "`string'"). * introduced and indenting multiline chunks of code. * created one table (search for "New codecs").
2002-09-20 11:16:59 -03:00
-------------
The usual post-release fiddling.
2001-10-19 14:55:30 -03:00
News about the socket type and the HP-UX port.
2001-10-27 19:28:54 -03:00
- We've finally confirmed that this release builds on HP-UX 11.00,
*with* threads, and passes the test suite.
News about OS/2 Visual Age C++ patches.
2001-11-04 22:51:07 -04:00
- Thanks to a series of patches from Michael Muller, Python may build
again under OS/2 Visual Age C++.
Note updated RISCOS port. Remove reference in the 2.1 release notes to os.extsep -- that variable actually didn't exist in that release!
2001-10-24 17:51:44 -03:00
- Updated RISCOS port by Dietmar Schwertberger.
The usual post-release fiddling.
2001-10-19 14:55:30 -03:00
Tests
ReST-ification of the NEWS file. While the total number of changes are fairly large, most are caused by reformatting section and subsection headings. The changes fall into the following categories: * reformatted section and subsection headers. * escaped isolated asterisks which would be interpreted as starting bold or italic text (e.g. "void (*)(PyObject \*)"). * quoted stuff that looks like internal references but isn't (e.g. ``PyCmp_``). * changed visually balanced quotes to just use apostrophes (e.g. "'string'" instead of "`string'"). * introduced and indenting multiline chunks of code. * created one table (search for "New codecs").
2002-09-20 11:16:59 -03:00
-----
The usual post-release fiddling.
2001-10-19 14:55:30 -03:00
Add curses-related news items
2001-10-22 13:37:10 -03:00
- Added a test script for the curses module. It isn't run automatically;
regrtest.py must be run with '-u curses' to enable it.
The usual post-release fiddling.
2001-10-19 14:55:30 -03:00
Windows
ReST-ification of the NEWS file. While the total number of changes are fairly large, most are caused by reformatting section and subsection headings. The changes fall into the following categories: * reformatted section and subsection headers. * escaped isolated asterisks which would be interpreted as starting bold or italic text (e.g. "void (*)(PyObject \*)"). * quoted stuff that looks like internal references but isn't (e.g. ``PyCmp_``). * changed visually balanced quotes to just use apostrophes (e.g. "'string'" instead of "`string'"). * introduced and indenting multiline chunks of code. * created one table (search for "New codecs").
2002-09-20 11:16:59 -03:00
-------
The usual post-release fiddling.
2001-10-19 14:55:30 -03:00
Merged in NEWS changes from the r22b2 branch.
2001-11-16 12:17:27 -04:00
Mac
ReST-ification of the NEWS file. While the total number of changes are fairly large, most are caused by reformatting section and subsection headings. The changes fall into the following categories: * reformatted section and subsection headers. * escaped isolated asterisks which would be interpreted as starting bold or italic text (e.g. "void (*)(PyObject \*)"). * quoted stuff that looks like internal references but isn't (e.g. ``PyCmp_``). * changed visually balanced quotes to just use apostrophes (e.g. "'string'" instead of "`string'"). * introduced and indenting multiline chunks of code. * created one table (search for "New codecs").
2002-09-20 11:16:59 -03:00
----
Merged in NEWS changes from the r22b2 branch.
2001-11-16 12:17:27 -04:00
- PythonScript has been moved to unsupported and is slated to be
removed completely in the next release.
- It should now be possible to build applets that work on both OS9 and
OSX.
- The core is now linked with CoreServices not Carbon; as a side
result, default 8bit encoding on OSX is now ASCII.
- Python should now build on OSX 10.1.1
The usual post-release fiddling.
2001-10-19 14:55:30 -03:00
Post-release fiddling (prep for 2.2b1).
2001-09-28 18:53:42 -03:00
What's New in Python 2.2b1?
===========================
ReST-ification of the NEWS file. While the total number of changes are fairly large, most are caused by reformatting section and subsection headings. The changes fall into the following categories: * reformatted section and subsection headers. * escaped isolated asterisks which would be interpreted as starting bold or italic text (e.g. "void (*)(PyObject \*)"). * quoted stuff that looks like internal references but isn't (e.g. ``PyCmp_``). * changed visually balanced quotes to just use apostrophes (e.g. "'string'" instead of "`string'"). * introduced and indenting multiline chunks of code. * created one table (search for "New codecs").
2002-09-20 11:16:59 -03:00
*Release date: 19-Oct-2001*
Post-release fiddling (prep for 2.2b1).
2001-09-28 18:53:42 -03:00
Type/class unification and new-style classes
ReST-ification of the NEWS file. While the total number of changes are fairly large, most are caused by reformatting section and subsection headings. The changes fall into the following categories: * reformatted section and subsection headers. * escaped isolated asterisks which would be interpreted as starting bold or italic text (e.g. "void (*)(PyObject \*)"). * quoted stuff that looks like internal references but isn't (e.g. ``PyCmp_``). * changed visually balanced quotes to just use apostrophes (e.g. "'string'" instead of "`string'"). * introduced and indenting multiline chunks of code. * created one table (search for "New codecs").
2002-09-20 11:16:59 -03:00
--------------------------------------------
Post-release fiddling (prep for 2.2b1).
2001-09-28 18:53:42 -03:00
Get rid of __defined__ and tp_defined -- there's no need to distinguish __dict__ and __defined__ any more. In the C structure, tp_cache takes its place -- but this hasn't been implemented yet.
2001-10-15 19:03:32 -03:00
- New-style classes are now always dynamic (except for built-in and
Reword the text on the demise of __dynamic__ somewhat, correcting a typo.
2001-10-15 21:46:57 -03:00
extension types). There is no longer a performance penalty, and I
Get rid of __defined__ and tp_defined -- there's no need to distinguish __dict__ and __defined__ any more. In the C structure, tp_cache takes its place -- but this hasn't been implemented yet.
2001-10-15 19:03:32 -03:00
no longer see another reason to keep this baggage around. One relic
Reword the text on the demise of __dynamic__ somewhat, correcting a typo.
2001-10-15 21:46:57 -03:00
remains: the __dict__ of a new-style class is a read-only proxy; you
must set the class's attribute to modify it. As a consequence, the
Get rid of __defined__ and tp_defined -- there's no need to distinguish __dict__ and __defined__ any more. In the C structure, tp_cache takes its place -- but this hasn't been implemented yet.
2001-10-15 19:03:32 -03:00
__defined__ attribute of new-style types no longer exists, for lack
of need: there is once again only one __dict__ (although in the
Reword the text on the demise of __dynamic__ somewhat, correcting a typo.
2001-10-15 21:46:57 -03:00
future a __cache__ may be resurrected with a similar function, if I
can prove that it actually speeds things up).
Make new classes dynamic by default.
2001-10-04 16:46:06 -03:00
Added a little type/class NEWS.
2001-10-04 03:43:12 -03:00
- C.__doc__ now works as expected for new-style classes (in 2.2a4 it
always returned None, even when there was a class docstring).
- doctest now finds and runs docstrings attached to new-style classes,
class methods, static methods, and properties.
Add fix for getattr(obj, name, default). Rearrange a few things.
2001-10-16 18:34:49 -03:00
Core and builtins
ReST-ification of the NEWS file. While the total number of changes are fairly large, most are caused by reformatting section and subsection headings. The changes fall into the following categories: * reformatted section and subsection headers. * escaped isolated asterisks which would be interpreted as starting bold or italic text (e.g. "void (*)(PyObject \*)"). * quoted stuff that looks like internal references but isn't (e.g. ``PyCmp_``). * changed visually balanced quotes to just use apostrophes (e.g. "'string'" instead of "`string'"). * introduced and indenting multiline chunks of code. * created one table (search for "New codecs").
2002-09-20 11:16:59 -03:00
-----------------
Post-release fiddling (prep for 2.2b1).
2001-09-28 18:53:42 -03:00
Note about fix in list comprehensions.
2001-10-15 12:53:58 -03:00
- A very subtle syntactical pitfall in list comprehensions was fixed.
For example: [a+b for a in 'abc', for b in 'def']. The comma in
this example is a mistake. Previously, this would silently let 'a'
iterate over the singleton tuple ('abc',), yielding ['abcd', 'abce',
'abcf'] rather than the intended ['ad', 'ae', 'af', 'bd', 'be',
'bf', 'cd', 'ce', 'cf']. Now, this is flagged as a syntax error.
Note that [a for a in <singleton>] is a convoluted way to say
[<singleton>] anyway, so it's not like any expressiveness is lost.
Add fix for getattr(obj, name, default). Rearrange a few things.
2001-10-16 18:34:49 -03:00
- getattr(obj, name, default) now only catches AttributeError, as
documented, rather than returning the default value for all
exceptions (which could mask bugs in a __getattr__ hook, for
example).
Added two very tardy notes about the 2.2b1 release, fixed a typo.
2001-10-22 15:41:51 -03:00
- Weak reference objects are now part of the core and offer a C API.
Add a note about changes related to the weak reference objects.
2001-10-18 15:18:06 -03:00
A bug which could allow a core dump when binary operations involved
Fix some typos
2001-10-21 22:47:26 -03:00
proxy reference has been fixed. weakref.ReferenceError is now a
Last minute updates for changes since 2.2a4. Unless Fred wants to add anything about the hotshot profiler, this file is ready for the 2.2b1 Windows build.
2001-10-19 02:35:40 -03:00
built-in exception.
Add a note about changes related to the weak reference objects.
2001-10-18 15:18:06 -03:00
Note the Unicode changes from SF patch #470578.
2001-10-18 23:05:35 -03:00
- unicode(obj) now behaves more like str(obj), accepting arbitrary
objects, and calling a __unicode__ method if it exists.
unicode(obj, encoding) and unicode(obj, encoding, errors) still
Additional test and documentation for the unicode() changes. This patch should also be applied to the 2.2b1 trunk.
2001-10-19 09:02:29 -03:00
require an 8-bit string or character buffer argument.
Note the Unicode changes from SF patch #470578.
2001-10-18 23:05:35 -03:00
Last minute updates for changes since 2.2a4. Unless Fred wants to add anything about the hotshot profiler, this file is ready for the 2.2b1 Windows build.
2001-10-19 02:35:40 -03:00
- isinstance() now allows any object as the first argument and a
class, a type or something with a __bases__ tuple attribute for the
second argument. The second argument may also be a tuple of a
class, type, or something with __bases__, in which case isinstance()
will return true if the first argument is an instance of any of the
things contained in the second argument tuple. E.g.
isinstance(x, (A, B))
returns true if x is an instance of A or B.
Add fix for getattr(obj, name, default). Rearrange a few things.
2001-10-16 18:34:49 -03:00
Extension modules
ReST-ification of the NEWS file. While the total number of changes are fairly large, most are caused by reformatting section and subsection headings. The changes fall into the following categories: * reformatted section and subsection headers. * escaped isolated asterisks which would be interpreted as starting bold or italic text (e.g. "void (*)(PyObject \*)"). * quoted stuff that looks like internal references but isn't (e.g. ``PyCmp_``). * changed visually balanced quotes to just use apostrophes (e.g. "'string'" instead of "`string'"). * introduced and indenting multiline chunks of code. * created one table (search for "New codecs").
2002-09-20 11:16:59 -03:00
-----------------
Add fix for getattr(obj, name, default). Rearrange a few things.
2001-10-16 18:34:49 -03:00
- thread.start_new_thread() now returns the thread ID (previously None).
Patch #462190, patch #464070: Support quoted printable in the binascii module. Decode and encode underscores for header style encoding. Fixes bug #463996.
2001-09-30 17:32:11 -03:00
- binascii has now two quopri support functions, a2b_qp and b2a_qp.
SF patch #460805 by Chris Gonnerman: Support for unsetenv() This adds unsetenv to posix, and uses it in the __delitem__ method of os.environ. (XXX Should we change the preferred name for putenv to setenv, for consistency?)
2001-10-18 22:31:59 -03:00
- readline now supports setting the startup_hook and the
pre_event_hook, and adds the add_history() function.
- os and posix supports chroot(), setgroups() and unsetenv() where
available. The stat(), fstat(), statvfs() and fstatvfs() functions
now return "pseudo-sequences" -- the various fields can now be
accessed as attributes (e.g. os.stat("/").st_mtime) but for
backwards compatibility they also behave as a fixed-length sequence.
Some platform-specific fields (e.g. st_rdev) are only accessible as
SF patch #462296: Add attributes to os.stat results; by Nick Mathewson. This is a big one, touching lots of files. Some of the platforms aren't tested yet. Briefly, this changes the return value of the os/posix functions stat(), fstat(), statvfs(), fstatvfs(), and the time functions localtime(), gmtime(), and strptime() from tuples into pseudo-sequences. When accessed as a sequence, they behave exactly as before. But they also have attributes like st_mtime or tm_year. The stat return value, moreover, has a few platform-specific attributes that are not available through the sequence interface (because everybody expects the sequence to have a fixed length, these couldn't be added there). If your platform's struct stat doesn't define st_blksize, st_blocks or st_rdev, they won't be accessible from Python either. (Still missing is a documentation update.)
2001-10-18 17:34:25 -03:00
attributes.
- time: localtime(), gmtime() and strptime() now return a
pseudo-sequence similar to the os.stat() return value, with
attributes like tm_year etc.
Document addition of chroot.
2001-10-04 19:46:41 -03:00
Add fix for getattr(obj, name, default). Rearrange a few things.
2001-10-16 18:34:49 -03:00
- Decompression objects in the zlib module now accept an optional
second parameter to decompress() that specifies the maximum amount
of memory to use for the uncompressed data.
Post-release fiddling (prep for 2.2b1).
2001-09-28 18:53:42 -03:00
Add entry for RAND_xxx() functions in socket module.
2001-10-19 00:40:19 -03:00
- optional SSL support in the socket module now exports OpenSSL
functions RAND_add(), RAND_egd(), and RAND_status(). These calls
are useful on platforms like Solaris where OpenSSL does not
Last minute updates for changes since 2.2a4. Unless Fred wants to add anything about the hotshot profiler, this file is ready for the 2.2b1 Windows build.
2001-10-19 02:35:40 -03:00
automatically seed its PRNG. Also, the keyfile and certfile
arguments to socket.ssl() are now optional.
- posixmodule (and by extension, the os module on POSIX platforms) now
exports O_LARGEFILE, O_DIRECT, O_DIRECTORY, and O_NOFOLLOW.
Add entry for RAND_xxx() functions in socket module.
2001-10-19 00:40:19 -03:00
Add fix for getattr(obj, name, default). Rearrange a few things.
2001-10-16 18:34:49 -03:00
Library
ReST-ification of the NEWS file. While the total number of changes are fairly large, most are caused by reformatting section and subsection headings. The changes fall into the following categories: * reformatted section and subsection headers. * escaped isolated asterisks which would be interpreted as starting bold or italic text (e.g. "void (*)(PyObject \*)"). * quoted stuff that looks like internal references but isn't (e.g. ``PyCmp_``). * changed visually balanced quotes to just use apostrophes (e.g. "'string'" instead of "`string'"). * introduced and indenting multiline chunks of code. * created one table (search for "New codecs").
2002-09-20 11:16:59 -03:00
-------
Partial patch from SF #452266, by Jason Petrone. This changes Pythread_start_thread() to return the thread ID, or -1 for an error. (It's technically an incompatible API change, but I doubt anyone calls it.)
2001-10-16 18:13:49 -03:00
SF patch [#466616] Exclude imported items from doctest, from Tim Hochberg. Also mucho fiddling to change the way doctest determines whether a thing is a function, module or class. Under 2.2, this really requires the functions in inspect.py (e.g., types.ClassType is close to meaningless now, if not outright misleading).
2001-10-02 00:53:41 -03:00
- doctest now excludes functions and classes not defined by the module
being tested, thanks to Tim Hochberg.
Added two very tardy notes about the 2.2b1 release, fixed a typo.
2001-10-22 15:41:51 -03:00
- HotShot, a new profiler implemented using a C-based callback, has
been added. This substantially reduces the overhead of profiling,
but it is still quite preliminary. Support modules and
documentation will be added in upcoming releases (before 2.2 final).
Add note about profile fix.
2001-10-04 07:19:00 -03:00
- profile now produces correct output in situations where an exception
raised in Python is cleared by C code (e.g. hasattr()). This used
to cause wrong output, including spurious claims of recursive
functions and attribution of time spent to the wrong function.
Remove code and docs for the OldProfile and HotProfile classes: code hasn't worked in years, docs were wrong, and they aren't interesting anymore regardless.
2001-10-07 00:12:08 -03:00
The code and documentation for the derived OldProfile and HotProfile
profiling classes was removed. The code hasn't worked for years (if
you tried to use them, they raised exceptions). OldProfile
intended to reproduce the behavior of the profiler Python used more
than 7 years ago, and isn't interesting anymore. HotProfile intended
to provide a faster profiler (but producing less information), and
that's a worthy goal we intend to meet via a different approach (but
without losing information).
A brand new implementation of Profile.calibrate(). This measures an actual run of the profiler, instead of timing a simplified simulation of part of what the profiler does. It computes a constant about 60% higher on my Win98SE box than the old method, and the new constant appears much more realistic. Deleted the undocumented simple(), instrumented(), and profiler_simulation() methods (which existed only to support the previous calibration method).
2001-10-09 02:31:56 -03:00
- Profile.calibrate() has a new implementation that should deliver
Allow the profiler's calibration constant to be specified in the constructor call, or via setting an instance or class vrbl. Rewrote the calibration docs. Modern boxes are so friggin' fast, and a profiler event does so much work anyway, that the cost of looking up an instance vrbl (the bias constant) per profile event just isn't a big deal.
2001-10-09 17:51:19 -03:00
a much better system-specific calibration constant. The constant can
now be specified in an instance constructor, or as a Profile class or
instance variable, instead of by editing profile.py's source code.
Calibration must still be done manually (see the docs for the profile
module).
Fix spelling.
2003-03-11 17:43:55 -04:00
Note that Profile.calibrate() must be overridden by subclasses.
Allow the profiler's calibration constant to be specified in the constructor call, or via setting an instance or class vrbl. Rewrote the calibration docs. Modern boxes are so friggin' fast, and a profiler event does so much work anyway, that the cost of looking up an instance vrbl (the bias constant) per profile event just isn't a big deal.
2001-10-09 17:51:19 -03:00
Improving the accuracy required exploiting detailed knowledge of
profiler internals; the earlier method abstracted away the details
and measured a simplified model instead, but consequently computed
a constant too small by a factor of 2 on some modern machines.
A brand new implementation of Profile.calibrate(). This measures an actual run of the profiler, instead of timing a simplified simulation of part of what the profiler does. It computes a constant about 60% higher on my Win98SE box than the old method, and the new constant appears much more realistic. Deleted the undocumented simple(), instrumented(), and profiler_simulation() methods (which existed only to support the previous calibration method).
2001-10-09 02:31:56 -03:00
Patch #462190, patch #464070: Support quoted printable in the binascii module. Decode and encode underscores for header style encoding. Fixes bug #463996.
2001-09-30 17:32:11 -03:00
- quopri's encode and decode methods take an optional header parameter,
Add note about new zlib feature.
2001-10-16 17:42:52 -03:00
which indicates whether output is intended for the header 'Q'
encoding.
SF bug #471720: ThreadingMixIn/TCPServer forgets close Solved with a helper method that calls finish_request() and then close_request(). The code is by Max Neunhöffer.
2001-10-18 15:02:07 -03:00
- The SocketServer.ThreadingMixIn class now closes the request after
finish_request() returns. (Not when it errors out though.)
ReST-ification of the NEWS file. While the total number of changes are fairly large, most are caused by reformatting section and subsection headings. The changes fall into the following categories: * reformatted section and subsection headers. * escaped isolated asterisks which would be interpreted as starting bold or italic text (e.g. "void (*)(PyObject \*)"). * quoted stuff that looks like internal references but isn't (e.g. ``PyCmp_``). * changed visually balanced quotes to just use apostrophes (e.g. "'string'" instead of "`string'"). * introduced and indenting multiline chunks of code. * created one table (search for "New codecs").
2002-09-20 11:16:59 -03:00
- The nntplib module's NNTP.body() method has grown a 'file' argument
Last minute updates for changes since 2.2a4. Unless Fred wants to add anything about the hotshot profiler, this file is ready for the 2.2b1 Windows build.
2001-10-19 02:35:40 -03:00
to allow saving the message body to a file.
- The email package has added a class email.Parser.HeaderParser which
only parses headers and does not recurse into the message's body.
Also, the module/class MIMEAudio has been added for representing
audio data (contributed by Anthony Baxter).
- ftplib should be able to handle files > 2GB.
- ConfigParser.getboolean() now also interprets TRUE, FALSE, YES, NO,
ON, and OFF.
Added two very tardy notes about the 2.2b1 release, fixed a typo.
2001-10-22 15:41:51 -03:00
- xml.dom.minidom NodeList objects now support the length attribute
and item() method as required by the DOM specifications.
Note removal of Demo/dns, point to PyDNS.
2001-10-02 20:15:37 -03:00
Tools/Demos
ReST-ification of the NEWS file. While the total number of changes are fairly large, most are caused by reformatting section and subsection headings. The changes fall into the following categories: * reformatted section and subsection headers. * escaped isolated asterisks which would be interpreted as starting bold or italic text (e.g. "void (*)(PyObject \*)"). * quoted stuff that looks like internal references but isn't (e.g. ``PyCmp_``). * changed visually balanced quotes to just use apostrophes (e.g. "'string'" instead of "`string'"). * introduced and indenting multiline chunks of code. * created one table (search for "New codecs").
2002-09-20 11:16:59 -03:00
-----------
Note removal of Demo/dns, point to PyDNS.
2001-10-02 20:15:37 -03:00
- Demo/dns was removed. It no longer serves any purpose; a package
derived from it is now maintained by Anthony Baxter, see
http://PyDNS.SourceForge.net.
Post-release fiddling (prep for 2.2b1).
2001-09-28 18:53:42 -03:00
Last minute updates for changes since 2.2a4. Unless Fred wants to add anything about the hotshot profiler, this file is ready for the 2.2b1 Windows build.
2001-10-19 02:35:40 -03:00
- The freeze tool has been made more robust, and two new options have
been added: -X and -E.
Post-release fiddling (prep for 2.2b1).
2001-09-28 18:53:42 -03:00
Build
ReST-ification of the NEWS file. While the total number of changes are fairly large, most are caused by reformatting section and subsection headings. The changes fall into the following categories: * reformatted section and subsection headers. * escaped isolated asterisks which would be interpreted as starting bold or italic text (e.g. "void (*)(PyObject \*)"). * quoted stuff that looks like internal references but isn't (e.g. ``PyCmp_``). * changed visually balanced quotes to just use apostrophes (e.g. "'string'" instead of "`string'"). * introduced and indenting multiline chunks of code. * created one table (search for "New codecs").
2002-09-20 11:16:59 -03:00
-----
Post-release fiddling (prep for 2.2b1).
2001-09-28 18:53:42 -03:00
Last minute updates for changes since 2.2a4. Unless Fred wants to add anything about the hotshot profiler, this file is ready for the 2.2b1 Windows build.
2001-10-19 02:35:40 -03:00
- configure will use CXX in LINKCC if CXX is used to build main() and
the system requires to link a C++ main using the C++ compiler.
Post-release fiddling (prep for 2.2b1).
2001-09-28 18:53:42 -03:00
C API
ReST-ification of the NEWS file. While the total number of changes are fairly large, most are caused by reformatting section and subsection headings. The changes fall into the following categories: * reformatted section and subsection headers. * escaped isolated asterisks which would be interpreted as starting bold or italic text (e.g. "void (*)(PyObject \*)"). * quoted stuff that looks like internal references but isn't (e.g. ``PyCmp_``). * changed visually balanced quotes to just use apostrophes (e.g. "'string'" instead of "`string'"). * introduced and indenting multiline chunks of code. * created one table (search for "New codecs").
2002-09-20 11:16:59 -03:00
-----
Post-release fiddling (prep for 2.2b1).
2001-09-28 18:53:42 -03:00
Note stricter tp_compare return value requirements.
2001-10-18 16:20:25 -03:00
- The documentation for the tp_compare slot is updated to require that
the return value must be -1, 0, 1; an arbitrary number <0 or >0 is
not correct. This is not yet enforced but will be enforced in
Python 2.3; even later, we may use -2 to indicate errors and +2 for
"NotImplemented". Right now, -1 should be used for an error return.
SF [#466125] PyLong_AsLongLong works for any integer. Generalize PyLong_AsLongLong to accept int arguments too. The real point is so that PyArg_ParseTuple's 'L' code does too. That code was undocumented (AFAICT), so documented it.
2001-09-30 02:09:37 -03:00
- PyLong_AsLongLong() now accepts int (as well as long) arguments.
Consequently, PyArg_ParseTuple's 'L' code also accepts int (as well
as long) arguments.
Partial patch from SF #452266, by Jason Petrone. This changes Pythread_start_thread() to return the thread ID, or -1 for an error. (It's technically an incompatible API change, but I doubt anyone calls it.)
2001-10-16 18:13:49 -03:00
- PyThread_start_new_thread() now returns a long int giving the thread
ID, if one can be calculated; it returns -1 for error, 0 if no
thread ID is calculated (this is an incompatible change, but only
the thread module used this API). This code has only really been
tested on Linux and Windows; other platforms please beware (and
report any bugs or strange behavior).
Note the Unicode changes from SF patch #470578.
2001-10-18 23:05:35 -03:00
- PyUnicode_FromEncodedObject() no longer accepts Unicode objects as
input.
Post-release fiddling (prep for 2.2b1).
2001-09-28 18:53:42 -03:00
New platforms
ReST-ification of the NEWS file. While the total number of changes are fairly large, most are caused by reformatting section and subsection headings. The changes fall into the following categories: * reformatted section and subsection headers. * escaped isolated asterisks which would be interpreted as starting bold or italic text (e.g. "void (*)(PyObject \*)"). * quoted stuff that looks like internal references but isn't (e.g. ``PyCmp_``). * changed visually balanced quotes to just use apostrophes (e.g. "'string'" instead of "`string'"). * introduced and indenting multiline chunks of code. * created one table (search for "New codecs").
2002-09-20 11:16:59 -03:00
-------------
Post-release fiddling (prep for 2.2b1).
2001-09-28 18:53:42 -03:00
Tests
ReST-ification of the NEWS file. While the total number of changes are fairly large, most are caused by reformatting section and subsection headings. The changes fall into the following categories: * reformatted section and subsection headers. * escaped isolated asterisks which would be interpreted as starting bold or italic text (e.g. "void (*)(PyObject \*)"). * quoted stuff that looks like internal references but isn't (e.g. ``PyCmp_``). * changed visually balanced quotes to just use apostrophes (e.g. "'string'" instead of "`string'"). * introduced and indenting multiline chunks of code. * created one table (search for "New codecs").
2002-09-20 11:16:59 -03:00
-----
Post-release fiddling (prep for 2.2b1).
2001-09-28 18:53:42 -03:00
Windows
ReST-ification of the NEWS file. While the total number of changes are fairly large, most are caused by reformatting section and subsection headings. The changes fall into the following categories: * reformatted section and subsection headers. * escaped isolated asterisks which would be interpreted as starting bold or italic text (e.g. "void (*)(PyObject \*)"). * quoted stuff that looks like internal references but isn't (e.g. ``PyCmp_``). * changed visually balanced quotes to just use apostrophes (e.g. "'string'" instead of "`string'"). * introduced and indenting multiline chunks of code. * created one table (search for "New codecs").
2002-09-20 11:16:59 -03:00
-------
Post-release fiddling (prep for 2.2b1).
2001-09-28 18:53:42 -03:00
Add item about new "Edit with IDLE" menu entry created by Windows installer.
2001-10-09 19:39:40 -03:00
- Installer: If you install IDLE, and don't disable file-extension
registration, a new "Edit with IDLE" context (right-click) menu entry
is created for .py and .pyw files.
SF patch [#466877] SIGBREAK is missing from signal module. Patch from Steve Scott to add SIGBREAK support (unique to Windows).
2001-10-01 14:58:40 -03:00
- The signal module now supports SIGBREAK on Windows, thanks to Steven
Scott. Note that SIGBREAK is unique to Windows. The default SIGBREAK
action remains to call Win32 ExitProcess(). This can be changed via
fix a couple nits with my use of ReST
2002-09-30 12:23:01 -03:00
signal.signal(). For example::
SF patch [#466877] SIGBREAK is missing from signal module. Patch from Steve Scott to add SIGBREAK support (unique to Windows).
2001-10-01 14:58:40 -03:00
ReST-ification of the NEWS file. While the total number of changes are fairly large, most are caused by reformatting section and subsection headings. The changes fall into the following categories: * reformatted section and subsection headers. * escaped isolated asterisks which would be interpreted as starting bold or italic text (e.g. "void (*)(PyObject \*)"). * quoted stuff that looks like internal references but isn't (e.g. ``PyCmp_``). * changed visually balanced quotes to just use apostrophes (e.g. "'string'" instead of "`string'"). * introduced and indenting multiline chunks of code. * created one table (search for "New codecs").
2002-09-20 11:16:59 -03:00
# Make Ctrl+Break raise KeyboardInterrupt, like Python's default Ctrl+C
# (SIGINT) behavior.
import signal
signal.signal(signal.SIGBREAK, signal.default_int_handler)
SF patch [#466877] SIGBREAK is missing from signal module. Patch from Steve Scott to add SIGBREAK support (unique to Windows).
2001-10-01 14:58:40 -03:00
ReST-ification of the NEWS file. While the total number of changes are fairly large, most are caused by reformatting section and subsection headings. The changes fall into the following categories: * reformatted section and subsection headers. * escaped isolated asterisks which would be interpreted as starting bold or italic text (e.g. "void (*)(PyObject \*)"). * quoted stuff that looks like internal references but isn't (e.g. ``PyCmp_``). * changed visually balanced quotes to just use apostrophes (e.g. "'string'" instead of "`string'"). * introduced and indenting multiline chunks of code. * created one table (search for "New codecs").
2002-09-20 11:16:59 -03:00
try:
Add newsitem for the two new unittest methods. Also, made some whitespace cleanup.
2002-12-29 16:14:11 -04:00
while 1:
pass
ReST-ification of the NEWS file. While the total number of changes are fairly large, most are caused by reformatting section and subsection headings. The changes fall into the following categories: * reformatted section and subsection headers. * escaped isolated asterisks which would be interpreted as starting bold or italic text (e.g. "void (*)(PyObject \*)"). * quoted stuff that looks like internal references but isn't (e.g. ``PyCmp_``). * changed visually balanced quotes to just use apostrophes (e.g. "'string'" instead of "`string'"). * introduced and indenting multiline chunks of code. * created one table (search for "New codecs").
2002-09-20 11:16:59 -03:00
except KeyboardInterrupt:
Add newsitem for the two new unittest methods. Also, made some whitespace cleanup.
2002-12-29 16:14:11 -04:00
# We get here on Ctrl+C or Ctrl+Break now; if we had not changed
# SIGBREAK, only on Ctrl+C (and Ctrl+Break would terminate the
# program without the possibility for any Python-level cleanup).
print "Clean exit"
SF patch [#466877] SIGBREAK is missing from signal module. Patch from Steve Scott to add SIGBREAK support (unique to Windows).
2001-10-01 14:58:40 -03:00
Post-release fiddling (prep for 2.2b1).
2001-09-28 18:53:42 -03:00
The usual post-release fiddling.
2001-09-07 22:25:47 -03:00
What's New in Python 2.2a4?
===========================
ReST-ification of the NEWS file. While the total number of changes are fairly large, most are caused by reformatting section and subsection headings. The changes fall into the following categories: * reformatted section and subsection headers. * escaped isolated asterisks which would be interpreted as starting bold or italic text (e.g. "void (*)(PyObject \*)"). * quoted stuff that looks like internal references but isn't (e.g. ``PyCmp_``). * changed visually balanced quotes to just use apostrophes (e.g. "'string'" instead of "`string'"). * introduced and indenting multiline chunks of code. * created one table (search for "New codecs").
2002-09-20 11:16:59 -03:00
*Release date: 28-Sep-2001*
Separate out the type/class-related news and reword some items. Add news items about comparisons, repr(), __class__ assignment.
2001-09-25 01:15:41 -03:00
Type/class unification and new-style classes
ReST-ification of the NEWS file. While the total number of changes are fairly large, most are caused by reformatting section and subsection headings. The changes fall into the following categories: * reformatted section and subsection headers. * escaped isolated asterisks which would be interpreted as starting bold or italic text (e.g. "void (*)(PyObject \*)"). * quoted stuff that looks like internal references but isn't (e.g. ``PyCmp_``). * changed visually balanced quotes to just use apostrophes (e.g. "'string'" instead of "`string'"). * introduced and indenting multiline chunks of code. * created one table (search for "New codecs").
2002-09-20 11:16:59 -03:00
--------------------------------------------
Separate out the type/class-related news and reword some items. Add news items about comparisons, repr(), __class__ assignment.
2001-09-25 01:15:41 -03:00
- pydoc and inspect are now aware of new-style classes;
e.g. help(list) at the interactive prompt now shows proper
documentation for all operations on list objects.
- Applications using Jim Fulton's ExtensionClass module can now safely
be used with Python 2.2. In particular, Zope 2.4.1 now works with
Python 2.2 (as well as with Python 2.1.1). The Demo/metaclass
examples also work again. It is hoped that Gtk and Boost also work
with 2.2a4 and beyond. (If you can confirm this, please write
webmaster@python.org; if there are still problems, please open a bug
report on SourceForge.)
The usual post-release fiddling.
2001-09-07 22:25:47 -03:00
Make properties discoverable from Python: - property() now takes 4 keyword arguments: fget, fset, fdel, doc. Note that the real purpose of the 'f' prefix is to make fdel fit in ('del' is a keyword, so can't used as a keyword argument name). - These map to visible readonly attributes 'fget', 'fset', 'fdel', and '__doc__' in the property object. - fget/fset/fdel weren't discoverable from Python before. - __doc__ is new, and allows to associate a docstring with a property.
2001-09-24 18:17:50 -03:00
- property() now takes 4 keyword arguments: fget, fset, fdel and doc.
Fix typos
2002-05-07 17:58:03 -03:00
These map to read-only attributes 'fget', 'fset', 'fdel', and '__doc__'
Make properties discoverable from Python: - property() now takes 4 keyword arguments: fget, fset, fdel, doc. Note that the real purpose of the 'f' prefix is to make fdel fit in ('del' is a keyword, so can't used as a keyword argument name). - These map to visible readonly attributes 'fget', 'fset', 'fdel', and '__doc__' in the property object. - fget/fset/fdel weren't discoverable from Python before. - __doc__ is new, and allows to associate a docstring with a property.
2001-09-24 18:17:50 -03:00
in the constructed property object. fget, fset and fdel weren't
discoverable from Python in 2.2a3. __doc__ is new, and allows to
associate a docstring with a property.
Separate out the type/class-related news and reword some items. Add news items about comparisons, repr(), __class__ assignment.
2001-09-25 01:15:41 -03:00
- Comparison overloading is now more completely implemented. For
example, a str subclass instance can properly be compared to a str
instance, and it can properly overload comparison. Ditto for most
other built-in object types.
- The repr() of new-style classes has changed; instead of <type
'M.Foo'> a new-style class is now rendered as <class 'M.Foo'>,
*except* for built-in types, which are still rendered as <type
'Foo'> (to avoid upsetting existing code that might parse or
otherwise rely on repr() of certain type objects).
- The repr() of new-style objects is now always <Foo object at XXX>;
previously, it was sometimes <Foo instance at XXX>.
- For new-style classes, what was previously called __getattr__ is now
called __getattribute__. This method, if defined, is called for
Fix some typos
2001-10-21 22:47:26 -03:00
*every* attribute access. A new __getattr__ hook more similar to the
Separate out the type/class-related news and reword some items. Add news items about comparisons, repr(), __class__ assignment.
2001-09-25 01:15:41 -03:00
one in classic classes is defined which is called only if regular
attribute access raises AttributeError; to catch *all* attribute
access, you can use __getattribute__ (for new-style classes). If
both are defined, __getattribute__ is called first, and if it raises
AttributeError, __getattr__ is called.
- The __class__ attribute of new-style objects can be assigned to.
The new class must have the same C-level object layout as the old
class.
- The builtin file type can be subclassed now. In the usual pattern,
"file" is the name of the builtin type, and file() is a new builtin
constructor, with the same signature as the builtin open() function.
file() is now the preferred way to open a file.
- Previously, __new__ would only see sequential arguments passed to
the type in a constructor call; __init__ would see both sequential
and keyword arguments. This made no sense whatsoever any more, so
now both __new__ and __init__ see all arguments.
- Previously, hash() applied to an instance of a subclass of str or
unicode always returned 0. This has been repaired.
- Previously, an operation on an instance of a subclass of an
immutable type (int, long, float, complex, tuple, str, unicode),
where the subtype didn't override the operation (and so the
operation was handled by the builtin type), could return that
instance instead a value of the base type. For example, if s was of
Fix typos
2002-05-07 17:58:03 -03:00
a str subclass type, s[:] returned s as-is. Now it returns a str
Separate out the type/class-related news and reword some items. Add news items about comparisons, repr(), __class__ assignment.
2001-09-25 01:15:41 -03:00
with the same value as s.
Merged changes from 22a4 branch.
2001-09-28 12:26:12 -03:00
- Provisional support for pickling new-style objects has been added.
Separate out the type/class-related news and reword some items. Add news items about comparisons, repr(), __class__ assignment.
2001-09-25 01:15:41 -03:00
Core
ReST-ification of the NEWS file. While the total number of changes are fairly large, most are caused by reformatting section and subsection headings. The changes fall into the following categories: * reformatted section and subsection headers. * escaped isolated asterisks which would be interpreted as starting bold or italic text (e.g. "void (*)(PyObject \*)"). * quoted stuff that looks like internal references but isn't (e.g. ``PyCmp_``). * changed visually balanced quotes to just use apostrophes (e.g. "'string'" instead of "`string'"). * introduced and indenting multiline chunks of code. * created one table (search for "New codecs").
2002-09-20 11:16:59 -03:00
----
Separate out the type/class-related news and reword some items. Add news items about comparisons, repr(), __class__ assignment.
2001-09-25 01:15:41 -03:00
Generalize file.writelines() to allow iterable objects.
2001-09-23 01:06:05 -03:00
- file.writelines() now accepts any iterable object producing strings.
Note about enhancements to unicode().
2001-09-20 09:59:37 -03:00
- PyUnicode_FromEncodedObject() now works very much like
PyObject_Str(obj) in that it tries to use __str__/tp_str
on the object if the object is not a string or buffer. This
makes unicode() behave like str() when applied to non-string/buffer
objects.
Fix some typos
2001-10-21 22:47:26 -03:00
- PyFile_WriteObject now passes Unicode objects to the file's write
method. As a result, all file-like objects which may be the target
Patch #462849: Pass Unicode objects to file's .write method.
2001-09-19 10:47:32 -03:00
of a print statement must support Unicode objects, i.e. they must
at least convert them into ASCII strings.
All the news that fits, we print. (Went through the logs looking for nuggets. This is what I found.)
2001-09-18 12:21:04 -03:00
- Thread scheduling on Solaris should be improved; it is no longer
necessary to insert a small sleep at the start of a thread in order
to let other runnable threads be scheduled.
The usual post-release fiddling.
2001-09-07 22:25:47 -03:00
Library
ReST-ification of the NEWS file. While the total number of changes are fairly large, most are caused by reformatting section and subsection headings. The changes fall into the following categories: * reformatted section and subsection headers. * escaped isolated asterisks which would be interpreted as starting bold or italic text (e.g. "void (*)(PyObject \*)"). * quoted stuff that looks like internal references but isn't (e.g. ``PyCmp_``). * changed visually balanced quotes to just use apostrophes (e.g. "'string'" instead of "`string'"). * introduced and indenting multiline chunks of code. * created one table (search for "New codecs").
2002-09-20 11:16:59 -03:00
-------
The usual post-release fiddling.
2001-09-07 22:25:47 -03:00
Added note about new StringIO/cStringIO feature.
2001-09-27 11:17:33 -03:00
- StringIO.StringIO instances and cStringIO.StringIO instances support
read character buffer compatible objects for their .write() methods.
These objects are converted to strings and then handled as such
by the instances.
Added a note about the new email package.
2001-09-24 01:28:10 -03:00
- The "email" package has been added. This is basically a port of the
mimelib package <http://sf.net/projects/mimelib> with API changes
and some implementations updated to use iterators and generators.
Make difflib.ndiff() and difflib.Differ.compare() generators. This restores the 2.1 ability of Tools/scripts/ndiff.py to start producing output before the entire comparison is complete.
2001-09-22 18:30:22 -03:00
- difflib.ndiff() and difflib.Differ.compare() are generators now. This
restores the ability of Tools/scripts/ndiff.py to start producing output
before the entire comparison is complete.
{String,cString}IO.StringIO's support iteration.
2001-09-22 01:44:21 -03:00
- StringIO.StringIO instances and cStringIO.StringIO instances support
iteration just like file objects (i.e. their .readline() method is
called for each iteration until it returns an empty string).
Docs and News item for the codecs.py additions.
2001-09-19 08:33:31 -03:00
- The codecs module has grown four new helper APIs to access
builtin codecs: getencoder(), getdecoder(), getreader(),
getwriter().
All the news that fits, we print. (Went through the logs looking for nuggets. This is what I found.)
2001-09-18 12:21:04 -03:00
- SimpleXMLRPCServer: a new module (based upon SimpleHTMLServer)
simplifies writing XML RPC servers.
Fixed a minor typo.
2001-09-28 14:01:02 -03:00
- os.path.realpath(): a new function that returns the absolute pathname
All the news that fits, we print. (Went through the logs looking for nuggets. This is what I found.)
2001-09-18 12:21:04 -03:00
after interpretation of symbolic links. On non-Unix systems, this
is an alias for os.path.abspath().
Generalize operator.indexOf (PySequence_Index) to work with any iterable object. I'm not sure how that got overlooked before! Got rid of the internal _PySequence_IterContains, introduced a new internal _PySequence_IterSearch, and rewrote all the iteration-based "count of", "index of", and "is the object in it or not?" routines to just call the new function. I suppose it's slower this way, but the code duplication was getting depressing.
2001-09-08 01:00:12 -03:00
- operator.indexOf() (PySequence_Index() in the C API) now works with any
iterable object.
All the news that fits, we print. (Went through the logs looking for nuggets. This is what I found.)
2001-09-18 12:21:04 -03:00
- smtplib now supports various authentication and security features of
the SMTP protocol through the new login() and starttls() methods.
- hmac: a new module implementing keyed hashing for message
authentication.
Mention SMTP additions and hmac module.
2001-09-14 13:35:16 -03:00
All the news that fits, we print. (Went through the logs looking for nuggets. This is what I found.)
2001-09-18 12:21:04 -03:00
- mimetypes now recognizes more extensions and file types. At the
same time, some mappings not sanctioned by IANA were removed.
Mention SMTP additions and hmac module.
2001-09-14 13:35:16 -03:00
All the news that fits, we print. (Went through the logs looking for nuggets. This is what I found.)
2001-09-18 12:21:04 -03:00
- The "compiler" package has been brought up to date to the state of
News about compiler and pydoc.
2001-09-20 02:30:24 -03:00
Python 2.2 bytecode generation. It has also been promoted from a
Tool to a standard library package. (Tools/compiler still exists as
a sample driver.)
The usual post-release fiddling.
2001-09-07 22:25:47 -03:00
Build
ReST-ification of the NEWS file. While the total number of changes are fairly large, most are caused by reformatting section and subsection headings. The changes fall into the following categories: * reformatted section and subsection headers. * escaped isolated asterisks which would be interpreted as starting bold or italic text (e.g. "void (*)(PyObject \*)"). * quoted stuff that looks like internal references but isn't (e.g. ``PyCmp_``). * changed visually balanced quotes to just use apostrophes (e.g. "'string'" instead of "`string'"). * introduced and indenting multiline chunks of code. * created one table (search for "New codecs").
2002-09-20 11:16:59 -03:00
-----
The usual post-release fiddling.
2001-09-07 22:25:47 -03:00
All the news that fits, we print. (Went through the logs looking for nuggets. This is what I found.)
2001-09-18 12:21:04 -03:00
- Large file support (LFS) is now automatic when the platform supports
it; no more manual configuration tweaks are needed. On Linux, at
least, it's possible to have a system whose C library supports large
files but whose kernel doesn't; in this case, large file support is
still enabled but doesn't do you any good unless you upgrade your
kernel or share your Python executable with another system whose
kernel has large file support.
- The configure script now supplies plausible defaults in a
cross-compilation environment. This doesn't mean that the supplied
values are always correct, or that cross-compilation now works
flawlessly -- but it's a first step (and it shuts up most of
autoconf's warnings about AC_TRY_RUN).
- The Unix build is now a bit less chatty, courtesy of the parser
generator. The build is completely silent (except for errors) when
using "make -s", thanks to a -q option to setup.py.
The usual post-release fiddling.
2001-09-07 22:25:47 -03:00
C API
ReST-ification of the NEWS file. While the total number of changes are fairly large, most are caused by reformatting section and subsection headings. The changes fall into the following categories: * reformatted section and subsection headers. * escaped isolated asterisks which would be interpreted as starting bold or italic text (e.g. "void (*)(PyObject \*)"). * quoted stuff that looks like internal references but isn't (e.g. ``PyCmp_``). * changed visually balanced quotes to just use apostrophes (e.g. "'string'" instead of "`string'"). * introduced and indenting multiline chunks of code. * created one table (search for "New codecs").
2002-09-20 11:16:59 -03:00
-----
The usual post-release fiddling.
2001-09-07 22:25:47 -03:00
All the news that fits, we print. (Went through the logs looking for nuggets. This is what I found.)
2001-09-18 12:21:04 -03:00
- The "structmember" API now supports some new flag bits to deny read
and/or write access to attributes in restricted execution mode.
The usual post-release fiddling.
2001-09-07 22:25:47 -03:00
New platforms
ReST-ification of the NEWS file. While the total number of changes are fairly large, most are caused by reformatting section and subsection headings. The changes fall into the following categories: * reformatted section and subsection headers. * escaped isolated asterisks which would be interpreted as starting bold or italic text (e.g. "void (*)(PyObject \*)"). * quoted stuff that looks like internal references but isn't (e.g. ``PyCmp_``). * changed visually balanced quotes to just use apostrophes (e.g. "'string'" instead of "`string'"). * introduced and indenting multiline chunks of code. * created one table (search for "New codecs").
2002-09-20 11:16:59 -03:00
-------------
The usual post-release fiddling.
2001-09-07 22:25:47 -03:00
All the news that fits, we print. (Went through the logs looking for nuggets. This is what I found.)
2001-09-18 12:21:04 -03:00
- Compaq's iPAQ handheld, running the "familiar" Linux distribution
(http://familiar.handhelds.org).
The usual post-release fiddling.
2001-09-07 22:25:47 -03:00
Tests
ReST-ification of the NEWS file. While the total number of changes are fairly large, most are caused by reformatting section and subsection headings. The changes fall into the following categories: * reformatted section and subsection headers. * escaped isolated asterisks which would be interpreted as starting bold or italic text (e.g. "void (*)(PyObject \*)"). * quoted stuff that looks like internal references but isn't (e.g. ``PyCmp_``). * changed visually balanced quotes to just use apostrophes (e.g. "'string'" instead of "`string'"). * introduced and indenting multiline chunks of code. * created one table (search for "New codecs").
2002-09-20 11:16:59 -03:00
-----
The usual post-release fiddling.
2001-09-07 22:25:47 -03:00
Make difflib.ndiff() and difflib.Differ.compare() generators. This restores the 2.1 ability of Tools/scripts/ndiff.py to start producing output before the entire comparison is complete.
2001-09-22 18:30:22 -03:00
- The "classic" standard tests, which work by comparing stdout to
an expected-output file under Lib/test/output/, no longer stop at
the first mismatch. Instead the test is run to completion, and a
variant of ndiff-style comparison is used to report all differences.
This is much easier to understand than the previous style of reporting.
- The unittest-based standard tests now use regrtest's test_main()
convention, instead of running as a side-effect of merely being
imported. This allows these tests to be run in more natural and
flexible ways as unittests, outside the regrtest framework.
- regrtest.py is much better integrated with unittest and doctest now,
especially in regard to reporting errors.
The usual post-release fiddling.
2001-09-07 22:25:47 -03:00
Windows
ReST-ification of the NEWS file. While the total number of changes are fairly large, most are caused by reformatting section and subsection headings. The changes fall into the following categories: * reformatted section and subsection headers. * escaped isolated asterisks which would be interpreted as starting bold or italic text (e.g. "void (*)(PyObject \*)"). * quoted stuff that looks like internal references but isn't (e.g. ``PyCmp_``). * changed visually balanced quotes to just use apostrophes (e.g. "'string'" instead of "`string'"). * introduced and indenting multiline chunks of code. * created one table (search for "New codecs").
2002-09-20 11:16:59 -03:00
-------
The usual post-release fiddling.
2001-09-07 22:25:47 -03:00
All the news that fits, we print. (Went through the logs looking for nuggets. This is what I found.)
2001-09-18 12:21:04 -03:00
- Large file support now also works for files > 4GB, on filesystems
Make difflib.ndiff() and difflib.Differ.compare() generators. This restores the 2.1 ability of Tools/scripts/ndiff.py to start producing output before the entire comparison is complete.
2001-09-22 18:30:22 -03:00
that support it (NTFS under Windows 2000). See "What's New in
Python 2.2a3" for more detail.
All the news that fits, we print. (Went through the logs looking for nuggets. This is what I found.)
2001-09-18 12:21:04 -03:00
The usual post-release fiddling.
2001-09-07 22:25:47 -03:00
"The usual" post-release fiddling.
2001-08-22 18:36:50 -03:00
What's New in Python 2.2a3?
===========================
ReST-ification of the NEWS file. While the total number of changes are fairly large, most are caused by reformatting section and subsection headings. The changes fall into the following categories: * reformatted section and subsection headers. * escaped isolated asterisks which would be interpreted as starting bold or italic text (e.g. "void (*)(PyObject \*)"). * quoted stuff that looks like internal references but isn't (e.g. ``PyCmp_``). * changed visually balanced quotes to just use apostrophes (e.g. "'string'" instead of "`string'"). * introduced and indenting multiline chunks of code. * created one table (search for "New codecs").
2002-09-20 11:16:59 -03:00
*Release Date: 07-Sep-2001*
"The usual" post-release fiddling.
2001-08-22 18:36:50 -03:00
Core
ReST-ification of the NEWS file. While the total number of changes are fairly large, most are caused by reformatting section and subsection headings. The changes fall into the following categories: * reformatted section and subsection headers. * escaped isolated asterisks which would be interpreted as starting bold or italic text (e.g. "void (*)(PyObject \*)"). * quoted stuff that looks like internal references but isn't (e.g. ``PyCmp_``). * changed visually balanced quotes to just use apostrophes (e.g. "'string'" instead of "`string'"). * introduced and indenting multiline chunks of code. * created one table (search for "New codecs").
2002-09-20 11:16:59 -03:00
----
"The usual" post-release fiddling.
2001-08-22 18:36:50 -03:00
Raise OverflowError when appropriate on long->float conversion. Most of the fiddling is simply due to that no caller of PyLong_AsDouble ever checked for failure (so that's fixing old bugs). PyLong_AsDouble is much faster for big inputs now too, but that's more of a happy consequence than a design goal.
2001-09-04 02:14:19 -03:00
- Conversion of long to float now raises OverflowError if the long is too
big to represent as a C double.
New restriction on pow(x, y, z): If z is not None, x and y must be of integer types, and y must be >= 0. See discussion at http://sf.net/tracker/index.php?func=detail&aid=457066&group_id=5470&atid=105470
2001-09-03 05:35:41 -03:00
- 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 types and the second argument is negative (in which latter case
the arguments are converted to float, so this is really the same
restriction).
Make dir() wordier (see the new docstring). The new behavior is a mixed bag. It's clearly wrong for classic classes, at heart because a classic class doesn't have a __class__ attribute, and I'm unclear on whether that's feature or bug. I'll repair this once I find out (in the meantime, dir() applied to classic classes won't find the base classes, while dir() applied to a classic-class instance *will* find the base classes but not *their* base classes). Please give the new dir() a try and see whether you love it or hate it. The new dir([]) behavior is something I could come to love. Here's something to hate: >>> class C: ... pass ... >>> c = C() >>> dir(c) ['__doc__', '__module__'] >>> The idea that an instance has a __doc__ attribute is jarring (of course it's really c.__class__.__doc__ == C.__doc__; likewise for __module__). OTOH, the code already has too many special cases, and dir(x) doesn't have a compelling or clear purpose when x isn't a module.
2001-09-03 02:47:38 -03:00
- The builtin dir() now returns more information, and sometimes much
more, generally naming all attributes of an object, and all attributes
reachable from the object via its class, and from its class's base
classes, and so on from them too. Example: in 2.2a2, dir([]) returned
an empty list. In 2.2a3,
>>> dir([])
['__add__', '__class__', '__contains__', '__delattr__', '__delitem__',
'__eq__', '__ge__', '__getattr__', '__getitem__', '__getslice__',
'__gt__', '__hash__', '__iadd__', '__imul__', '__init__', '__le__',
'__len__', '__lt__', '__mul__', '__ne__', '__new__', '__repr__',
'__rmul__', '__setattr__', '__setitem__', '__setslice__', '__str__',
'append', 'count', 'extend', 'index', 'insert', 'pop', 'remove',
'reverse', 'sort']
dir(module) continues to return only the module's attributes, though.
Start items w/ "-" instead of "+" (consistency w/ earlier versions). Stephen Hansen reported via email that he didn't finish the port to Borland C, so remove the old item saying it worked and add a new item saying what I know; I've asked Stephen for more details.
2001-09-02 00:40:59 -03:00
- Overflowing operations on plain ints now return a long int rather
Add various and sundry news items -- most mine, one Barry's, one Michael Hudson's.
2001-08-31 15:31:35 -03:00
than raising OverflowError. This is a partial implementation of PEP
237. You can use -Wdefault::OverflowWarning to enable a warning for
this situation, and -Werror::OverflowWarning to revert to the old
OverflowError exception.
Rename the -D option to -Q, to avoid a Jython option name conflict.
2001-09-04 00:26:15 -03:00
- A new command line option, -Q<arg>, is added to control run-time
Add various and sundry news items -- most mine, one Barry's, one Michael Hudson's.
2001-08-31 15:31:35 -03:00
warnings for the use of classic division. (See PEP 238.) Possible
Merging 2.2a3 branch changes back into trunk
2001-09-07 15:13:44 -03:00
values are -Qold, -Qwarn, -Qwarnall, and -Qnew. The default is
-Qold, meaning the / operator has its classic meaning and no
warnings are issued. Using -Qwarn issues a run-time warning about
all uses of classic division for int and long arguments; -Qwarnall
also warns about classic division for float and complex arguments
SF bug #488514: -Qnew needs work Big Hammer to implement -Qnew as PEP 238 says it should work (a global option affecting all instances of "/"). pydebug.h, main.c, pythonrun.c: define a private _Py_QnewFlag flag, true iff -Qnew is passed on the command line. This should go away (as the comments say) when true division becomes The Rule. This is deliberately not exposed to runtime inspection or modification: it's a one-way one-shot switch to pretend you're using Python 3. ceval.c: when _Py_QnewFlag is set, treat BINARY_DIVIDE as BINARY_TRUE_DIVIDE. test_{descr, generators, zipfile}.py: fiddle so these pass under -Qnew too. This was just a matter of s!/!//! in test_generators and test_zipfile. test_descr was trickier, as testbinop() is passed assumptions that "/" is the same as calling a "__div__" method; put a temporary hack there to call "__truediv__" instead when the method name is "__div__" and 1/2 evaluates to 0.5. Three standard tests still fail under -Qnew (on Windows; somebody please try the Linux tests with -Qnew too! Linux runs a whole bunch of tests Windows doesn't): test_augassign test_class test_coercion I can't stay awake longer to stare at this (be my guest). Offhand cures weren't obvious, nor was it even obvious that cures are possible without major hackery. Question: when -Qnew is in effect, should calls to __div__ magically change into calls to __truediv__? See "major hackery" at tail end of last paragraph <wink>.
2001-12-06 02:23:26 -04:00
(for use with fixdiv.py).
ReST-ification of the NEWS file. While the total number of changes are fairly large, most are caused by reformatting section and subsection headings. The changes fall into the following categories: * reformatted section and subsection headers. * escaped isolated asterisks which would be interpreted as starting bold or italic text (e.g. "void (*)(PyObject \*)"). * quoted stuff that looks like internal references but isn't (e.g. ``PyCmp_``). * changed visually balanced quotes to just use apostrophes (e.g. "'string'" instead of "`string'"). * introduced and indenting multiline chunks of code. * created one table (search for "New codecs").
2002-09-20 11:16:59 -03:00
[Note: the remainder of this item (preserved below) became
obsolete in 2.2c1 -- -Qnew has global effect in 2.2] ::
Using -Qnew is questionable; it turns on new division by default, but
only in the __main__ module. You can usefully combine -Qwarn or
-Qwarnall and -Qnew: this gives the __main__ module new division, and
warns about classic division everywhere else.
Add various and sundry news items -- most mine, one Barry's, one Michael Hudson's.
2001-08-31 15:31:35 -03:00
Start items w/ "-" instead of "+" (consistency w/ earlier versions). Stephen Hansen reported via email that he didn't finish the port to Borland C, so remove the old item saying it worked and add a new item saying what I know; I've asked Stephen for more details.
2001-09-02 00:40:59 -03:00
- Many built-in types can now be subclassed. This applies to int,
Add various and sundry news items -- most mine, one Barry's, one Michael Hudson's.
2001-08-31 15:31:35 -03:00
long, float, str, unicode, and tuple. (The types complex, list and
dictionary can also be subclassed; this was introduced earlier.)
Note that restrictions apply when subclassing immutable built-in
types: you can only affect the value of the instance by overloading
__new__. You can add mutable attributes, and the subclass instances
will have a __dict__ attribute, but you cannot change the "value"
(as implemented by the base class) of an immutable subclass instance
once it is created.
Add news about dictionary() constructor.
2001-09-02 10:44:35 -03:00
- The dictionary constructor now takes an optional argument, a
mapping-like object, and initializes the dictionary from its
(key, value) pairs.
Start items w/ "-" instead of "+" (consistency w/ earlier versions). Stephen Hansen reported via email that he didn't finish the port to Borland C, so remove the old item saying it worked and add a new item saying what I know; I've asked Stephen for more details.
2001-09-02 00:40:59 -03:00
- A new built-in type, super, has been added. This facilitates making
Add various and sundry news items -- most mine, one Barry's, one Michael Hudson's.
2001-08-31 15:31:35 -03:00
"cooperative super calls" in a multiple inheritance setting. For an
explanation, see http://www.python.org/2.2/descrintro.html#cooperation
Rename 'getset' to 'property'.
2001-09-06 19:02:58 -03:00
- A new built-in type, property, has been added. This enables the
creation of "properties". These are attributes implemented by
getter and setter functions (or only one of these for read-only or
write-only attributes), without the need to override __getattr__.
See http://www.python.org/2.2/descrintro.html#property
Add various and sundry news items -- most mine, one Barry's, one Michael Hudson's.
2001-08-31 15:31:35 -03:00
Start items w/ "-" instead of "+" (consistency w/ earlier versions). Stephen Hansen reported via email that he didn't finish the port to Borland C, so remove the old item saying it worked and add a new item saying what I know; I've asked Stephen for more details.
2001-09-02 00:40:59 -03:00
- The syntax of floating-point and imaginary literals has been
SF patch #455966: Allow leading 0 in float/imag literals. Consequences for Jython still unknown (but raised on Jython-Dev).
2001-08-30 17:51:59 -03:00
liberalized, to allow leading zeroes. Examples of literals now
legal that were SyntaxErrors before:
00.0 0e3 0100j 07.5 00000000000000000008.
Start items w/ "-" instead of "+" (consistency w/ earlier versions). Stephen Hansen reported via email that he didn't finish the port to Borland C, so remove the old item saying it worked and add a new item saying what I know; I've asked Stephen for more details.
2001-09-02 00:40:59 -03:00
- An old tokenizer bug allowed floating point literals with an incomplete
Note change in fp literal syntax (e.g. "3e-" worked by accident before).
2001-08-28 17:56:27 -03:00
exponent, such as 1e and 3.1e-. Such literals now raise SyntaxError.
"The usual" post-release fiddling.
2001-08-22 18:36:50 -03:00
Library
ReST-ification of the NEWS file. While the total number of changes are fairly large, most are caused by reformatting section and subsection headings. The changes fall into the following categories: * reformatted section and subsection headers. * escaped isolated asterisks which would be interpreted as starting bold or italic text (e.g. "void (*)(PyObject \*)"). * quoted stuff that looks like internal references but isn't (e.g. ``PyCmp_``). * changed visually balanced quotes to just use apostrophes (e.g. "'string'" instead of "`string'"). * introduced and indenting multiline chunks of code. * created one table (search for "New codecs").
2002-09-20 11:16:59 -03:00
-------
"The usual" post-release fiddling.
2001-08-22 18:36:50 -03:00
Report patch #416079 changes.
2001-09-06 05:54:16 -03:00
- telnetlib includes symbolic names for the options, and support for
Patch #630829: Don't block on IAC, process suboptions.
2002-11-04 05:56:00 -04:00
setting an option negotiation callback. It also supports processing
of suboptions.
Report patch #416079 changes.
2001-09-06 05:54:16 -03:00
Rework the way we try to check for libm overflow, given that C99 no longer requires that errno ever get set, and it looks like glibc is already playing that game. New rules: + Never use HUGE_VAL. Use the new Py_HUGE_VAL instead. + Never believe errno. If overflow is the only thing you're interested in, use the new Py_OVERFLOWED(x) macro. If you're interested in any libm errors, use the new Py_SET_ERANGE_IF_OVERFLOW(x) macro, which attempts to set errno the way C89 said it worked. Unfortunately, none of these are reliable, but they work on Windows and I *expect* under glibc too.
2001-09-05 19:36:56 -03:00
- The new C standard no longer requires that math libraries set errno to
ERANGE on overflow. For platform libraries that exploit this new
freedom, Python's overflow-checking was wholly broken. A new overflow-
checking scheme attempts to repair that, but may not be reliable on all
platforms (C doesn't seem to provide anything both useful and portable
in this area anymore).
Patch #428326: New class threading.Timer.
2001-09-05 10:44:54 -03:00
- Asynchronous timeout actions are available through the new class
threading.Timer.
Return reasonable results for math.log(long) and math.log10(long) (we were getting Infs, NaNs, or nonsense in 2.1 and before; in yesterday's CVS we were getting OverflowError; but these functions always make good sense for positive arguments, no matter how large).
2001-09-04 21:53:45 -03:00
- math.log and math.log10 now return sensible results for even huge
long arguments. For example, math.log10(10 ** 10000) ~= 10000.0.
Start items w/ "-" instead of "+" (consistency w/ earlier versions). Stephen Hansen reported via email that he didn't finish the port to Borland C, so remove the old item saying it worked and add a new item saying what I know; I've asked Stephen for more details.
2001-09-02 00:40:59 -03:00
- A new function, imp.lock_held(), returns 1 when the import lock is
Add a new function imp.lock_held(), and use it to skip test_threaded_import when that test is doomed to deadlock.
2001-08-30 02:16:13 -03:00
currently held. See the docs for the imp module.
Start items w/ "-" instead of "+" (consistency w/ earlier versions). Stephen Hansen reported via email that he didn't finish the port to Borland C, so remove the old item saying it worked and add a new item saying what I know; I've asked Stephen for more details.
2001-09-02 00:40:59 -03:00
- pickle, cPickle and marshal on 32-bit platforms can now correctly read
marshal.c r_long64: When reading a TYPE_INT64 value on a box with 32-bit ints, convert to PyLong (rather than throwing away the high-order 32 bits).
2001-08-28 23:28:42 -03:00
dumps containing ints written on platforms where Python ints are 8 bytes.
When read on a box where Python ints are 4 bytes, such values are
converted to Python longs.
Start items w/ "-" instead of "+" (consistency w/ earlier versions). Stephen Hansen reported via email that he didn't finish the port to Borland C, so remove the old item saying it worked and add a new item saying what I know; I've asked Stephen for more details.
2001-09-02 00:40:59 -03:00
- In restricted execution mode (using the rexec module), unmarshalling
Add various and sundry news items -- most mine, one Barry's, one Michael Hudson's.
2001-08-31 15:31:35 -03:00
code objects is no longer allowed. This plugs a security hole.
Added note of unittest.py changes that fixed bug 451309
2001-09-06 13:05:17 -03:00
- unittest.TestResult instances no longer store references to tracebacks
generated by test failures. This prevents unexpected dangling references
to objects that should be garbage collected between tests.
"The usual" post-release fiddling.
2001-08-22 18:36:50 -03:00
Tools
ReST-ification of the NEWS file. While the total number of changes are fairly large, most are caused by reformatting section and subsection headings. The changes fall into the following categories: * reformatted section and subsection headers. * escaped isolated asterisks which would be interpreted as starting bold or italic text (e.g. "void (*)(PyObject \*)"). * quoted stuff that looks like internal references but isn't (e.g. ``PyCmp_``). * changed visually balanced quotes to just use apostrophes (e.g. "'string'" instead of "`string'"). * introduced and indenting multiline chunks of code. * created one table (search for "New codecs").
2002-09-20 11:16:59 -03:00
-----
"The usual" post-release fiddling.
2001-08-22 18:36:50 -03:00
Merging 2.2a3 branch changes back into trunk
2001-09-07 15:13:44 -03:00
- Tools/scripts/fixdiv.py has been added which can be used to fix
division operators as per PEP 238.
"The usual" post-release fiddling.
2001-08-22 18:36:50 -03:00
Build
ReST-ification of the NEWS file. While the total number of changes are fairly large, most are caused by reformatting section and subsection headings. The changes fall into the following categories: * reformatted section and subsection headers. * escaped isolated asterisks which would be interpreted as starting bold or italic text (e.g. "void (*)(PyObject \*)"). * quoted stuff that looks like internal references but isn't (e.g. ``PyCmp_``). * changed visually balanced quotes to just use apostrophes (e.g. "'string'" instead of "`string'"). * introduced and indenting multiline chunks of code. * created one table (search for "New codecs").
2002-09-20 11:16:59 -03:00
-----
"The usual" post-release fiddling.
2001-08-22 18:36:50 -03:00
Merging 2.2a3 branch changes back into trunk
2001-09-07 15:13:44 -03:00
- If you are an adventurous person using Mac OS X you may want to look at
Mac/OSX. There is a Makefile there that will build Python as a real Mac
application, which can be used for experimenting with Carbon or Cocoa.
Discussion of this on pythonmac-sig, please.
At Guido's suggestion, here's a new C API function, PyObject_Dir(), like __builtin__.dir(). Moved the guts from bltinmodule.c to object.c.
2001-09-04 19:08:56 -03:00
C API
ReST-ification of the NEWS file. While the total number of changes are fairly large, most are caused by reformatting section and subsection headings. The changes fall into the following categories: * reformatted section and subsection headers. * escaped isolated asterisks which would be interpreted as starting bold or italic text (e.g. "void (*)(PyObject \*)"). * quoted stuff that looks like internal references but isn't (e.g. ``PyCmp_``). * changed visually balanced quotes to just use apostrophes (e.g. "'string'" instead of "`string'"). * introduced and indenting multiline chunks of code. * created one table (search for "New codecs").
2002-09-20 11:16:59 -03:00
-----
At Guido's suggestion, here's a new C API function, PyObject_Dir(), like __builtin__.dir(). Moved the guts from bltinmodule.c to object.c.
2001-09-04 19:08:56 -03:00
- New function PyObject_Dir(obj), like Python __builtin__.dir(obj).
Add a new function imp.lock_held(), and use it to skip test_threaded_import when that test is doomed to deadlock.
2001-08-30 02:16:13 -03:00
Raise OverflowError when appropriate on long->float conversion. Most of the fiddling is simply due to that no caller of PyLong_AsDouble ever checked for failure (so that's fixing old bugs). PyLong_AsDouble is much faster for big inputs now too, but that's more of a happy consequence than a design goal.
2001-09-04 02:14:19 -03:00
- Note that PyLong_AsDouble can fail! This has always been true, but no
callers checked for it. It's more likely to fail now, because overflow
fix a couple nits with my use of ReST
2002-09-30 12:23:01 -03:00
errors are properly detected now. The proper way to check::
Raise OverflowError when appropriate on long->float conversion. Most of the fiddling is simply due to that no caller of PyLong_AsDouble ever checked for failure (so that's fixing old bugs). PyLong_AsDouble is much faster for big inputs now too, but that's more of a happy consequence than a design goal.
2001-09-04 02:14:19 -03:00
ReST-ification of the NEWS file. While the total number of changes are fairly large, most are caused by reformatting section and subsection headings. The changes fall into the following categories: * reformatted section and subsection headers. * escaped isolated asterisks which would be interpreted as starting bold or italic text (e.g. "void (*)(PyObject \*)"). * quoted stuff that looks like internal references but isn't (e.g. ``PyCmp_``). * changed visually balanced quotes to just use apostrophes (e.g. "'string'" instead of "`string'"). * introduced and indenting multiline chunks of code. * created one table (search for "New codecs").
2002-09-20 11:16:59 -03:00
double x = PyLong_AsDouble(some_long_object);
if (x == -1.0 && PyErr_Occurred()) {
Add newsitem for the two new unittest methods. Also, made some whitespace cleanup.
2002-12-29 16:14:11 -04:00
/* The conversion failed. */
ReST-ification of the NEWS file. While the total number of changes are fairly large, most are caused by reformatting section and subsection headings. The changes fall into the following categories: * reformatted section and subsection headers. * escaped isolated asterisks which would be interpreted as starting bold or italic text (e.g. "void (*)(PyObject \*)"). * quoted stuff that looks like internal references but isn't (e.g. ``PyCmp_``). * changed visually balanced quotes to just use apostrophes (e.g. "'string'" instead of "`string'"). * introduced and indenting multiline chunks of code. * created one table (search for "New codecs").
2002-09-20 11:16:59 -03:00
}
Raise OverflowError when appropriate on long->float conversion. Most of the fiddling is simply due to that no caller of PyLong_AsDouble ever checked for failure (so that's fixing old bugs). PyLong_AsDouble is much faster for big inputs now too, but that's more of a happy consequence than a design goal.
2001-09-04 02:14:19 -03:00
Start items w/ "-" instead of "+" (consistency w/ earlier versions). Stephen Hansen reported via email that he didn't finish the port to Borland C, so remove the old item saying it worked and add a new item saying what I know; I've asked Stephen for more details.
2001-09-02 00:40:59 -03:00
- The GC API has been changed. Extensions that use the old API will still
Add news about GC API change. Explain how to upgrade extension modules.
2001-08-30 12:38:01 -03:00
compile but will not participate in GC. To upgrade an extension
module:
- rename Py_TPFLAGS_GC to PyTPFLAGS_HAVE_GC
SF patch #455966: Allow leading 0 in float/imag literals. Consequences for Jython still unknown (but raised on Jython-Dev).
2001-08-30 17:51:59 -03:00
Add news about GC API change. Explain how to upgrade extension modules.
2001-08-30 12:38:01 -03:00
- use PyObject_GC_New or PyObject_GC_NewVar to allocate objects and
PyObject_GC_Del to deallocate them
SF patch #455966: Allow leading 0 in float/imag literals. Consequences for Jython still unknown (but raised on Jython-Dev).
2001-08-30 17:51:59 -03:00
Add news about GC API change. Explain how to upgrade extension modules.
2001-08-30 12:38:01 -03:00
- rename PyObject_GC_Init to PyObject_GC_Track and PyObject_GC_Fini
to PyObject_GC_UnTrack
SF patch #455966: Allow leading 0 in float/imag literals. Consequences for Jython still unknown (but raised on Jython-Dev).
2001-08-30 17:51:59 -03:00
Add news about GC API change. Explain how to upgrade extension modules.
2001-08-30 12:38:01 -03:00
- remove PyGC_HEAD_SIZE from object size calculations
- remove calls to PyObject_AS_GC and PyObject_FROM_GC
Start items w/ "-" instead of "+" (consistency w/ earlier versions). Stephen Hansen reported via email that he didn't finish the port to Borland C, so remove the old item saying it worked and add a new item saying what I know; I've asked Stephen for more details.
2001-09-02 00:40:59 -03:00
- Two new functions: PyString_FromFormat() and PyString_FromFormatV().
Add various and sundry news items -- most mine, one Barry's, one Michael Hudson's.
2001-08-31 15:31:35 -03:00
These can be used safely to construct string objects from a
sprintf-style format string (similar to the format string supported
by PyErr_Format()).
Add a new function imp.lock_held(), and use it to skip test_threaded_import when that test is doomed to deadlock.
2001-08-30 02:16:13 -03:00
"The usual" post-release fiddling.
2001-08-22 18:36:50 -03:00
New platforms
ReST-ification of the NEWS file. While the total number of changes are fairly large, most are caused by reformatting section and subsection headings. The changes fall into the following categories: * reformatted section and subsection headers. * escaped isolated asterisks which would be interpreted as starting bold or italic text (e.g. "void (*)(PyObject \*)"). * quoted stuff that looks like internal references but isn't (e.g. ``PyCmp_``). * changed visually balanced quotes to just use apostrophes (e.g. "'string'" instead of "`string'"). * introduced and indenting multiline chunks of code. * created one table (search for "New codecs").
2002-09-20 11:16:59 -03:00
-------------
"The usual" post-release fiddling.
2001-08-22 18:36:50 -03:00
Clarify the Borland situation, based on email from Stephen.
2001-09-02 20:01:43 -03:00
- Stephen Hansen contributed patches sufficient to get a clean compile
under Borland C (Windows), but he reports problems running it and ran
out of time to complete the port. Volunteers? Expect a MemoryError
when importing the types module; this is probably shallow, and
causing later failures too.
Start items w/ "-" instead of "+" (consistency w/ earlier versions). Stephen Hansen reported via email that he didn't finish the port to Borland C, so remove the old item saying it worked and add a new item saying what I know; I've asked Stephen for more details.
2001-09-02 00:40:59 -03:00
"The usual" post-release fiddling.
2001-08-22 18:36:50 -03:00
Tests
ReST-ification of the NEWS file. While the total number of changes are fairly large, most are caused by reformatting section and subsection headings. The changes fall into the following categories: * reformatted section and subsection headers. * escaped isolated asterisks which would be interpreted as starting bold or italic text (e.g. "void (*)(PyObject \*)"). * quoted stuff that looks like internal references but isn't (e.g. ``PyCmp_``). * changed visually balanced quotes to just use apostrophes (e.g. "'string'" instead of "`string'"). * introduced and indenting multiline chunks of code. * created one table (search for "New codecs").
2002-09-20 11:16:59 -03:00
-----
"The usual" post-release fiddling.
2001-08-22 18:36:50 -03:00
Windows
ReST-ification of the NEWS file. While the total number of changes are fairly large, most are caused by reformatting section and subsection headings. The changes fall into the following categories: * reformatted section and subsection headers. * escaped isolated asterisks which would be interpreted as starting bold or italic text (e.g. "void (*)(PyObject \*)"). * quoted stuff that looks like internal references but isn't (e.g. ``PyCmp_``). * changed visually balanced quotes to just use apostrophes (e.g. "'string'" instead of "`string'"). * introduced and indenting multiline chunks of code. * created one table (search for "New codecs").
2002-09-20 11:16:59 -03:00
-------
"The usual" post-release fiddling.
2001-08-22 18:36:50 -03:00
Enable large file support on Win32 systems. Curious: the MS docs say stati64 etc are supported even on Win95, but Win95 doesn't support a filesystem that allows partitions > 2 Gb. test_largefile: This was opening its test file in text mode. I have no idea how that worked under Win64, but it sure needs binary mode on Win98. BTW, on Win98 test_largefile runs quickly (under a second).
2001-09-05 21:32:15 -03:00
- Large file support is now enabled on Win32 platforms as well as on
Win64. This means that, for example, you can use f.tell() and f.seek()
to manipulate files larger than 2 gigabytes (provided you have enough
disk space, and are using a Windows filesystem that supports large
Add info about Windows filesystem limits.
2001-09-11 20:18:51 -03:00
partitions). Windows filesystem limits: FAT has a 2GB (gigabyte)
filesize limit, and large file support makes no difference there.
FAT32's limit is 4GB, and files >= 2GB are easier to use from Python now.
NTFS has no practical limit on file size, and files of any size can be
used from Python now.
Enable large file support on Win32 systems. Curious: the MS docs say stati64 etc are supported even on Win95, but Win95 doesn't support a filesystem that allows partitions > 2 Gb. test_largefile: This was opening its test file in text mode. I have no idea how that worked under Win64, but it sure needs binary mode on Win98. BTW, on Win98 test_largefile runs quickly (under a second).
2001-09-05 21:32:15 -03:00
Start items w/ "-" instead of "+" (consistency w/ earlier versions). Stephen Hansen reported via email that he didn't finish the port to Borland C, so remove the old item saying it worked and add a new item saying what I know; I've asked Stephen for more details.
2001-09-02 00:40:59 -03:00
- The w9xpopen hack is now used on Windows NT and 2000 too when COMPSPEC
SF patch [ #455137 ] Makes popen work with COMMAND.COM on WNT, from Brian Quinlan.
2001-08-27 03:37:48 -03:00
points to command.com (patch from Brian Quinlan).
"The usual" post-release fiddling.
2001-08-22 18:36:50 -03:00
Get started on 2.2a2 NEWS.
2001-07-20 23:31:40 -03:00
What's New in Python 2.2a2?
===========================
ReST-ification of the NEWS file. While the total number of changes are fairly large, most are caused by reformatting section and subsection headings. The changes fall into the following categories: * reformatted section and subsection headers. * escaped isolated asterisks which would be interpreted as starting bold or italic text (e.g. "void (*)(PyObject \*)"). * quoted stuff that looks like internal references but isn't (e.g. ``PyCmp_``). * changed visually balanced quotes to just use apostrophes (e.g. "'string'" instead of "`string'"). * introduced and indenting multiline chunks of code. * created one table (search for "New codecs").
2002-09-20 11:16:59 -03:00
*Release Date: 22-Aug-2001*
Patch #445762: Support --disable-unicode - Do not compile unicodeobject, unicodectype, and unicodedata if Unicode is disabled - check for Py_USING_UNICODE in all places that use Unicode functions - disables unicode literals, and the builtin functions - add the types.StringTypes list - remove Unicode literals from most tests.
2001-08-17 15:39:25 -03:00
Build
ReST-ification of the NEWS file. While the total number of changes are fairly large, most are caused by reformatting section and subsection headings. The changes fall into the following categories: * reformatted section and subsection headers. * escaped isolated asterisks which would be interpreted as starting bold or italic text (e.g. "void (*)(PyObject \*)"). * quoted stuff that looks like internal references but isn't (e.g. ``PyCmp_``). * changed visually balanced quotes to just use apostrophes (e.g. "'string'" instead of "`string'"). * introduced and indenting multiline chunks of code. * created one table (search for "New codecs").
2002-09-20 11:16:59 -03:00
-----
Patch #445762: Support --disable-unicode - Do not compile unicodeobject, unicodectype, and unicodedata if Unicode is disabled - check for Py_USING_UNICODE in all places that use Unicode functions - disables unicode literals, and the builtin functions - add the types.StringTypes list - remove Unicode literals from most tests.
2001-08-17 15:39:25 -03:00
Add an item about Tim's new installer. This didn't make it into the 2.2a2 release, but it's still worth mentioning.
2001-08-22 17:26:56 -03:00
- Tim Peters developed a brand new Windows installer using Wise 8.1,
generously donated to us by Wise Solutions.
Patch #445762: Support --disable-unicode - Do not compile unicodeobject, unicodectype, and unicodedata if Unicode is disabled - check for Py_USING_UNICODE in all places that use Unicode functions - disables unicode literals, and the builtin functions - add the types.StringTypes list - remove Unicode literals from most tests.
2001-08-17 15:39:25 -03:00
- configure supports a new option --enable-unicode, with the values
ucs2 and ucs4 (new in 2.2a1). With --disable-unicode, the Unicode
type and supporting code is completely removed from the interpreter.
More NEWS for 2.2a2.
2001-08-22 01:08:41 -03:00
Added a note about --enable-framework on Mac OS X.
2001-08-21 16:28:20 -03:00
- A new configure option --enable-framework builds a Mac OS X framework,
which "make frameworkinstall" will install. This provides a starting
point for more mac-like functionality, join pythonmac-sig@python.org
if you are interested in helping.
Patch #445762: Support --disable-unicode - Do not compile unicodeobject, unicodectype, and unicodedata if Unicode is disabled - check for Py_USING_UNICODE in all places that use Unicode functions - disables unicode literals, and the builtin functions - add the types.StringTypes list - remove Unicode literals from most tests.
2001-08-17 15:39:25 -03:00
More NEWS for 2.2a2.
2001-08-22 01:08:41 -03:00
- The NeXT platform is no longer supported.
ReST-ification of the NEWS file. While the total number of changes are fairly large, most are caused by reformatting section and subsection headings. The changes fall into the following categories: * reformatted section and subsection headers. * escaped isolated asterisks which would be interpreted as starting bold or italic text (e.g. "void (*)(PyObject \*)"). * quoted stuff that looks like internal references but isn't (e.g. ``PyCmp_``). * changed visually balanced quotes to just use apostrophes (e.g. "'string'" instead of "`string'"). * introduced and indenting multiline chunks of code. * created one table (search for "New codecs").
2002-09-20 11:16:59 -03:00
- The 'new' module is now statically linked.
More NEWS for 2.2a2.
2001-08-22 01:08:41 -03:00
Add blurb about cleanfuture.py. Fix misspelling in an older item.
2001-08-15 03:06:44 -03:00
Tools
ReST-ification of the NEWS file. While the total number of changes are fairly large, most are caused by reformatting section and subsection headings. The changes fall into the following categories: * reformatted section and subsection headers. * escaped isolated asterisks which would be interpreted as starting bold or italic text (e.g. "void (*)(PyObject \*)"). * quoted stuff that looks like internal references but isn't (e.g. ``PyCmp_``). * changed visually balanced quotes to just use apostrophes (e.g. "'string'" instead of "`string'"). * introduced and indenting multiline chunks of code. * created one table (search for "New codecs").
2002-09-20 11:16:59 -03:00
-----
Add blurb about cleanfuture.py. Fix misspelling in an older item.
2001-08-15 03:06:44 -03:00
- The new Tools/scripts/cleanfuture.py can be used to automatically
Fix typo
2001-08-15 12:54:56 -03:00
edit out obsolete future statements from Python source code. See
Add blurb about cleanfuture.py. Fix misspelling in an older item.
2001-08-15 03:06:44 -03:00
the module docstring for details.
Get started on 2.2a2 NEWS.
2001-07-20 23:31:40 -03:00
Tests
ReST-ification of the NEWS file. While the total number of changes are fairly large, most are caused by reformatting section and subsection headings. The changes fall into the following categories: * reformatted section and subsection headers. * escaped isolated asterisks which would be interpreted as starting bold or italic text (e.g. "void (*)(PyObject \*)"). * quoted stuff that looks like internal references but isn't (e.g. ``PyCmp_``). * changed visually balanced quotes to just use apostrophes (e.g. "'string'" instead of "`string'"). * introduced and indenting multiline chunks of code. * created one table (search for "New codecs").
2002-09-20 11:16:59 -03:00
-----
Get started on 2.2a2 NEWS.
2001-07-20 23:31:40 -03:00
SF patch #445412 extract ndiff functionality to difflib, from David Goodger.
2001-08-12 19:25:01 -03:00
- regrtest.py now knows which tests are expected to be skipped on some
More NEWS for 2.2a2.
2001-08-22 01:08:41 -03:00
platforms, allowing to give clearer test result output. regrtest
also has optional --use/-u switch to run normally disabled tests
which require network access or consume significant disk resources.
SF patch #445412 extract ndiff functionality to difflib, from David Goodger.
2001-08-12 19:25:01 -03:00
Get started on 2.2a2 NEWS.
2001-07-20 23:31:40 -03:00
- Several new tests in the standard test suite, with special thanks to
Nick Mathewson.
Core
ReST-ification of the NEWS file. While the total number of changes are fairly large, most are caused by reformatting section and subsection headings. The changes fall into the following categories: * reformatted section and subsection headers. * escaped isolated asterisks which would be interpreted as starting bold or italic text (e.g. "void (*)(PyObject \*)"). * quoted stuff that looks like internal references but isn't (e.g. ``PyCmp_``). * changed visually balanced quotes to just use apostrophes (e.g. "'string'" instead of "`string'"). * introduced and indenting multiline chunks of code. * created one table (search for "New codecs").
2002-09-20 11:16:59 -03:00
----
Get started on 2.2a2 NEWS.
2001-07-20 23:31:40 -03:00
More NEWS for 2.2a2.
2001-08-22 01:08:41 -03:00
- The floor division operator // has been added as outlined in PEP
238. The / operator still provides classic division (and will until
Python 3.0) unless "from __future__ import division" is included, in
which case the / operator will provide true division. The operator
module provides truediv() and floordiv() functions. Augmented
assignment variants are included, as are the equivalent overloadable
methods and C API methods. See the PEP for a full discussion:
<http://python.sf.net/peps/pep-0238.html>
A fiddled version of the rest of Michael Hudson's SF patch #449043 supporting __future__ in simulated shells which implements PEP 264.
2001-08-17 19:11:27 -03:00
- Future statements are now effective in simulated interactive shells
(like IDLE). This should "just work" by magic, but read Michael
Hudson's "Future statements in simulated shells" PEP 264 for full
details: <http://python.sf.net/peps/pep-0264.html>.
Add note on type/class unification.
2001-08-17 18:21:04 -03:00
- The type/class unification (PEP 252-253) was integrated into the
trunk and is not so tentative any more (the exact specification of
some features is still tentative). A lot of work has done on fixing
bugs and adding robustness and features (performance still has to
come a long way).
Add news items.
2001-07-31 11:24:31 -03:00
- Warnings about a mismatch in the Python API during extension import
now use the Python warning framework (which makes it possible to
write filters for these warnings).
Document the new semantics for setting and deleting a function's __dict__ attribute. Deleting it, or setting it to a non-dictionary result in a TypeError. Note that getting it the first time magically initializes it to an empty dict so that func.__dict__ will always appear to be a dictionary (never None). Closes SF bug #446645.
2001-08-14 15:35:02 -03:00
- A function's __dict__ (aka func_dict) will now always be a
dictionary. It used to be possible to delete it or set it to None,
but now both actions raise TypeErrors. It is still legal to set it
to a dictionary object. Getting func.__dict__ before any attributes
have been assigned now returns an empty dictionary instead of None.
Describe -E (which was added to 2.2a2).
2001-09-05 15:43:35 -03:00
- A new command line option, -E, was added which disables the use of
all environment variables, or at least those that are specifically
significant to Python. Usually those have a name starting with
"PYTHON". This was used to fix a problem where the tests fail if
the user happens to have PYTHONHOME or PYTHONPATH pointing to an
older distribution.
Moved the news items about C API topics down to the C API section.
2001-07-31 11:42:42 -03:00
Library
ReST-ification of the NEWS file. While the total number of changes are fairly large, most are caused by reformatting section and subsection headings. The changes fall into the following categories: * reformatted section and subsection headers. * escaped isolated asterisks which would be interpreted as starting bold or italic text (e.g. "void (*)(PyObject \*)"). * quoted stuff that looks like internal references but isn't (e.g. ``PyCmp_``). * changed visually balanced quotes to just use apostrophes (e.g. "'string'" instead of "`string'"). * introduced and indenting multiline chunks of code. * created one table (search for "New codecs").
2002-09-20 11:16:59 -03:00
-------
Moved the news items about C API topics down to the C API section.
2001-07-31 11:42:42 -03:00
SF patch #445412 extract ndiff functionality to difflib, from David Goodger.
2001-08-12 19:25:01 -03:00
- New class Differ and new functions ndiff() and restore() in difflib.py.
These package the algorithms used by the popular Tools/scripts/ndiff.py,
Add blurb about cleanfuture.py. Fix misspelling in an older item.
2001-08-15 03:06:44 -03:00
for programmatic reuse.
SF patch #445412 extract ndiff functionality to difflib, from David Goodger.
2001-08-12 19:25:01 -03:00
Moved the news items about C API topics down to the C API section.
2001-07-31 11:42:42 -03:00
- New function xml.sax.saxutils.quoteattr(): Quote an XML attribute
value using the minimal quoting required for the value; more
reliable than using xml.sax.saxutils.escape() for attribute values.
- Readline completion support for cmd.Cmd was added.
More NEWS for 2.2a2.
2001-08-22 01:08:41 -03:00
- Calling os.tempnam() or os.tmpnam() generate RuntimeWarnings.
- Added function threading.BoundedSemaphore()
- Added Ka-Ping Yee's cgitb.py module.
ReST-ification of the NEWS file. While the total number of changes are fairly large, most are caused by reformatting section and subsection headings. The changes fall into the following categories: * reformatted section and subsection headers. * escaped isolated asterisks which would be interpreted as starting bold or italic text (e.g. "void (*)(PyObject \*)"). * quoted stuff that looks like internal references but isn't (e.g. ``PyCmp_``). * changed visually balanced quotes to just use apostrophes (e.g. "'string'" instead of "`string'"). * introduced and indenting multiline chunks of code. * created one table (search for "New codecs").
2002-09-20 11:16:59 -03:00
- The 'new' module now exposes the CO_xxx flags.
More NEWS for 2.2a2.
2001-08-22 01:08:41 -03:00
Rename get_referents to get_referrers. Fixes #483815.
2001-11-24 05:24:51 -04:00
- The gc module offers the get_referents function.
Moved the news items about C API topics down to the C API section.
2001-07-31 11:42:42 -03:00
New platforms
ReST-ification of the NEWS file. While the total number of changes are fairly large, most are caused by reformatting section and subsection headings. The changes fall into the following categories: * reformatted section and subsection headers. * escaped isolated asterisks which would be interpreted as starting bold or italic text (e.g. "void (*)(PyObject \*)"). * quoted stuff that looks like internal references but isn't (e.g. ``PyCmp_``). * changed visually balanced quotes to just use apostrophes (e.g. "'string'" instead of "`string'"). * introduced and indenting multiline chunks of code. * created one table (search for "New codecs").
2002-09-20 11:16:59 -03:00
-------------
Moved the news items about C API topics down to the C API section.
2001-07-31 11:42:42 -03:00
C API
ReST-ification of the NEWS file. While the total number of changes are fairly large, most are caused by reformatting section and subsection headings. The changes fall into the following categories: * reformatted section and subsection headers. * escaped isolated asterisks which would be interpreted as starting bold or italic text (e.g. "void (*)(PyObject \*)"). * quoted stuff that looks like internal references but isn't (e.g. ``PyCmp_``). * changed visually balanced quotes to just use apostrophes (e.g. "'string'" instead of "`string'"). * introduced and indenting multiline chunks of code. * created one table (search for "New codecs").
2002-09-20 11:16:59 -03:00
-----
Moved the news items about C API topics down to the C API section.
2001-07-31 11:42:42 -03:00
Add news items.
2001-07-31 11:24:31 -03:00
- Two new APIs PyOS_snprintf() and PyOS_vsnprintf() were added
which provide a cross-platform implementations for the
relatively new snprintf()/vsnprintf() C lib APIs. In contrast to
the standard sprintf() and vsprintf() C lib APIs, these versions
apply bounds checking on the used buffer which enhances protection
against buffer overruns.
Add news item about Unicode API name mangling.
2001-07-31 11:37:40 -03:00
- Unicode APIs now use name mangling to assure that mixing interpreters
Derived from SF patch #446899 Permit import of .pyw under Windows, from David Bolen.
2001-08-04 05:12:36 -03:00
and extensions using different Unicode widths is rendered next to
impossible. Trying to import an incompatible Unicode-aware extension
Add news item about Unicode API name mangling.
2001-07-31 11:37:40 -03:00
will result in an ImportError. Unicode extensions writers must make
sure to check the Unicode width compatibility in their extensions by
using at least one of the mangled Unicode APIs in the extension.
Patch #445762: Support --disable-unicode - Do not compile unicodeobject, unicodectype, and unicodedata if Unicode is disabled - check for Py_USING_UNICODE in all places that use Unicode functions - disables unicode literals, and the builtin functions - add the types.StringTypes list - remove Unicode literals from most tests.
2001-08-17 15:39:25 -03:00
- Two new flags METH_NOARGS and METH_O are available in method definition
tables to simplify implementation of methods with no arguments and a
single untyped argument. Calling such methods is more efficient than
calling corresponding METH_VARARGS methods. METH_OLDARGS is now
deprecated.
Derived from SF patch #446899 Permit import of .pyw under Windows, from David Bolen.
2001-08-04 05:12:36 -03:00
Windows
ReST-ification of the NEWS file. While the total number of changes are fairly large, most are caused by reformatting section and subsection headings. The changes fall into the following categories: * reformatted section and subsection headers. * escaped isolated asterisks which would be interpreted as starting bold or italic text (e.g. "void (*)(PyObject \*)"). * quoted stuff that looks like internal references but isn't (e.g. ``PyCmp_``). * changed visually balanced quotes to just use apostrophes (e.g. "'string'" instead of "`string'"). * introduced and indenting multiline chunks of code. * created one table (search for "New codecs").
2002-09-20 11:16:59 -03:00
-------
Derived from SF patch #446899 Permit import of .pyw under Windows, from David Bolen.
2001-08-04 05:12:36 -03:00
- "import module" now compiles module.pyw if it exists and nothing else
relevant is found.
Get started on 2.2a2 NEWS.
2001-07-20 23:31:40 -03:00
- Add news about generators. - Change header to 2.2a1. - Add separator between 2.2 and 2.1 news.
2001-07-17 14:22:32 -03:00
What's New in Python 2.2a1?
Generalize list(seq) to work with iterators. This also generalizes list() to no longer insist that len(seq) be defined. NEEDS DOC CHANGES. This is meant to be a model for how other functions of this ilk (max, filter, etc) can be generalized similarly. Feel encouraged to grab your favorite and convert it! Note some cute consequences: list(file) == file.readlines() == list(file.xreadlines()) list(dict) == dict.keys() list(dict.iteritems()) = dict.items() list(xrange(i, j, k)) == range(i, j, k)
2001-05-01 17:45:31 -03:00
===========================
ReST-ification of the NEWS file. While the total number of changes are fairly large, most are caused by reformatting section and subsection headings. The changes fall into the following categories: * reformatted section and subsection headers. * escaped isolated asterisks which would be interpreted as starting bold or italic text (e.g. "void (*)(PyObject \*)"). * quoted stuff that looks like internal references but isn't (e.g. ``PyCmp_``). * changed visually balanced quotes to just use apostrophes (e.g. "'string'" instead of "`string'"). * introduced and indenting multiline chunks of code. * created one table (search for "New codecs").
2002-09-20 11:16:59 -03:00
*Release date: 18-Jul-2001*
Generalize list(seq) to work with iterators. This also generalizes list() to no longer insist that len(seq) be defined. NEEDS DOC CHANGES. This is meant to be a model for how other functions of this ilk (max, filter, etc) can be generalized similarly. Feel encouraged to grab your favorite and convert it! Note some cute consequences: list(file) == file.readlines() == list(file.xreadlines()) list(dict) == dict.keys() list(dict.iteritems()) = dict.items() list(xrange(i, j, k)) == range(i, j, k)
2001-05-01 17:45:31 -03:00
Core
ReST-ification of the NEWS file. While the total number of changes are fairly large, most are caused by reformatting section and subsection headings. The changes fall into the following categories: * reformatted section and subsection headers. * escaped isolated asterisks which would be interpreted as starting bold or italic text (e.g. "void (*)(PyObject \*)"). * quoted stuff that looks like internal references but isn't (e.g. ``PyCmp_``). * changed visually balanced quotes to just use apostrophes (e.g. "'string'" instead of "`string'"). * introduced and indenting multiline chunks of code. * created one table (search for "New codecs").
2002-09-20 11:16:59 -03:00
----
SF bug[ #423781: pprint.isrecursive() broken.
2001-05-14 04:05:58 -03:00
Merge of descr-branch back into trunk.
2001-08-02 01:15:00 -03:00
- TENTATIVELY, a large amount of code implementing much of what's
described in PEP 252 (Making Types Look More Like Classes) and PEP
253 (Subtyping Built-in Types) was added. This will be released
with Python 2.2a1. Documentation will be provided separately
through http://www.python.org/2.2/. The purpose of releasing this
with Python 2.2a1 is to test backwards compatibility. It is
possible, though not likely, that a decision is made not to release
this code as part of 2.2 final, if any serious backwards
Fix spelling errors and note the addition of operator.pow()
2002-08-19 11:25:03 -03:00
incompatibilities are found during alpha testing that cannot be
Merge of descr-branch back into trunk.
2001-08-02 01:15:00 -03:00
repaired.
- Add news about generators. - Change header to 2.2a1. - Add separator between 2.2 and 2.1 news.
2001-07-17 14:22:32 -03:00
- Generators were added; this is a new way to create an iterator (see
Typo repair.
2001-07-17 15:48:00 -03:00
below) using what looks like a simple function containing one or
- Add news about generators. - Change header to 2.2a1. - Add separator between 2.2 and 2.1 news.
2001-07-17 14:22:32 -03:00
more 'yield' statements. See PEP 255. Since this adds a new
keyword to the language, this feature must be enabled by including a
future statement: "from __future__ import generators" (see PEP 236).
Generators will become a standard feature in a future release
(probably 2.3). Without this future statement, 'yield' remains an
ordinary identifier, but a warning is issued each time it is used.
(These warnings currently don't conform to the warnings framework of
PEP 230; we intend to fix this in 2.2a2.)
Added NEWS item for the UTF-16 change.
2001-05-22 05:58:23 -03:00
- The UTF-16 codec was modified to be more RFC compliant. It will now
only remove BOM characters at the start of the string and then
only if running in native mode (UTF-16-LE and -BE won't remove a
leading BMO character).
Add NEWS item for new string methods.
2001-05-15 15:38:45 -03:00
- Strings now have a new method .decode() to complement the already
existing .encode() method. These two methods provide direct access
to the corresponding decoders and encoders of the registered codecs.
To enhance the usability of the .encode() method, the special
casing of Unicode object return values was dropped (Unicode objects
were auto-magically converted to string using the default encoding).
New collision resolution scheme: no polynomials, simpler, faster, less code, less memory. Tests have uncovered no drawbacks. Christian and Vladimir are the other two people who have burned many brain cells on the dict code in recent years, and they like the approach too, so I'm checking it in without further ado.
2001-06-02 02:27:19 -03:00
Add NEWS item for new string methods.
2001-05-15 15:38:45 -03:00
Both methods will now return whatever the codec in charge of the
requested encoding returns as object, e.g. Unicode codecs will
return Unicode objects when decoding is requested ("<22><><EFBFBD>".decode("latin-1")
will return u"<22><><EFBFBD>"). This enables codec writer to create codecs
for various simple to use conversions.
New codecs were added to demonstrate these new features (the .encode()
and .decode() columns indicate the type of the returned objects):
ReST-ification of the NEWS file. While the total number of changes are fairly large, most are caused by reformatting section and subsection headings. The changes fall into the following categories: * reformatted section and subsection headers. * escaped isolated asterisks which would be interpreted as starting bold or italic text (e.g. "void (*)(PyObject \*)"). * quoted stuff that looks like internal references but isn't (e.g. ``PyCmp_``). * changed visually balanced quotes to just use apostrophes (e.g. "'string'" instead of "`string'"). * introduced and indenting multiline chunks of code. * created one table (search for "New codecs").
2002-09-20 11:16:59 -03:00
+---------+-----------+-----------+-----------------------------+
|Name | .encode() | .decode() | Description |
+=========+===========+===========+=============================+
|uu | string | string | UU codec (e.g. for email) |
+---------+-----------+-----------+-----------------------------+
|base64 | string | string | base64 codec |
+---------+-----------+-----------+-----------------------------+
|quopri | string | string | quoted-printable codec |
+---------+-----------+-----------+-----------------------------+
|zlib | string | string | zlib compression |
+---------+-----------+-----------+-----------------------------+
|hex | string | string | 2-byte hex codec |
+---------+-----------+-----------+-----------------------------+
|rot-13 | string | Unicode | ROT-13 Unicode charmap codec|
+---------+-----------+-----------+-----------------------------+
Add NEWS item for new string methods.
2001-05-15 15:38:45 -03:00
Add mention of the default file system encoding for Windows.
2001-05-14 00:09:36 -03:00
- Some operating systems now support the concept of a default Unicode
encoding for file system operations. Notably, Windows supports 'mbcs'
as the default. The Macintosh will also adopt this concept in the medium
Fix a typo, consistently spell ASCII in all caps, and insert blank lines between paragraphs in Mark Hammond's news item about the default encoding in posixmodule. Resist the temptation to reflow paragraphs.
2001-05-14 10:53:38 -03:00
term, although the default encoding for that platform will be other than
Add mention of the default file system encoding for Windows.
2001-05-14 00:09:36 -03:00
'mbcs'.
Fix a typo, consistently spell ASCII in all caps, and insert blank lines between paragraphs in Mark Hammond's news item about the default encoding in posixmodule. Resist the temptation to reflow paragraphs.
2001-05-14 10:53:38 -03:00
On operating system that support non-ASCII filenames, it is common for
Add mention of the default file system encoding for Windows.
2001-05-14 00:09:36 -03:00
functions that return filenames (such as os.listdir()) to return Python
string objects pre-encoded using the default file system encoding for
the platform. As this encoding is likely to be different from Python's
default encoding, converting this name to a Unicode object before passing
it back to the Operating System would result in a Unicode error, as Python
SF bug[ #423781: pprint.isrecursive() broken.
2001-05-14 04:05:58 -03:00
would attempt to use its default encoding (generally ASCII) rather than
the default encoding for the file system.
Fix a typo, consistently spell ASCII in all caps, and insert blank lines between paragraphs in Mark Hammond's news item about the default encoding in posixmodule. Resist the temptation to reflow paragraphs.
2001-05-14 10:53:38 -03:00
SF bug[ #423781: pprint.isrecursive() broken.
2001-05-14 04:05:58 -03:00
In general, this change simply removes surprises when working with
Unicode and the file system, making these operations work as you expect,
increasing the transparency of Unicode objects in this context.
Add mention of the default file system encoding for Windows.
2001-05-14 00:09:36 -03:00
See [????] for more details, including examples.
Generalize list(seq) to work with iterators. This also generalizes list() to no longer insist that len(seq) be defined. NEEDS DOC CHANGES. This is meant to be a model for how other functions of this ilk (max, filter, etc) can be generalized similarly. Feel encouraged to grab your favorite and convert it! Note some cute consequences: list(file) == file.readlines() == list(file.xreadlines()) list(dict) == dict.keys() list(dict.iteritems()) = dict.items() list(xrange(i, j, k)) == range(i, j, k)
2001-05-01 17:45:31 -03:00
Blurb about the increased precision of float literals in .pyc/.pyo files.
2001-05-08 12:43:37 -03:00
- Float (and complex) literals in source code were evaluated to full
precision only when running from a .py file; the same code loaded from a
.pyc (or .pyo) file could suffer numeric differences starting at about the
12th significant decimal digit. For example, on a machine with IEEE-754
floating arithmetic,
x = 9007199254740992.0
print long(x)
printed 9007199254740992 if run directly from .py, but 9007199254740000
if from a compiled (.pyc or .pyo) file. This was due to marshal using
str(float) instead of repr(float) when building code objects. marshal
now uses repr(float) instead, which should reproduce floats to full
machine precision (assuming the platform C float<->string I/O conversion
functions are of good quality).
This may cause floating-point results to change in some cases, and
usually for the better, but may also cause numerically unstable
algorithms to break.
Get rid of the superstitious "~" in dict hashing's "i = (~hash) & mask". The comment following used to say: /* We use ~hash instead of hash, as degenerate hash functions, such as for ints <sigh>, can have lots of leading zeros. It's not really a performance risk, but better safe than sorry. 12-Dec-00 tim: so ~hash produces lots of leading ones instead -- what's the gain? */ That is, there was never a good reason for doing it. And to the contrary, as explained on Python-Dev last December, it tended to make the *sum* (i + incr) & mask (which is the first table index examined in case of collison) the same "too often" across distinct hashes. Changing to the simpler "i = hash & mask" reduced the number of string-dict collisions (== # number of times we go around the lookup for-loop) from about 6 million to 5 million during a full run of the test suite (these are approximate because the test suite does some random stuff from run to run). The number of collisions in non-string dicts also decreased, but not as dramatically. Note that this may, for a given dict, change the order (wrt previous releases) of entries exposed by .keys(), .values() and .items(). A number of std tests suffered bogus failures as a result. For dicts keyed by small ints, or (less so) by characters, the order is much more likely to be in increasing order of key now; e.g., >>> d = {} >>> for i in range(10): ... d[i] = i ... >>> d {0: 0, 1: 1, 2: 2, 3: 3, 4: 4, 5: 5, 6: 6, 7: 7, 8: 8, 9: 9} >>> Unfortunately. people may latch on to that in small examples and draw a bogus conclusion. test_support.py Moved test_extcall's sortdict() into test_support, made it stronger, and imported sortdict into other std tests that needed it. test_unicode.py Excluced cp875 from the "roundtrip over range(128)" test, because cp875 doesn't have a well-defined inverse for unicode("?", "cp875"). See Python-Dev for excruciating details. Cookie.py Chaged various output functions to sort dicts before building strings from them. test_extcall Fiddled the expected-result file. This remains sensitive to native dict ordering, because, e.g., if there are multiple errors in a keyword-arg dict (and test_extcall sets up many cases like that), the specific error Python complains about first depends on native dict ordering.
2001-05-12 21:19:31 -03:00
- The implementation of dicts suffers fewer collisions, which has speed
benefits. However, the order in which dict entries appear in dict.keys(),
dict.values() and dict.items() may differ from previous releases for a
given dict. Nothing is defined about this order, so no program should
rely on it. Nevertheless, it's easy to write test cases that rely on the
order by accident, typically because of printing the str() or repr() of a
dict to an "expected results" file. See Lib/test/test_support.py's new
sortdict(dict) function for a simple way to display a dict in sorted
order.
Added q/Q standard (x-platform 8-byte ints) mode in struct module. This completes the q/Q project. longobject.c _PyLong_AsByteArray: The original code had a gross bug: the most-significant Python digit doesn't necessarily have SHIFT significant bits, and you really need to count how many copies of the sign bit it has else spurious overflow errors result. test_struct.py: This now does exhaustive std q/Q testing at, and on both sides of, all relevant power-of-2 boundaries, both positive and negative. NEWS: Added brief dict news while I was at it.
2001-06-11 22:22:22 -03:00
- Many other small changes to dicts were made, resulting in faster
operation along the most common code paths.
Add more news about iterators.
2001-05-01 17:54:30 -03:00
- Dictionary objects now support the "in" operator: "x in dict" means
the same as dict.has_key(x).
Add an item about the extension to {}.update() to allow generic mapping objects as an argument.
2001-06-26 17:12:50 -03:00
- The update() method of dictionaries now accepts generic mapping
objects. Specifically the argument object must support the .keys()
and __getitem__() methods. This allows you to say, for example,
{}.update(UserDict())
Add more news about iterators.
2001-05-01 17:54:30 -03:00
- Iterators were added; this is a generalized way of providing values
to a for loop. See PEP 234. There's a new built-in function iter()
to return an iterator. There's a new protocol to get the next value
from an iterator using the next() method (in Python) or the
tp_iternext slot (in C). There's a new protocol to get iterators
using the __iter__() method (in Python) or the tp_iter slot (in C).
Iterating (i.e. a for loop) over a dictionary generates its keys.
Iterating over a file generates its lines.
Generalize list(seq) to work with iterators. This also generalizes list() to no longer insist that len(seq) be defined. NEEDS DOC CHANGES. This is meant to be a model for how other functions of this ilk (max, filter, etc) can be generalized similarly. Feel encouraged to grab your favorite and convert it! Note some cute consequences: list(file) == file.readlines() == list(file.xreadlines()) list(dict) == dict.keys() list(dict.iteritems()) = dict.items() list(xrange(i, j, k)) == range(i, j, k)
2001-05-01 17:45:31 -03:00
- The following functions were generalized to work nicely with iterator
fix a couple nits with my use of ReST
2002-09-30 12:23:01 -03:00
arguments::
ReST-ification of the NEWS file. While the total number of changes are fairly large, most are caused by reformatting section and subsection headings. The changes fall into the following categories: * reformatted section and subsection headers. * escaped isolated asterisks which would be interpreted as starting bold or italic text (e.g. "void (*)(PyObject \*)"). * quoted stuff that looks like internal references but isn't (e.g. ``PyCmp_``). * changed visually balanced quotes to just use apostrophes (e.g. "'string'" instead of "`string'"). * introduced and indenting multiline chunks of code. * created one table (search for "New codecs").
2002-09-20 11:16:59 -03:00
SF patch #421922: Implement rich comparison for dicts. d1 == d2 and d1 != d2 now work even if the keys and values in d1 and d2 don't support comparisons other than ==, and testing dicts for equality is faster now (especially when inequality obtains).
2001-05-08 01:38:29 -03:00
map(), filter(), reduce(), zip()
Generalize zip() to work with iterators. NEEDS DOC CHANGES. More AttributeErrors transmuted into TypeErrors, in test_b2.py, and, again, this strikes me as a good thing. This checkin completes the iterator generalization work that obviously needed to be done. Can anyone think of others that should be changed?
2001-05-05 22:05:02 -03:00
list(), tuple() (PySequence_Tuple() and PySequence_Fast() in C API)
max(), min()
Change list.extend() error msgs and NEWS to reflect that list.extend() now takes any iterable argument, not only sequences. NEEDS DOC CHANGES -- but I don't think we settled on a concise way to say this stuff.
2001-05-26 16:37:54 -03:00
join() method of strings
extend() method of lists
Generalize PySequence_Count() (operator.countOf) to work with iterators.
2001-05-05 08:33:43 -03:00
'x in y' and 'x not in y' (PySequence_Contains() in C API)
operator.countOf() (PySequence_Count() in C API)
ReST-ification of the NEWS file. While the total number of changes are fairly large, most are caused by reformatting section and subsection headings. The changes fall into the following categories: * reformatted section and subsection headers. * escaped isolated asterisks which would be interpreted as starting bold or italic text (e.g. "void (*)(PyObject \*)"). * quoted stuff that looks like internal references but isn't (e.g. ``PyCmp_``). * changed visually balanced quotes to just use apostrophes (e.g. "'string'" instead of "`string'"). * introduced and indenting multiline chunks of code. * created one table (search for "New codecs").
2002-09-20 11:16:59 -03:00
right-hand side of assignment statements with multiple targets, such as ::
Teach the UNPACK_SEQUENCE opcode how to tease an iterable object into giving up the goods. NEEDS DOC CHANGES
2001-06-20 23:49:55 -03:00
x, y, z = some_iterable_object_returning_exactly_3_values
Generalize PySequence_Count() (operator.countOf) to work with iterators.
2001-05-05 08:33:43 -03:00
Variant of patch #423262: Change module attribute get & set Allow module getattr and setattr to exploit string interning, via the previously null module object tp_getattro and tp_setattro slots. Yields a very nice speedup for things like random.random and os.path etc.
2001-05-11 18:51:48 -03:00
- Accessing module attributes is significantly faster (for example,
random.random or os.path or yourPythonModule.yourAttribute).
SF patch #421922: Implement rich comparison for dicts. d1 == d2 and d1 != d2 now work even if the keys and values in d1 and d2 don't support comparisons other than ==, and testing dicts for equality is faster now (especially when inequality obtains).
2001-05-08 01:38:29 -03:00
- Comparing dictionary objects via == and != is faster, and now works even
if the keys and values don't support comparisons other than ==.
SF bug #422121 Insecurities in dict comparison. Fixed a half dozen ways in which general dict comparison could crash Python (even cause Win98SE to reboot) in the presence of kay and/or value comparison routines that mutate the dict during dict comparison. Bugfix candidate.
2001-05-10 05:32:44 -03:00
- Comparing dictionaries in ways other than == and != is slower: there were
insecurities in the dict comparison implementation that could cause Python
to crash if the element comparison routines for the dict keys and/or
values mutated the dicts. Making the code bulletproof slowed it down.
New collision resolution scheme: no polynomials, simpler, faster, less code, less memory. Tests have uncovered no drawbacks. Christian and Vladimir are the other two people who have burned many brain cells on the dict code in recent years, and they like the approach too, so I'm checking it in without further ado.
2001-06-02 02:27:19 -03:00
- Collisions in dicts are resolved via a new approach, which can help
dramatically in bad cases. For example, looking up every key in a dict
Added q/Q standard (x-platform 8-byte ints) mode in struct module. This completes the q/Q project. longobject.c _PyLong_AsByteArray: The original code had a gross bug: the most-significant Python digit doesn't necessarily have SHIFT significant bits, and you really need to count how many copies of the sign bit it has else spurious overflow errors result. test_struct.py: This now does exhaustive std q/Q testing at, and on both sides of, all relevant power-of-2 boundaries, both positive and negative. NEWS: Added brief dict news while I was at it.
2001-06-11 22:22:22 -03:00
d with d.keys() == [i << 16 for i in range(20000)] is approximately 500x
New collision resolution scheme: no polynomials, simpler, faster, less code, less memory. Tests have uncovered no drawbacks. Christian and Vladimir are the other two people who have burned many brain cells on the dict code in recent years, and they like the approach too, so I'm checking it in without further ado.
2001-06-02 02:27:19 -03:00
faster now. Thanks to Christian Tismer for pointing out the cause and
the nature of an effective cure (last December! better late than never).
Implement an old idea of Christian Tismer's: use polynomial division instead of multiplication to generate the probe sequence. The idea is recorded in Python-Dev for Dec 2000, but that version is prone to rare infinite loops. The value is in getting *all* the bits of the hash code to participate; and, e.g., this speeds up querying every key in a dict with keys [i << 16 for i in range(20000)] by a factor of 500. Should be equally valuable in any bad case where the high-order hash bits were getting ignored. Also wrote up some of the motivations behind Python's ever-more-subtle hash table strategy.
2001-05-27 04:39:22 -03:00
Reformat decl of new _PyString_Join. Add NEWS blurb about repr() speedup.
2001-06-16 02:42:57 -03:00
- repr() is much faster for large containers (dict, list, tuple).
SF bug[ #423781: pprint.isrecursive() broken.
2001-05-14 04:05:58 -03:00
Library
ReST-ification of the NEWS file. While the total number of changes are fairly large, most are caused by reformatting section and subsection headings. The changes fall into the following categories: * reformatted section and subsection headers. * escaped isolated asterisks which would be interpreted as starting bold or italic text (e.g. "void (*)(PyObject \*)"). * quoted stuff that looks like internal references but isn't (e.g. ``PyCmp_``). * changed visually balanced quotes to just use apostrophes (e.g. "'string'" instead of "`string'"). * introduced and indenting multiline chunks of code. * created one table (search for "New codecs").
2002-09-20 11:16:59 -03:00
-------
SF bug[ #423781: pprint.isrecursive() broken.
2001-05-14 04:05:58 -03:00
Added the constants ascii_letters, ascii_lowercase, and ascii_uppercase to the string module. This was determined to be the right approach in SF bug #226706.
2001-07-20 15:38:26 -03:00
- The constants ascii_letters, ascii_lowercase. and ascii_uppercase
Fix spelling errors and note the addition of operator.pow()
2002-08-19 11:25:03 -03:00
were added to the string module. These a locale-independent
Added the constants ascii_letters, ascii_lowercase, and ascii_uppercase to the string module. This was determined to be the right approach in SF bug #226706.
2001-07-20 15:38:26 -03:00
constants, unlike letters, lowercase, and uppercase. These are now
use in appropriate locations in the standard library.
Patch #412229: Add functions sys.getdlopenflags and sys.setdlopenflags. Add dlopenflags to PyInterpreterState, and use it in dlopen calls.
2001-07-18 13:17:16 -03:00
- The flags used in dlopen calls can now be configured using
sys.setdlopenflags and queried using sys.getdlopenflags.
Add xmlrpc. (Tim & I should agree on where to add new additions: I add them at the top, Tim adds them at the bottom. I like the top better because folks who occasionally check out the NEWS file will see the latest news first.)
2001-07-12 08:54:37 -03:00
- Fredrik Lundh's xmlrpclib is now a standard library module. This
provides full client-side XML-RPC support. In addition,
Demo/xmlrpc/ contains two server frameworks (one SocketServer-based,
one asyncore-based). Thanks to Eric Raymond for the documentation.
News about xrange().
2001-07-05 11:46:25 -03:00
- The xrange() object is simplified: it no longer supports slicing,
repetition, comparisons, efficient 'in' checking, the tolist()
method, or the start, stop and step attributes. See PEP 260.
Report on fnmatch.filter.
2001-06-06 03:25:40 -03:00
- A new function fnmatch.filter to filter lists of file names was added.
- calendar.py uses month and day names based on the current locale.
2001-05-22 13:00:10 -03:00
- calendar.py uses month and day names based on the current locale.
Add warnings to the strop module, for to those functions that really *are* obsolete; three variables and the maketrans() function are not (yet) obsolete. Add a compensating warnings.filterwarnings() call to test_strop.py. Add this to the NEWS.
2001-05-14 23:14:44 -03:00
- strop is now *really* obsolete (this was announced before with 1.6),
and issues DeprecationWarning when used (except for the four items
that are still imported into string.py).
SF bug[ #423781: pprint.isrecursive() broken.
2001-05-14 04:05:58 -03:00
- Cookie.py now sorts key+value pairs by key in output strings.
- pprint.isrecursive(object) didn't correctly identify recursive objects.
Now it does.
pprint's workhorse _safe_repr() function took time quadratic in the # of elements when crunching a list, dict or tuple. Now takes linear time instead -- huge speedup for even moderately large containers, and the code is notably simpler too. Added some basic "is the output correct?" tests to test_pprint.
2001-05-14 15:39:41 -03:00
- pprint functions now much faster for large containers (tuple, list, dict).
Initial support for 'q' and 'Q' struct format codes: for now, only in native mode, and only when config #defines HAVE_LONG_LONG. Standard mode will eventually treat them as 8-byte ints across all platforms, but that likely requires a new set of routines in longobject.c first (while sizeof(long) >= 4 is guaranteed by C, there's nothing in C we can rely on x-platform to hold 8 bytes of int, so we'll have to roll our own; I'm thinking of a simple pair of conversion functions, Python long to/from sized vector of unsigned bytes; that may be useful for GMP conversions too; std q/Q would call them with size fixed at 8). test_struct.py: In addition to adding some native-mode 'q' and 'Q' tests, got rid of unused code, and repaired a non-portable assumption about native sizeof(short) (it isn't 2 on some Cray boxes). libstruct.tex: In addition to adding a bit of 'q'/'Q' docs (more needed later), removed an erroneous footnote about 'I' behavior.
2001-06-10 20:40:19 -03:00
- New 'q' and 'Q' format codes in the struct module, corresponding to C
types "long long" and "unsigned long long" (on Windows, __int64). In
native mode, these can be used only when the platform C compiler supports
these types (when HAVE_LONG_LONG is #define'd by the Python config
process), and then they inherit the sizes and alignments of the C types.
Added q/Q standard (x-platform 8-byte ints) mode in struct module. This completes the q/Q project. longobject.c _PyLong_AsByteArray: The original code had a gross bug: the most-significant Python digit doesn't necessarily have SHIFT significant bits, and you really need to count how many copies of the sign bit it has else spurious overflow errors result. test_struct.py: This now does exhaustive std q/Q testing at, and on both sides of, all relevant power-of-2 boundaries, both positive and negative. NEWS: Added brief dict news while I was at it.
2001-06-11 22:22:22 -03:00
In standard mode, 'q' and 'Q' are supported on all platforms, and are
8-byte integral types.
Initial support for 'q' and 'Q' struct format codes: for now, only in native mode, and only when config #defines HAVE_LONG_LONG. Standard mode will eventually treat them as 8-byte ints across all platforms, but that likely requires a new set of routines in longobject.c first (while sizeof(long) >= 4 is guaranteed by C, there's nothing in C we can rely on x-platform to hold 8 bytes of int, so we'll have to roll our own; I'm thinking of a simple pair of conversion functions, Python long to/from sized vector of unsigned bytes; that may be useful for GMP conversions too; std q/Q would call them with size fixed at 8). test_struct.py: In addition to adding some native-mode 'q' and 'Q' tests, got rid of unused code, and repaired a non-portable assumption about native sizeof(short) (it isn't 2 on some Cray boxes). libstruct.tex: In addition to adding a bit of 'q'/'Q' docs (more needed later), removed an erroneous footnote about 'I' behavior.
2001-06-10 20:40:19 -03:00
Add new built-in 'help' which invokes pydoc.help (with a twist).
2001-06-12 13:48:52 -03:00
- The site module installs a new built-in function 'help' that invokes
pydoc.help. It must be invoked as 'help()'; when invoked as 'help',
it displays a message reminding the user to use 'help()' or
'help(object)'.
SF bug[ #423781: pprint.isrecursive() broken.
2001-05-14 04:05:58 -03:00
Tests
ReST-ification of the NEWS file. While the total number of changes are fairly large, most are caused by reformatting section and subsection headings. The changes fall into the following categories: * reformatted section and subsection headers. * escaped isolated asterisks which would be interpreted as starting bold or italic text (e.g. "void (*)(PyObject \*)"). * quoted stuff that looks like internal references but isn't (e.g. ``PyCmp_``). * changed visually balanced quotes to just use apostrophes (e.g. "'string'" instead of "`string'"). * introduced and indenting multiline chunks of code. * created one table (search for "New codecs").
2002-09-20 11:16:59 -03:00
-----
SF bug[ #423781: pprint.isrecursive() broken.
2001-05-14 04:05:58 -03:00
- New test_mutants.py runs dict comparisons where the key and value
Fix spelling errors and note the addition of operator.pow()
2002-08-19 11:25:03 -03:00
comparison operators mutate the dicts randomly during comparison. This
SF bug[ #423781: pprint.isrecursive() broken.
2001-05-14 04:05:58 -03:00
rapidly causes Python to crash under earlier releases (not for the faint
of heart: it can also cause Win9x to freeze or reboot!).
Fix spelling errors and note the addition of operator.pow()
2002-08-19 11:25:03 -03:00
- New test_pprint.py verifies that pprint.isrecursive() and
pprint's workhorse _safe_repr() function took time quadratic in the # of elements when crunching a list, dict or tuple. Now takes linear time instead -- huge speedup for even moderately large containers, and the code is notably simpler too. Added some basic "is the output correct?" tests to test_pprint.
2001-05-14 15:39:41 -03:00
pprint.isreadable() return sensible results. Also verifies that simple
cases produce correct output.
SF bug[ #423781: pprint.isrecursive() broken.
2001-05-14 04:05:58 -03:00
Cruft cleanup: Removed the unused last_is_sticky argument from the internal _PyTuple_Resize().
2001-05-28 19:30:08 -03:00
C API
ReST-ification of the NEWS file. While the total number of changes are fairly large, most are caused by reformatting section and subsection headings. The changes fall into the following categories: * reformatted section and subsection headers. * escaped isolated asterisks which would be interpreted as starting bold or italic text (e.g. "void (*)(PyObject \*)"). * quoted stuff that looks like internal references but isn't (e.g. ``PyCmp_``). * changed visually balanced quotes to just use apostrophes (e.g. "'string'" instead of "`string'"). * introduced and indenting multiline chunks of code. * created one table (search for "New codecs").
2002-09-20 11:16:59 -03:00
-----
Cruft cleanup: Removed the unused last_is_sticky argument from the internal _PyTuple_Resize().
2001-05-28 19:30:08 -03:00
- Removed the unused last_is_sticky argument from the internal
_PyTuple_Resize(). If this affects you, you were cheating.
ReST-ification of the NEWS file. While the total number of changes are fairly large, most are caused by reformatting section and subsection headings. The changes fall into the following categories: * reformatted section and subsection headers. * escaped isolated asterisks which would be interpreted as starting bold or italic text (e.g. "void (*)(PyObject \*)"). * quoted stuff that looks like internal references but isn't (e.g. ``PyCmp_``). * changed visually balanced quotes to just use apostrophes (e.g. "'string'" instead of "`string'"). * introduced and indenting multiline chunks of code. * created one table (search for "New codecs").
2002-09-20 11:16:59 -03:00
----
**(For information about older versions, consult the HISTORY file.)**