summaryrefslogtreecommitdiffstats
Commit message (Collapse)AuthorAgeFilesLines
* Final tweaks for 2.2a3 distribution.Jack Jansen2001-09-0813-60/+104
|
* Silence warnings about passing unsigned char** as char**.Martin v. Löwis2001-09-081-4/+4
|
* Oops, this file is very outdated. Removed.Jack Jansen2001-09-081-116/+0
|
* Generalize operator.indexOf (PySequence_Index) to work with anyTim Peters2001-09-086-82/+128
| | | | | | | | | | 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.
* It appears that unittest was changed to stop hoarding raw exception data,Tim Peters2001-09-081-4/+1
| | | | | | | | | saving instead a traceback string, but test_support's run_unittest was still peeking into unittest internals and trying to pick apart unittest's errors and failures vectors as if they contained exc_info() tuples instead of strings. Whatever, when a unittest-based test failed, test_support blew up. I'm not sure this is the right way to fix it; it simply gets me unstuck.
* The usual post-release fiddling.Tim Peters2001-09-082-4/+24
|
* PyClass_New(): put the extended Don Beaudry hook back in. When one ofGuido van Rossum2001-09-071-4/+14
| | | | | | | | | | | | | | | | the base classes is not a classic class, and its class (the metaclass) is callable, call the metaclass to do the deed. One effect of this is that, when mixing classic and new-style classes amongst the bases of a class, it doesn't matter whether the first base class is a classic class or not: you will always get the error "TypeError: metatype conflict among bases". (Formerly, with a classic class first, you'd get "TypeError: PyClass_New: base must be a class".) Another effect is that multiple inheritance from ExtensionClass.Base, with a classic class as the first class, transfers control to the ExtensionClass.Base class. This is what we need for SF #443239 (and also for running Zope under 2.2a4, before ExtensionClass is replaced).
* PySequence_Check(), PyMapping_Check(): only return true if theGuido van Rossum2001-09-071-2/+4
| | | | | | | | | | | | | | | corresponding "getitem" operation (sq_item or mp_subscript) is implemented. I realize that "sequence-ness" and "mapping-ness" are poorly defined (and the tests may still be wrong for user-defined instances, which always have both slots filled), but I believe that a sequence that doesn't support its getitem operation should not be considered a sequence. All other operations are optional though. For example, the ZODB BTree tests crashed because PySequence_Check() returned true for a dictionary! (In 2.2, the dictionary type has a tp_as_sequence pointer, but the only field filled is sq_contains, so you can write "if key in dict".) With this fix, all standalone ZODB tests succeed.
* PyType_IsSubtype(): test tp_flags for HAVE_CLASS bit before accessingGuido van Rossum2001-09-071-0/+3
| | | | | | | | | | | | a->tp_mro. If a doesn't have class, it's considered a subclass only of itself or of 'object'. This one fix is enough to prevent the ExtensionClass test suite from dumping core, but that doesn't say much (it's a rather small test suite). Also note that for ExtensionClass-defined types, a different subclass test may be needed. But I haven't checked whether PyType_IsSubtype() is actually used in situations where this matters -- probably it doesn't, since we also don't check for classic classes.
* Bumping version numbers.Barry Warsaw2001-09-071-2/+2
|
* Merging in removal of this file from branch to trunk.Barry Warsaw2001-09-071-163/+0
|
* Merging 2.2a3 branch changes back into trunkBarry Warsaw2001-09-071-8/+18
|
* Patch #438790: Add additional mappings.Martin v. Löwis2001-09-071-3/+36
| | | | Also remove mappings that are not registered with IANA, and not extensions.
* Patch #450702: allow threads when calling into zlib, protect usage ofMartin v. Löwis2001-09-071-114/+350
| | | | the module in multiple threads with a global lock.
* Fix compiler warnings. This closes some of the #458880 problem.Martin v. Löwis2001-09-071-9/+8
|
* (Slightly modified) patch by Steve Spicklemire to make Python buildJack Jansen2001-09-072-250/+286
| | | | | | | | | out of the box on OSX 10.1. Untested by me (except for not having adverse effects on 10.0.4) but it looks good, for now. Eventually we should not trigger on the darwin version but test for something, but until I have the time to install 10.1 myself I have no clue what to test on. It would be nice if this got in to the 2.2a3 distribution.
* Fix bug #410274 - sys.prefix isn't always set.Mark Hammond2001-09-071-1/+35
| | | | If after calculating sys.path we do not have sys.prefix set, we loop over all path entries checking if one can point to our home directory.
* Patch by Mark Day to allow from __future__ imports. Looks harmlessJack Jansen2001-09-071-3/+5
| | | | | | | enough, but may have side-effects because it preallocates a single codeop.Compiler() to compile all statements the user enters. Just: please review and retract/modify if necessary.
* SF bug [#458941] Looks like a unary minus bug.Tim Peters2001-09-071-16/+49
| | | | | | | | | | com_factor(): when a unary minus is attached to a float or imaginary zero, don't optimize the UNARY_MINUS opcode away: the const dict can't distinguish between +0.0 and -0.0, so ended up treating both like the first one added to it. Optimizing UNARY_PLUS away isn't a problem. (BTW, I already uploaded the 2.2a3 Windows installer, and this isn't important enough to delay the release.)
* Fix typo in error reporting. This doesn't need to go into the releaseTim Peters2001-09-071-1/+1
| | | | branch (if it ever gets to the typo, the test is failing anyway).
* Reverting to rev 1.2. Apparently gcc doesn't use the extended-precisionTim Peters2001-09-061-3/+16
| | | | | | | | capabilities of the Pentium FPU, so what should have been (and were on Windows) exact results got fuzzy. Then it turns out test_support.fcmp() isn't tolerant of tiny errors when *one* of the comparands is 0, but test_complex's old check_close_real() is. Rather than fix gcc <wink>, easier to revert this test and revisit after the release.
* Rewrite to use test_support's fine fcmp instead -- I didn't know thatTim Peters2001-09-061-16/+3
| | | | existed when I wrote this test.
* Added some underflow-to-0.0 long/long true division tests.Tim Peters2001-09-061-0/+6
|
* Rename 'getset' to 'property'.Guido van Rossum2001-09-061-5/+5
|
* long_true_divide: reliably force underflow to 0 when the denominatorTim Peters2001-09-061-0/+2
| | | | | | has more bits than the numerator than can be counted in a C int (yes, that's unlikely, and no, I'm not adding a test case with a 2 gigabit long).
* Rename 'getset' to 'property'.Guido van Rossum2001-09-066-45/+45
|
* Do not rebuild html-$(RELEASE).tar every time we need to use it.Fred Drake2001-09-061-1/+1
|
* Bump version number.Fred Drake2001-09-061-1/+1
|
* Update link to the PyOpenGL project in the "gl" module docs.Fred Drake2001-09-061-6/+8
| | | | This closes SF bug #459256.
* Add missing period in docstring.Fred Drake2001-09-061-1/+1
| | | | (Steve, can you add this to the PyUnit repository as well?)
* Document the built-in iter() function.Fred Drake2001-09-061-0/+17
|
* Bump version number.Fred Drake2001-09-061-1/+1
|
* Added an additional link to NIST information on secure hashing.Fred Drake2001-09-061-0/+4
| | | | This closes SF bug #458785.
* Clarified the interaction between string literals and continuation lines.Fred Drake2001-09-061-5/+28
| | | | Fixes bug reported as SF bug #453728.
* Make the examples for "Default Argument Values" more presentable andFred Drake2001-09-061-9/+13
| | | | | less hostile to newbie use at the interactive prompt. This is in response to SF bug #458654.
* Fix parameter for PyInt_Check().Fred Drake2001-09-061-1/+31
| | | | Add refcount information for other recently documented APIs.
* Document the PyMethod_* type object, functions, and macros.Fred Drake2001-09-061-0/+58
|
* Minimal instructions for using the Makefile here. Also a clearJack Jansen2001-09-061-0/+28
| | | | | statement that this is a proof-of-concept meant for people to experiment with, nothing more.
* Added targets to install the application, and to install mac-additionsJack Jansen2001-09-061-1/+113
| | | | in Python.
* Bump Windows buildno (installer changes were made earlier).Tim Peters2001-09-062-2/+4
|
* Document the rule that Python.h must be included before any standardFred Drake2001-09-062-2/+7
| | | | headers. This is the final checkin for SF bug #458768.
* Do not #include <stdio.h> since Python.h already does that.Fred Drake2001-09-061-1/+0
|
* Use the standard argument convention for main(), and conform to theFred Drake2001-09-061-1/+2
| | | | Python/C style guide.
* Two small changes to the resource usage option:Guido van Rossum2001-09-062-4/+5
| | | | | | | | (1) Allow multiple -u options to extend each other (and the initial value of use_resources passed into regrtest.main()). (2) When a test is run stand-alone (not via regrtest.py), needed resources are always granted.
* Added note of unittest.py changes that fixed bug 451309Steve Purcell2001-09-061-0/+4
|
* Several updates to cover omissions noted by Rich Salz.Fred Drake2001-09-061-3/+27
| | | | This closes SF bug #458771.
* Document the "unixfrom" attribute of the rfc822.Message class.Fred Drake2001-09-061-1/+7
| | | | Based on a patch by Skip Montanaro, this closes SF bug #458885.
* Added tests for key deletion for both Weak*Dictionary flavors.Fred Drake2001-09-061-0/+22
| | | | This covers regression on SF bug #458860.
* Add __delitem__() support for WeakKeyDictionary.Fred Drake2001-09-061-0/+7
| | | | This closes SF bug #458860.
* Skip instead of fail this test if the socket module has no sslGuido van Rossum2001-09-061-0/+3
| | | | support.
generated by cgit v0.12 at 2025-09-15 09:44:45 (GMT)