summaryrefslogtreecommitdiffstats
Commit message (Collapse)AuthorAgeFilesLines
* Replaced PyMac_FullPath by PyMac_FullPathname, which has an extra 'length'Jack Jansen2001-09-106-35/+74
| | | | | | parameter for the return string (as unix pathnames are not limited by the 255 char pstring limit). Implemented the function for MachO-Python, where it returns unix pathnames.
* more xmlrpclib tweaks: fixed repr(Fault()); enable UTF-8 parsing inFredrik Lundh2001-09-101-12/+17
| | | | xmllib (on 2.0 and later)
* More for SF bug [#460020] bug or feature: unicode() and subclassesTim Peters2001-09-103-2/+7
| | | | | Repair float constructor to return a true float when passed a subclass instance. New PyFloat_CheckExact macro.
* Superseded by Python 2.2.vct.Jack Jansen2001-09-101-0/+0
|
* SF bug #460020: bug or feature: unicode() and subclasses.Tim Peters2001-09-106-3/+55
| | | | | | | | | | | Given an immutable type M, and an instance I of a subclass of M, the constructor call M(I) was just returning I as-is; but it should return a new instance of M. This fixes it for M in {int, long}. Strings, floats and tuples remain to be done. Added new macros PyInt_CheckExact and PyLong_CheckExact, to more easily distinguish between "is" and "is a" (i.e., only an int passes PyInt_CheckExact, while any sublass of int passes PyInt_Check). Added private API function _PyLong_Copy.
* _portable_fseek():Guido van Rossum2001-09-101-0/+6
| | | | | | | | | | | | | | | | | | | | | Subtlety on Windows: if we change test_largefile.py to use a file > 4GB, it still fails. A debug session suggests this is because fseek(fp, 0, 2) refuses to seek to the end of the file when the file is > 4GB, because it uses the SetFilePointer() in 32-bit mode. But it only fails when we seek relative to the end of the file, because in the other seek modes only calls to fgetpos() and fsetpos() are made, which use Get/SetFilePointer() in 64-bit mode. Solution: #ifdef MS_WInDOWS, replace the call to fseek(fp, ...) with a call to _lseeki64(fileno(fp), ...). Make sure to call fflush(fp) first. (XXX Could also replace the entire branch with a call to _lseeki64(). Would that be more efficient? Certainly less generated code.) (XXX This needs more testing. I can't actually test that it works for files >4GB on my Win98 machine, because the filesystem here won't let me create files >=4GB at all. Tim should test this on his Win2K machine.)
* sync with pythonware codebase: much faster import (doesn't importFredrik Lundh2001-09-101-65/+70
| | | | | xmllib unless needed), merged docstring patches, added overridable Transport.getparser to simplify plugging in different parsers.
* Another volunteer.Guido van Rossum2001-09-101-0/+1
|
* PyObject_Dir():Guido van Rossum2001-09-101-2/+6
| | | | | | - use PyModule_Check() instead of PyObject_TypeCheck(), now we can. - don't assert that the __dict__ gotten out of a module is always a dictionary; check its type, and raise an exception if it's not.
* PyModule_Check() now checks for subtype of module, as it should.Guido van Rossum2001-09-101-1/+1
|
* Remove some XXX markersAndrew M. Kuchling2001-09-101-15/+17
| | | | Update the patch and bug counts
* Use $(CC) -G to link shared libraries on Solaris.Martin v. Löwis2001-09-102-4/+4
|
* Work around a LaTeX2HTML bug that caused the "m" in "mutable" to be droppedFred Drake2001-09-101-1/+1
| | | | in one place.
* Remove two XXX comments that have been resolved.Guido van Rossum2001-09-101-2/+0
|
* Move the global variables 'size' and 'name' to the top -- these areGuido van Rossum2001-09-101-5/+5
| | | | | "module parameters", and used in the Windows test (which crashed because size was undefined -- sigh).
* Improve threading on Solaris, according to SF patch #460269, submittedGuido van Rossum2001-09-105-224/+324
| | | | | | | | | | by bbrox@bbrox.org / lionel.ulmer@free.fr. This adds a configure check and if all goes well turns on the PTHREAD_SCOPE_SYSTEM thread attribute for new threads. This should remove the need to add tiny sleeps at the start of threads to allow other threads to be scheduled.
* Change the criteria for skipping the test.Guido van Rossum2001-09-101-19/+22
| | | | | | | | | | | | | | | If on Windows, we require the 'largefile' resource. If not on Windows, we use a test that actually writes a byte beyond the 2BG limit -- seeking alone is not sufficient, since on some systems (e.g. Linux with glibc 2.2) the sytem call interface supports large seek offsets but not all filesystem implementations do. Note that on Windows, we do not use the write test: on Win2K, that test can take a minute trying to zero all those blocks on disk, and on Windows our code always supports large seek offsets (but again, not all filesystems do). This may mean that on Win95, or on certain other backward filesystems, test_largefile will *fail*.
* Removed an erronous comment about alias files.Jack Jansen2001-09-101-3/+0
|
* Add section on long integer changesAndrew M. Kuchling2001-09-101-18/+69
| | | | | Add removal of 3-arg pow() for floats Rewrite introduction a bit
* Add a few more todo items.Guido van Rossum2001-09-101-1/+12
|
* Test the failed-unicode-decoding bug in PyArg_ParseTuple().Jeremy Hylton2001-09-101-0/+24
|
* Fix core dump in PyArg_ParseTuple() with Unicode arguments.Jeremy Hylton2001-09-101-15/+17
| | | | | | | | | Reported by Fredrik Lundh on python-dev. The conversimple() code that handles Unicode arguments and converts them to the default encoding now calls converterr() with the original Unicode argument instead of the NULL returned by the failed encoding attempt.
* Repair late-night doc typos.Tim Peters2001-09-102-3/+3
|
* This time (I hope) I've fixed largefileGuido van Rossum2001-09-094-420/+327
| | | | | | support on Linux (and Solaris, I expect) for real. The necessary symbols are defined once and for all, under the assumption that they won't harm elsewhere.
* Teach regrtest how to pass on doctest failure msgs. This is done via aTim Peters2001-09-098-27/+95
| | | | | | | | | | | horridly inefficient hack in regrtest's Compare class, but it's about as clean as can be: regrtest has to set up the Compare instance before importing a test module, and by the time the module *is* imported it's too late to change that decision. The good news is that the more tests we convert to unittest and doctest, the less the inefficiency here matters. Even now there are few tests with large expected-output files (the new cost here is a Python-level call per .write() when there's an expected- output file).
* Force "test." into the start of the module name, inherited by class andTim Peters2001-09-091-17/+11
| | | | type reprs, to accomodate the way Jack runs tests on the Mac.
* Install the dialog resources into the application bundle. The EasyDialogsJack Jansen2001-09-091-1/+7
| | | | selftest now works.
* Don't call MacOS.SchedParams() in MachO, it doesn't exist.Jack Jansen2001-09-091-4/+8
|
* Minimal module to decode AppleSingle files (the way resource files areJack Jansen2001-09-091-0/+101
| | | | | | | stored in the CVS repository). It can either decode resource/data forks in the standard Mac way or decode only the resource fork but store the result in the data fork (the MacOSX preferred way). Finder info and all other stuff is ignored.
* This commit was manufactured by cvs2svn to create tag 'r22a3'.v2.2a3cvs2svn2001-09-081-0/+1
|
* 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).
generated by cgit v0.12 at 2025-01-09 11:20:26 (GMT)