summaryrefslogtreecommitdiffstats
path: root/Modules
Commit message (Collapse)AuthorAgeFilesLines
* Remove PyArg_NoArgs() and PyArg_GetInt()Neal Norwitz2006-03-171-2/+0
|
* Get rid of xreadlines() (methods).Neal Norwitz2006-03-171-8/+0
|
* Checkpoint. 218 tests are okay; 53 are failing. Done so far:Guido van Rossum2006-03-151-33/+2
| | | | | | | | - all classes are new-style (but ripping out classobject.[ch] isn't done) - int/int -> float - all exceptions must derive from BaseException - absolute import - 'as' and 'with' are keywords
* Try to avoid many of the compiler warnings when compiling libffi byThomas Heller2006-03-141-3/+3
| | | | using a proper function prototype.
* Cast an Py_ssize_t to int, to avoid a compiler warning.Thomas Heller2006-03-141-2/+2
|
* Integrate patch from Neal Norwitz. He writes:Thomas Heller2006-03-143-56/+60
| | | | | | | | | | | | | | | | | | """ The attached patch fixes all the ctypes tests so they pass on amd64. It also fixes several warnings. I'm not sure what else to do with the patch. Let me know how you want to handle these in the future. I'm not sure the patch is 100% correct. You will need to decide what can be 64 bits and what can't. I believe sq_{item,slice,ass_item,ass_slice} all need to use Py_ssize_t. The types in ctypes.h may not require all the changes I made. I don't know how you want to support older version, so I unconditionally changed the types to Py_ssize_t. """ The patch is also in the ctypes SVN repository now, after small changes to add compatibility with older Python versions.
* Fix and test (manually w/xx module) passing NULLs to PyObject_Str() andNeal Norwitz2006-03-141-0/+14
| | | | | | | | | | | | | PyObject_Unicode(). This problem was originally reported from Coverity and addresses mail on python-dev "checkin r43015". This inlines the conversion of the string to unicode and cleans up/simplifies some code at the end of the PyObject_Unicode(). We really need a complete C API test module for all public APIs and passing good and bad parameter values. Will backport.
* Bug #1448490: Fix a bug that ISO-2022 codecs could not handleHye-Shik Chang2006-03-131-1/+1
| | | | SS2 (single-shift 2) escape sequences correctly.
* merged with cElementTree development trunk (1.0.6 snapshot):Fredrik Lundh2006-03-121-32/+60
| | | | | | Fixed a number of potential null-pointer-reference-under-pressure glitches, based on input from the Coverity analysis tool and Simo Salminen.
* Fix another leak in bsddb, and avoid use of uninitialized value -- funny howThomas Wouters2006-03-121-1/+2
| | | | gcc 4.0.x wasn't complaining about *that* one ;)
* Adjust CJK Ideograph range to Unicode 4.1.Martin v. Löwis2006-03-111-13/+12
|
* Fix refcounting bug.Martin v. Löwis2006-03-101-0/+1
|
* Avoid forward-declaring the methods array.Martin v. Löwis2006-03-101-52/+53
| | | | Rename unicodedata.db* to unicodedata.ucd*
* Um, I thought I'd already checked this in.Guido van Rossum2006-03-101-27/+4
| | | | | | | Anyway, this is the changes to the with-statement so that __exit__ must return a true value in order for a pending exception to be ignored. The PEP (343) is already updated.
* Update Unicode database to Unicode 4.1.Martin v. Löwis2006-03-093-12495/+16107
|
* Try to be a bit more consistent on all platforms:Neal Norwitz2006-03-091-1/+2
| | | | | | | python . python < . both print a message, return non-zero and do not core dump.
* Copy ctypes-0.9.9.4 sources from external into the trunk.Thomas Heller2006-03-08108-0/+43876
|
* typoGeorg Brandl2006-03-081-1/+1
|
* Fix logic error and DECREF reported by Coverity.Neal Norwitz2006-03-081-4/+4
|
* Clean up _bsddb.c: add a couple dozen missing Py_DECREF()'s, a handful ofThomas Wouters2006-03-081-65/+73
| | | | | | | | | | missing PyObject_Del()'s, simplify some code by using Py_BuildValue() instead of creating a tuple with items manually, stop clobbering builtin exceptions in a few places, and guard against NULL-returning functions some more. This fixes 117 of the 780 (!?!#%@#$!!) reference leaks in test_bsddb3. I ain't not done yet, although this review of 5kloc was just the easy part.
* Reformulate 42903 using an if statement.Martin v. Löwis2006-03-071-35/+31
|
* _hotshot hotshot_profiler(): If write_header() returnedTim Peters2006-03-071-1/+3
| | | | | | | | | | | | | | | | an error code, this let `self` leak. This is a disaster on Windows, since `self` already points to a newly-opened file object, and it was impossible for Python code to close the thing since the only reference to it was in a blob of leaked C memory. test_hotshot test_bad_sys_path(): This new test provoked the C bug above. This test passed, but left an open "@test" file behind, which caused a massive cascade of bogus test failures in later, unrelated tests on Windows. Changed the test code to remove the @test file it leaves behind, which relies on the change above to close that file first.
* Fix bug introduced in rev. 42884.Georg Brandl2006-03-071-3/+5
|
* Checking in the code for PEP 357.Guido van Rossum2006-03-073-35/+34
| | | | | | This was mostly written by Travis Oliphant. I've inspected it all; Neal Norwitz and MvL have also looked at it (in an earlier incarnation).
* SF #1444030: Fix several potential defects found by Coverity.Hye-Shik Chang2006-03-073-4/+10
| | | | (reviewed by Neal Norwitz)
* Add additional missing checks for return vals of PyTuple_New().Georg Brandl2006-03-071-66/+65
| | | | Normalize coding style.
* Fix gcc 4.0.x warning about use of uninitialized value.Thomas Wouters2006-03-071-1/+1
|
* Coverity found bug: test result of PyTuple_New() against NULL before use.Thomas Wouters2006-03-071-6/+6
| | | | Will backport.
* Coverity found refleak: need to free 'v' after calling Tkinter_Error().Thomas Wouters2006-03-071-2/+5
| | | | Will backport to release24.
* Coverity-found bug: don't use temp->next *before* checking it for NULL. AlsoThomas Wouters2006-03-071-2/+4
| | | | return rather than use it again.
* Bug #1432525: os.listdir now releases the GIL while callingGeorg Brandl2006-03-071-3/+15
| | | | readdir().
* Change int to Py_ssize_t in several places.Martin v. Löwis2006-03-071-4/+4
| | | | | Add (int) casts to silence compiler warnings. Raise Python exceptions for overflows.
* Don't DECREF a borrowed reference.Thomas Wouters2006-03-071-1/+0
|
* SF patch #1443865; gc.get_count() added and optional argument 'generation'Barry Warsaw2006-03-071-5/+34
| | | | | | added to gc.collect(). Updated docs, unit test, and NEWS entry. (Also, fixed a typo in NEWS.)
* Thanks to Coverity, these were all reported by their Prevent tool.Neal Norwitz2006-03-075-2/+12
| | | | | All of these (except _lsprof.c) should be backported. Particularly the hotshot change which validates sys.path. Can someone backport?
* Fix warnings on x86 (32-bit) and support Win64.Neal Norwitz2006-03-061-2/+15
|
* Check NULL if Py_InitModule fails.Hye-Shik Chang2006-03-061-1/+2
|
* Make PyGC_Collect() use Py_ssize_t.Neal Norwitz2006-03-041-11/+11
|
* - Modernize code to use Py_ssize_t more intensively.Hye-Shik Chang2006-03-0418-168/+131
| | | | - Do some minor code clean-ups.
* Explain why we use the unsigned int format for a signed int variable.Thomas Wouters2006-03-021-0/+4
| | | | (Should 'code' be cast to the right pointer type?)
* Properly fix Py_SAFE_DOWNCAST-triggerd bugs.Thomas Wouters2006-03-021-7/+10
|
* Py_SAFE_DOWNCAST isn't quite doing the right thing for going from Py_ssize_tThomas Wouters2006-03-021-7/+4
| | | | | | to an unsigned int (and back again) on 64-bit machines, even though the actual value of the Py_ssize_t variable is way below 31 bits. I suspect compiler-error.
* Make Py_ssize_t-cleanThomas Wouters2006-03-021-2/+4
|
* Remove UNLESS.Martin v. Löwis2006-03-011-29/+28
|
* Use Py_ssize_t for arithmetic on Py_ssize_t's, instead of unsigned ints.Thomas Wouters2006-03-011-2/+2
|
* Fix gcc (4.0.x) warning about use of uninitialized variable.Thomas Wouters2006-03-011-0/+1
|
* Patch #1440601: Add col_offset attribute to AST nodes.Martin v. Löwis2006-03-011-1/+1
|
* Rework channelnumber/samplesize detetion code's output variables a bit toThomas Wouters2006-03-012-14/+12
| | | | | convince gcc (4.0.x) the variables are never used uninitialized (and raising a proper exception if they ever are.)
* Silence gcc (4.0.x) warning about use of uninitialized value.Thomas Wouters2006-03-011-1/+1
|
* Fix brainfart.Thomas Wouters2006-03-011-1/+1
|
generated by cgit v0.12 at 2024-11-25 01:54:53 (GMT)