summaryrefslogtreecommitdiffstats
Commit message (Collapse)AuthorAgeFilesLines
* Hush up CVS.Fred Drake2001-10-191-0/+10
|
* Support for the iSilo conversion.Fred Drake2001-10-191-0/+12
|
* The usual post-release fiddling.Tim Peters2001-10-192-4/+29
|
* When stating that some parameters to makefile() are similar to the open()Fred Drake2001-10-191-1/+2
| | | | | | | | parameters, given a hyperlink to the right part of the documentation to make it easier to look those up. Also, refer to the file() function/ constructor instead of open() now that that is where the actual docs for those parameters live. This closes SF bug #472004.
* Updated version numbers for post 2.2b1 development.Barry Warsaw2001-10-191-3/+3
|
* added tests for long ints and ints where they are > 32 bits.Skip Montanaro2001-10-191-0/+14
| | | | should have been checked in as part of patch #470254.
* Fix for Bug #216405:Thomas Heller2001-10-191-4/+6
| | | | use the correct base for a buffer object in _PyBuffer_FromObject.
* (Hopefully) fix SF bug #472675: CVS socketmodule now doesn't compileGuido van Rossum2001-10-191-1/+1
| | | | | This appears to be a case of a missing \n\ in a multiline string literal.
* Additional test and documentation for the unicode() changes.Marc-André Lemburg2001-10-195-37/+93
| | | | 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.
* Added a note about the somewhat kludgey behavior of the messageBarry Warsaw2001-10-191-0/+10
| | | | | | epilogue, based on the discussion in this SF bug report: https://sourceforge.net/tracker/index.php?func=detail&aid=472481&group_id=25568&atid=384678
* Another merge from mimelib:Barry Warsaw2001-10-191-0/+27
| | | | | TestMIMEMessage.test_epilogue(), TestIdempotent.test_preamble_epilogue(): Test cases for SF bug #472481.
* Another email package test fileBarry Warsaw2001-10-191-0/+22
|
* Another merge from mimelib:Barry Warsaw2001-10-191-0/+2
| | | | | | _handle_multipart(): If there is an epilogue and the epilogue does not itself start with a newline, add a newline before writing the epilogue. Closes SF bug #472481.
* 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
|
* SF patch #470578: Fixes to synchronize unicode() and str()Guido van Rossum2001-10-193-72/+76
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This patch implements what we have discussed on python-dev late in September: str(obj) and unicode(obj) should behave similar, while the old behaviour is retained for unicode(obj, encoding, errors). The patch also adds a new feature with which objects can provide unicode(obj) with input data: the __unicode__ method. Currently no new tp_unicode slot is implemented; this is left as option for the future. Note that PyUnicode_FromEncodedObject() no longer accepts Unicode objects as input. The API name already suggests that Unicode objects do not belong in the list of acceptable objects and the functionality was only needed because PyUnicode_FromEncodedObject() was being used directly by unicode(). The latter was changed in the discussed way: * unicode(obj) calls PyObject_Unicode() * unicode(obj, encoding, errors) calls PyUnicode_FromEncodedObject() One thing left open to discussion is whether to leave the PyUnicode_FromObject() API as a thin API extension on top of PyUnicode_FromEncodedObject() or to turn it into a (macro) alias for PyObject_Unicode() and deprecate it. Doing so would have some surprising consequences though, e.g. u"abc" + 123 would turn out as u"abc123"... [Marc-Andre didn't have time to check this in before the deadline. I hope this is OK, Marc-Andre! You can still make changes and commit them on the trunk after the branch has been made, but then please mail Barry a context diff if you want the change to be merged into the 2.2b1 release branch. GvR]
* Another.Guido van Rossum2001-10-191-0/+1
|
* SF patch #470393 (Jim Ahlstrom): Add missing marshal functionGuido van Rossum2001-10-191-0/+8
| | | | | | | | | | In Include/, marshal.h declares both PyMarshal_ReadLongFromFile() and PyMarshal_ReadShortFromFile(), but the second is missing from marshal.c. [Shouldn't the return type be declared as 'short' instead of 'int'? But 'int' is what was in marshal.h all those years... --Guido]
* SF patch #460805 by Chris Gonnerman: Support for unsetenv()Guido van Rossum2001-10-196-20/+82
| | | | | | | | 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 #443759: Add Interface to readline's add_historyGuido van Rossum2001-10-192-0/+22
| | | | | | | | | | | | | | This was submitted by Moshe, but apparently he's too busy to check it in himself. He wrote: Here is a function in GNU readline called add_history, which is used to manage the history list. Though Python uses this function internally, it does not expose it to the Python programmer. This patch adds direct interface to this function with documentation. This could be used by friendly modules to "seed" the history with commands.
* Assume a 64-bit start and len if O_LARGEFILE is available.Martin v. Löwis2001-10-181-1/+8
|
* Expose O_LARGEFILE, O_DIRECT, O_DIRECTORY, and O_NOFOLLOW.Martin v. Löwis2001-10-181-0/+17
|
* Whitespace normalization.Tim Peters2001-10-1819-69/+62
|
* Move dlfcn.h block out of NetBSD block, assuming that NetBSD beforeMartin v. Löwis2001-10-181-3/+4
| | | | | 199712 didn't have dlfcn.h, or that it wouldn't conflict with the other stuff defined.
* The assignment to result.st_rdev can raise AttributeError as well asGuido van Rossum2001-10-181-1/+1
| | | | | TypeError (on systems where it's not defined at all, it raises AttributeError; when it's defined, assignment to it raises TypeError).
* changed misleading argument nameFredrik Lundh2001-10-182-18/+18
|
* Don't leave bare newlines in long strings -- VC doesn't like that.Guido van Rossum2001-10-181-3/+3
|
* add structseq.c to projectGuido van Rossum2001-10-181-0/+15
|
* SF Patch (but with no patch) 472555 Remove trailing common in enumeration.Tim Peters2001-10-181-1/+1
| | | | | Some AIX compiler didn't like the trailing comma at the end of the why_code enum decl.
* Missing file structseq.c for SF patch #462296Guido van Rossum2001-10-181-0/+284
|
* SF patch #462296: Add attributes to os.stat results; by Nick Mathewson.Guido van Rossum2001-10-1811-240/+814
| | | | | | | | | | | | | | | | | 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.)
* SF bug [#472347] pydoc and properties.Tim Peters2001-10-182-3/+35
| | | | | | | | | | | | | | | The GUI-mode code to display properties blew up if the property functions (get, set, etc) weren't simply methods (or functions). "The problem" here is really that the generic document() method dispatches to one of .doc{routine, class, module, other}(), but all of those require a different(!) number of arguments. Thus document isn't general-purpose at all: you have to know exactly what kind of thing is it you're going to document first, in order to pass the correct number of arguments to .document for it to pass on. As an expedient hack, just tacked "*ignored" on to the end of the formal argument lists for the .docXXX routines so that .document's caller doesn't have to know in advance which path .document is going to take.
* Shut up warnings for setgroups() on Linux -- you have to #includeGuido van Rossum2001-10-184-10/+18
| | | | <grp.h> it seems. This requires yet another configure test.
* Some minor clarifications for find()'s arguments based on SF bugBarry Warsaw2001-10-181-5/+6
| | | | #463572. Closing.
* Do not expect line number events when running under "python -O".Fred Drake2001-10-181-0/+3
| | | | | The right fix is to generate line number events anyway ;-), but this will have to do for now.
* SRE bug #441409:Fredrik Lundh2001-10-183-4/+16
| | | | | | | | compile should raise error for non-strings SRE bug #432570, 448951: reset group after failed match also bumped version number to 2.2.0
* Add a test for calling a weakref proxy with a dictionary of keyword args.Fred Drake2001-10-181-0/+3
|
* Remove an unnecessary check for NULL.Fred Drake2001-10-181-4/+3
|
* Note stricter tp_compare return value requirements.Guido van Rossum2001-10-181-0/+6
|
* Part 2/2 of SF patch #416704: More robust freeze, by Toby Dickenson.Guido van Rossum2001-10-183-11/+59
| | | | | | | | | | | | | (With slight cosmetic improvements to shorten lines and a grammar fix to a docstring.) This addes -X and -E options to freeze. From the docstring: -X module Like -x, except the module can never be imported by the frozen binary. -E: Freeze will fail if any modules can't be found (that were not excluded using -x or -X).
* Straighten out the exec*() function descriptions a bit, and clarify a fewFred Drake2001-10-181-65/+68
| | | | points in the spawn*() description.
* Squash compiler wng about signed/unsigned mismatch.Tim Peters2001-10-181-1/+1
|
* First part of SF patch #416704: More robust freeze, by Toby Dickenson.Guido van Rossum2001-10-181-5/+23
| | | | | | | This fixes the behavior reported by SF bug #404545, where a file x.y.py could be imported by the statement "import x.y" when there's a frozen package x (I believe even if x.y also exists as a frozen module).
* Fix the frozen bytecode for __hello__ (betcha didn't know that existedGuido van Rossum2001-10-184-5/+43
| | | | | | | | | | :-). Add a test that prevents the __hello__ bytecode from going stale unnoticed again. The test also tests the loophole noted in SF bug #404545. This test will fail right now; I'll check in the fix in a minute.
* Bump version number.Fred Drake2001-10-181-4/+3
| | | | Remove inconsistent use of HTMLDIR.
* Bump release information.Fred Drake2001-10-181-2/+2
|
* Add a note about changes related to the weak reference objects.Fred Drake2001-10-181-0/+4
|
* Make sure we do not core dump when using proxies with the binary slotFred Drake2001-10-181-0/+8
| | | | handlers. This was fixed in Objects/weakrefobject.c 1.2.
* When weakref proxies are involved in binary & ternary slot operations,Fred Drake2001-10-181-15/+28
| | | | | | | | | | | the left-hand operand may not be the proxy in all cases. If it isn't, we end up doing two things: a) unwrapping something that isn't a PyWeakReference (later resulting in a core dump) and b) passing a proxy as the right-hand operand anyway, even though that can't be handled by the actual handler (maybe eventually causing a core dump). This is fixed by always unwrapping all the proxies involved before passing anything to the actual handler.
generated by cgit v0.12 at 2024-11-24 01:54:58 (GMT)