summaryrefslogtreecommitdiffstats
path: root/Misc
Commit message (Collapse)AuthorAgeFilesLines
* News about OS/2 Visual Age C++ patches.Tim Peters2001-11-051-0/+3
|
* Finish SF patch 477059: __del__ on new classes vs. GC.Tim Peters2001-11-031-0/+5
| | | | Just doc and NEWS here, about the change in gc.garbage meaning.
* Improved error msg when a symbolic group name is redefined. Added docsTim Peters2001-11-031-0/+6
| | | | | | 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.
* Patch #471120: Improved doc strings and new wrappers.Martin v. Löwis2001-11-021-0/+5
|
* Move a name into correct position.Tim Peters2001-10-311-1/+1
|
* SF patch #474485: pydoc generates some bad html, from Rich Salz.Tim Peters2001-10-311-0/+1
|
* SF patch #474500: Make OS/2 locks work like posix locks, from MichaelTim Peters2001-10-311-0/+1
| | | | Muller.
* SF bug #474077 2.2b1: Error compiling extns with BCCTim Peters2001-10-301-0/+1
| | | | | | Removed "#undef HAVE_HYPOT" line from Borland config, as suggested. Whether this will break some other Borland usage is a good question I can't answer.
* News and attribution for SF bug #473009.Guido van Rossum2001-10-302-0/+4
|
* Rename "dictionary" (type and constructor) to "dict".Tim Peters2001-10-291-0/+3
|
* Add __del__ callbacks. They are too useful to leave out.Guido van Rossum2001-10-291-0/+3
| | | | | | | | | | | | | | | | 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.
* News about the socket type and the HP-UX port.Guido van Rossum2001-10-271-1/+8
|
* Updated this README to reality.Guido van Rossum2001-10-261-15/+6
|
* Some news.Guido van Rossum2001-10-261-1/+13
|
* Delete Makefile.pre.in (BDFL pronouncement)Andrew M. Kuchling2001-10-261-305/+0
|
* Generalize dictionary() to accept a sequence of 2-sequences. At theTim Peters2001-10-261-0/+9
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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).
* Fix two typos, one noted by Noah Spurrier in SF bug #475166, theGuido van Rossum2001-10-261-0/+1
| | | | | second noted after a second's thought about what the next line should do. :-(
* I went back and figured out the release date for Python 2.2a1.Barry Warsaw2001-10-251-0/+1
|
* Fix SF bug #474538: Memory (reference) leak in poller.register (Dave Brueck)Guido van Rossum2001-10-251-0/+1
| | | | | | | | Replace some tortuous code that was trying to be clever but forgot to DECREF the key and value, by more longwinded but obviously correct code. (Inspired by but not copying the fix from SF patch #475033.)
* Note updated RISCOS port. Remove reference in the 2.1 release notesGuido van Rossum2001-10-241-4/+8
| | | | to os.extsep -- that variable actually didn't exist in that release!
* SF patch #474175 (Jay T Miller): file.readinto arg parsing bugGuido van Rossum2001-10-231-0/+1
| | | | | | | | | | | | | | | | | | | | | | The C-code in fileobject.readinto(buffer) which parses the arguments assumes that size_t is interchangeable with int: size_t ntodo, ndone, nnow; if (f->f_fp == NULL) return err_closed(); if (!PyArg_Parse(args, "w#", &ptr, &ntodo)) return NULL; This causes a problem on Alpha / Tru64 / OSF1 v5.1 where size_t is a long and sizeof(long) != sizeof(int). The patch I'm proposing declares ntodo as an int. An alternative might be to redefine w# to expect size_t. [We can't change w# because there are probably third party modules relying on it. GvR]
* Doc and NEWS changes due to Jeremy adding traceback objects to gc.Tim Peters2001-10-231-0/+4
|
* Added two very tardy notes about the 2.2b1 release, fixed a typo.Fred Drake2001-10-221-1/+9
|
* Add curses-related news itemsAndrew M. Kuchling2001-10-221-0/+5
|
* Fix some typosAndrew M. Kuchling2001-10-221-4/+4
|
* Methods of built-in types now properly check for keyword argumentsGuido van Rossum2001-10-221-0/+4
| | | | | (formerly these were silently ignored). The only built-in methods that take keyword arguments are __call__, __init__ and __new__.
* Patch from SF bug #473150: configure weaknesses on HP-UX (Michael Piotrowski)Guido van Rossum2001-10-201-0/+1
| | | | | | | | | | 1. configure doesn't handle HP-UX release numbers (e.g., B.11.00), resulting in MACHDEP = "hpuxB". 2. After checking for wchar.h, configure doesn't include it when checking the size of wchar_t. (Python 2.2b1 on HP-UX 11.00)
* The usual post-release fiddling.Tim Peters2001-10-191-0/+25
|
* Additional test and documentation for the unicode() changes.Marc-André Lemburg2001-10-191-1/+1
| | | | This patch should also be applied to the 2.2b1 trunk.
* Last minute updates for changes since 2.2a4. Unless Fred wants to addBarry Warsaw2001-10-191-2/+37
| | | | | anything about the hotshot profiler, this file is ready for the 2.2b1 Windows build.
* Add entry for RAND_xxx() functions in socket module.Jeremy Hylton2001-10-191-0/+5
|
* Note the Unicode changes from SF patch #470578.Guido van Rossum2001-10-191-1/+9
|
* Another.Guido van Rossum2001-10-191-0/+1
|
* SF patch #460805 by Chris Gonnerman: Support for unsetenv()Guido van Rossum2001-10-191-8/+9
| | | | | | | | 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?)
* SF patch #462296: Add attributes to os.stat results; by Nick Mathewson.Guido van Rossum2001-10-181-1/+11
| | | | | | | | | | | | | | | | | 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.)
* Note stricter tp_compare return value requirements.Guido van Rossum2001-10-181-0/+6
|
* Add a note about changes related to the weak reference objects.Fred Drake2001-10-181-0/+4
|
* SF bug #471720: ThreadingMixIn/TCPServer forgets closeGuido van Rossum2001-10-182-0/+4
| | | | | Solved with a helper method that calls finish_request() and then close_request(). The code is by Max Neunhöffer.
* Fix SF bug #472234: type(obj) calls type->tp_init (Roeland Rengelink)Guido van Rossum2001-10-181-0/+1
| | | | | The fix is a band-aid: type_call() now makes the same exception for a single-argument call to type() as type_new() was already making.
* Expose setgroups. Fixes feature request #468116.Martin v. Löwis2001-10-181-1/+1
|
* SF patch #467430.Guido van Rossum2001-10-171-0/+1
| | | | | | - replace some log_error() calls with log_message() - flush self.rfile before forking too (hope this works on Windows)
* YAPC.Guido van Rossum2001-10-171-0/+1
|
* Add fix for getattr(obj, name, default). Rearrange a few things.Guido van Rossum2001-10-161-7/+14
|
* Partial patch from SF #452266, by Jason Petrone.Guido van Rossum2001-10-161-0/+9
| | | | | | 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.)
* Add note about new zlib feature.Jeremy Hylton2001-10-161-1/+6
|
* Add Shane.Guido van Rossum2001-10-161-0/+1
|
* Reword the text on the demise of __dynamic__ somewhat, correcting aGuido van Rossum2001-10-161-4/+5
| | | | typo.
* Get rid of __defined__ and tp_defined -- there's no need toGuido van Rossum2001-10-151-9/+8
| | | | | distinguish __dict__ and __defined__ any more. In the C structure, tp_cache takes its place -- but this hasn't been implemented yet.
* Another contributor.Guido van Rossum2001-10-151-0/+1
|
* Patch 471400: escape single-dot lines; by Jason Hildebrand.Guido van Rossum2001-10-151-0/+1
| | | | | RFC 2049 recommends never outputting a line consisting of a single dot.
generated by cgit v0.12 at 2024-11-27 15:59:28 (GMT)