summaryrefslogtreecommitdiffstats
path: root/Misc
Commit message (Collapse)AuthorAgeFilesLines
* Fix caseAndrew M. Kuchling2003-04-241-1/+1
|
* [Patch #679505] Document that the rotor module is deprecatedAndrew M. Kuchling2003-04-241-0/+4
|
* New module platform.py, submitted by Marc-Andre Lemburg.Marc-André Lemburg2003-04-241-0/+3
| | | | | There's no separate documentation for this module yet - apart from the doc-strings which explain the APIs.
* Revert the previous enhancement to the bytecode optimizer.Raymond Hettinger2003-04-241-7/+0
| | | | The additional code complexity and new NOP opcode were not worth it.
* Mention the new getargs.c format codes.Thomas Heller2003-04-231-0/+3
|
* SF patch 557704: netrc module can't handle all passwordsRaymond Hettinger2003-04-231-0/+2
| | | | | | | | | 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.
* Enable os.fsync() for Windows, mapping it to MS's _commit() there. TheTim Peters2003-04-231-0/+3
| | | | | | 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).
* Adding new built-in function sum, with docs and tests.Alex Martelli2003-04-221-0/+4
|
* Improved the bytecode optimizer.Raymond Hettinger2003-04-221-0/+7
| | | | | | | | | | | | | | * Can now test for basic blocks. * Optimize inverted comparisions. * Optimize unary_not followed by a conditional jump. * Added a new opcode, NOP, to keep code size constant. * Applied NOP to previous transformations where appropriate. Note, the NOP would not be necessary if other functions were added to re-target jump addresses and update the co_lnotab mapping. That would yield slightly faster and cleaner bytecode at the expense of optimizer simplicity and of keeping it decoupled from the line-numbering structure.
* Patch #553171: Add writeback parameter. Also add protocol parameter.Martin v. Löwis2003-04-191-0/+3
|
* - bool() called without arguments now returns False rather thanGuido van Rossum2003-04-191-0/+5
| | | | | | | 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.
* - Several methods of nntplib.NNTP have grown an optional file argumentGuido van Rossum2003-04-192-0/+5
| | | | | | which specifies a file where to divert the command's output (already supported by the body() method). (SF patch #720468) Thanks to Terry Carroll.
* Patch #536883: SimpleXMLRPCServer auto-docing subclass.Martin v. Löwis2003-04-181-0/+2
|
* Implement IDNA (Internationalized Domain Names in Applications).Martin v. Löwis2003-04-181-0/+5
|
* _Py_PrintReferenceAddresses(): also print the type name. In real useTim Peters2003-04-182-1/+13
| | | | | | | | | 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.
* Implemented posix-mode parsing support in shlex.py, as dicussed inGustavo Niemeyer2003-04-171-0/+4
| | | | mailing list, and in patch #722686.
* - New C API PyGC_Collect(), same as calling gc.collect().Guido van Rossum2003-04-171-1/+7
| | | | | - Call this in Py_Finalize(). - Expand the Misc/NEWS text on PY_LONG_LONG.
* Changes in support of PEP 269.Guido van Rossum2003-04-171-0/+5
|
* - The repr() of a weakref object now shows the __name__ attribute ofGuido van Rossum2003-04-161-0/+3
| | | | | | | 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.
* For StringVar results to strings. Document that boolean things are ofMartin v. Löwis2003-04-161-0/+3
| | | | type bool. Requested in #721171.
* - super() no longer ignores data descriptors, except __class__. SeeGuido van Rossum2003-04-161-0/+4
| | | | | the thread started at http://mail.python.org/pipermail/python-dev/2003-April/034338.html
* Add two dictionaries to htmlentitydefs: name2codepoint mapsWalter Dörwald2003-04-161-0/+4
| | | | | HTML entity names to Unicode codepoints (as integers). codepoint2name is the reverse mapping. From SF patch #722017.
* - pythunrun.c, Py_Finalize(): move the call to _Py_PrintReferences()Guido van Rossum2003-04-151-0/+4
| | | | | | | | | | | | | | | | | | | 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.
* The date class is now properly subclassable. (SF bug #720908)Guido van Rossum2003-04-141-0/+2
| | | | | (This is only the tip of the iceberg; the time and datetime classes need the same treatment.)
* - list.insert(i, x) now interprets negative i as it would beGuido van Rossum2003-04-141-0/+5
| | | | | | 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.
* SF patch #720991 by Gary Herron:Guido van Rossum2003-04-141-0/+4
| | | | | | | 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.
* Patch by Chad Netzer (with significant change):Guido van Rossum2003-04-111-0/+5
| | | | | | | - 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.)
* Added a note that the Mac OSA modules are documented.Jack Jansen2003-04-111-1/+2
|
* - New function winsound.MessageBeep() wraps the Win32 APIGuido van Rossum2003-04-091-1/+2
| | | | MessageBeep().
* - New function sys.call_tracing() allows pdb to debug codeGuido van Rossum2003-04-091-0/+6
| | | | | | recursively. - pdb has a new command, "debug", which lets you step through arbitrary code from the debugger's (pdb) prompt.
* s/referrents/referents/g. Gotta love that referrers remains rife with rs.Tim Peters2003-04-081-1/+1
|
* Finished implementing gc.get_referrents(): dealt with error and endTim Peters2003-04-081-0/+5
| | | | cases, wrote docs, added a test.
* Reworked has_finalizer() to use the new _PyObject_Lookup() insteadTim Peters2003-04-071-3/+11
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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).
* SF bug #715145: unittest.py still uses != in failUnlessEqualRaymond Hettinger2003-04-041-0/+4
|
* Revert Patch #670715: iconv support.Martin v. Löwis2003-04-031-5/+2
|
* Fix description: u"%c" % 0xffffffff returned a ValueError not a TypeError.Walter Dörwald2003-04-021-1/+1
|
* Change formatchar(), so that u"%c" % 0xffffffff now raisesWalter Dörwald2003-04-021-1/+2
| | | | | an OverflowError instead of a TypeError to be consistent with "%c" % 256. See SF patch #710127.
* Added a note about scripting support and the IDE builtin help.Jack Jansen2003-04-011-0/+6
|
* Fix PyString_Format() so that '%c' % u'a' returns u'a'Walter Dörwald2003-03-311-0/+3
| | | | | | | | instead of raising a TypeError. (From SF patch #710127) Add tests to verify this is fixed. Add various tests for '%c' % int.
* Fix typo.Walter Dörwald2003-03-311-1/+1
|
* Patch #545300: Support marked sections.Martin v. Löwis2003-03-301-0/+3
|
* The socket module now always uses the _socketobject wrapper class, even onSkip Montanaro2003-03-301-0/+5
| | | | | | | | | 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.
* Rename LONG_LONG to PY_LONG_LONG. Fixes #710285.Martin v. Löwis2003-03-291-0/+2
|
* Fix typo.Walter Dörwald2003-03-261-1/+1
|
* Frank Vercruesse gave an okay on removing the copyright notice:Jack Jansen2003-03-251-0/+1
| | | | | "Hereby I make the script in question available under the terms and conditions of the latest Python License."
* Added a Mac note that EasyDialogs dialogs now bring the application toJack Jansen2003-03-241-1/+3
| | | | the foreground.
* When Py_TRACE_REFS is defined, a list of all live objects is maintained inTim Peters2003-03-231-4/+13
| | | | | | | | | | | a doubly-linked list, exposed by sys.getobjects(). Unfortunately, it's not really all live objects, and it seems my fate to bump into programs where sys.gettotalrefcount() keeps going up but where the reference leaks aren't accounted for by anything in the list of all objects. This patch helps a little: if COUNT_ALLOCS is also defined, from now on type objects will also appear in this list, provided at least one object of a type has been allocated.
* add several people involved with PEP 305 and the csv packageSkip Montanaro2003-03-201-0/+3
|
* announce csv packageSkip Montanaro2003-03-201-0/+2
|
* SF bug 705836: struct.pack of floats in non-native endian orderTim Peters2003-03-201-0/+8
| | | | | | | | | | | | | | 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.
generated by cgit v0.12 at 2025-01-07 23:25:53 (GMT)