summaryrefslogtreecommitdiffstats
Commit message (Collapse)AuthorAgeFilesLines
* Patch #1468808: don't complain if Tkinter is already deleted at the time ↵Georg Brandl2006-04-121-1/+3
| | | | Font.__del__ is run.
* Add PEP 243 sectionAndrew M. Kuchling2006-04-121-1/+26
|
* Update test_sundry. Many modules have now tests, butGeorg Brandl2006-04-121-36/+12
| | | | e.g. SimpleXMLRPCServer wasn't in here yet.
* Note C API incompatibilitiesAndrew M. Kuchling2006-04-121-0/+32
|
* Mention access to ASTsAndrew M. Kuchling2006-04-121-1/+14
|
* Bug #1469163: SimpleXMLRPCServer unconditionally attempted to import fcntl.Anthony Baxter2006-04-122-2/+9
| | | | Wrapped in a try/except.
* Off-by-one buffer overflow error.Armin Rigo2006-04-121-1/+1
|
* Patch #1463288: use a context manager to temporarily switch locales.Walter Dörwald2006-04-122-30/+164
| | | | Add tests for the output of the TextCalendar and HTMLCalendar classes.
* wrap docstrings so they are less than 80 columns. add spaces after commas.Neal Norwitz2006-04-121-3/+5
|
* gen_throw(): The caller doesn't own PyArg_ParseTuple()Tim Peters2006-04-121-3/+1
| | | | | | "O" arguments, so must not decref them. This accounts for why running test_contextlib.test_main() in a loop eventually tried to deallocate Py_None.
* Update comments and the skip list, maybe some of these tests don'tNeal Norwitz2006-04-121-3/+10
| | | | | | | | | | | | report failures, we'll see. Skip certain hopeless tests: compiler and logging. compiler will likely always show varying leaks since it doesn't work on a defined set of modules unless -u compiler is specified. But that takes forever (we only run with -u network currently). logging causes hangs when running with -R.
* Add another little test to make sure we roundtrip multiple list comp ifs ok.Neal Norwitz2006-04-121-0/+4
| | | | Add tests for generator expressions too.
* Update for new grammarNeal Norwitz2006-04-121-4/+4
|
* put in a reference to PEP 306 in a comment at the topAnthony Baxter2006-04-121-0/+3
|
* Get rid of some warnings on MacNeal Norwitz2006-04-122-6/+3
|
* avoid C++ name mangling for the _Py.*SizeT functionsAnthony Baxter2006-04-121-0/+6
|
* remove forward declarations. No constructors to move for these files. MakesAnthony Baxter2006-04-122-6/+1
| | | | code work with C++ compilers.
* Move constructors, add some casts to make C++ compiler happy. Still a problemAnthony Baxter2006-04-121-202/+201
| | | | with the getstring() results in pattern_subx. Will come back to that.
* remove forward declarations, move constructor functions. makes code C++ safe.Anthony Baxter2006-04-121-43/+42
|
* Make symtable.c safe for C++ compilers. Changed macros in the same way asAnthony Baxter2006-04-121-11/+13
| | | | compile.c to add a cast.
* per Jeremy's email, remove the _WITH_CAST versions of macros. g++Anthony Baxter2006-04-121-46/+24
| | | | | still has errors from the casts of asdl_seq_GET to cmpop_ty, but otherwise it's C++ clean.
* Part two of the fix for SF bug #1466641: Regenerate graminit.c and add testThomas Wouters2006-04-122-2/+7
| | | | for the bogus failure.
* Fix SF bug #1466641: multiple adjacent 'if's in listcomps and genexps, as inThomas Wouters2006-04-121-2/+2
| | | | | [x for x in it if x if x], were broken for no good reason by the PEP 308 patch.
* Fix int() and long() to repr() their argument when formatting the exception,Thomas Wouters2006-04-112-6/+28
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | to avoid confusing situations like: >>> int("") ValueError: invalid literal for int(): >>> int("2\n\n2") ValueError: invalid literal for int(): 2 2 Also report the base used, to avoid: ValueError: invalid literal for int(): 2 They now report: >>> int("") ValueError: invalid literal for int() with base 10: '' >>> int("2\n\n2") ValueError: invalid literal for int() with base 10: '2\n\n2' >>> int("2", 2) ValueError: invalid literal for int() with base 2: '2' (Reporting the base could be avoided when base is 10, which is the default, but hrm.) Another effect of these changes is that the errormessage can be longer; before, it was cut off at about 250 characters. Now, it can be up to four times as long, as the unrepr'ed string is cut off at 200 characters, instead. No tests were added or changed, since testing for exact errormsgs is (pardon the pun) somewhat errorprone, and I consider not testing the exact text preferable. The actually changed code is tested frequent enough in the test_builtin test as it is (120 runs for each of ints and longs.)
* StreamHandler now checks explicitly for None before using sys.stderr as the ↵Vinay Sajip2006-04-111-1/+1
| | | | stream (see SF bug #1463840).
* _Py_PrintReferenceAddresses,_Py_PrintReferences:Tim Peters2006-04-111-7/+3
| | | | | | | | | | interpolate PY_FORMAT_SIZE_T for refcount display instead of casting refcounts to long. I understand that gcc on some boxes delivers nuisance warnings about this, but if any new ones appear because of this they'll get fixed by magic when the others get fixed.
* Complete the ElementTree sectionAndrew M. Kuchling2006-04-111-5/+32
|
* Some more changes to make code compile under a C++ compiler.Anthony Baxter2006-04-115-10/+11
|
* more low-hanging fruit to make code compile under a C++ compiler. NotAnthony Baxter2006-04-115-70/+102
| | | | | entirely happy with the two new VISIT macros in compile.c, but I couldn't see a better approach.
* Patch #1464444: Add --with-system-ffi.Martin v. Löwis2006-04-114-38/+98
|
* Convert 0 to their respective enum types. ConvertMartin v. Löwis2006-04-111-11/+11
| | | | | void* to their respective _ty types. Fix signature of ast_for_exprlist.
* Correct casts to char*.Martin v. Löwis2006-04-111-4/+4
|
* Remove "static forward" declaration. Move constructorsMartin v. Löwis2006-04-113-85/+79
| | | | after the type objects.
* Regenerate.Martin v. Löwis2006-04-111-2/+0
|
* As discussed on python-dev, really fix the PyMem_*/PyObject_* memory APINeal Norwitz2006-04-113-29/+29
| | | | | | | | | | | | | | | | mismatches. At least I hope this fixes them all. This reverts part of my change from yesterday that converted everything in Parser/*.c to use PyObject_* API. The encoding doesn't really need to use PyMem_*, however, it uses new_string() which must return PyMem_* for handling the result of PyOS_Readline() which returns PyMem_* memory. If there were 2 versions of new_string() one that returned PyMem_* for tokens and one that return PyObject_* for encodings that could also fix this problem. I'm not sure which version would be clearer. This seems to fix both Guido's and Phillip's problems, so it's good enough for now. After this change, it would be good to review Parser/*.c for consistent use of the 2 memory APIs.
* Make _kind types global for C++ compilation.Martin v. Löwis2006-04-113-20/+26
| | | | Explicitly cast void* to int to cmpop_ty.
* Get compiling againNeal Norwitz2006-04-111-1/+1
|
* low-hanging fruit in Python/ - g++ still hates all the enum_kind declarationsAnthony Baxter2006-04-114-22/+24
| | | | in Python/Python-ast.c. Not sure what to do about those.
* More low-hanging fruit. Still need to re-arrange some code (or find a betterAnthony Baxter2006-04-115-79/+80
| | | | | solution) in the same way as listobject.c got changed. Hoping for a better solution.
* C++ already defines a perfectly good 'bool'. Use that.Anthony Baxter2006-04-111-0/+2
|
* Adjust whitespace.Neal Norwitz2006-04-112-4/+4
|
* Add whitespace after commaNeal Norwitz2006-04-111-1/+1
|
* Correct test whether wchar_t is unsigned. Fixed crashMartin v. Löwis2006-04-112-3/+5
| | | | in #1454485.
* Clear errno before calling opendir() and readdir().Georg Brandl2006-04-111-0/+1
|
* More C++-compliance. Note especially listobject.c - to get C++ to accept theAnthony Baxter2006-04-118-136/+147
| | | | | | | | | PyTypeObject structures, I had to make prototypes for the functions, and move the structure definition ahead of the functions. I'd dearly like a better way to do this - to change this would make for a massive set of changes to the codebase. There's still some warnings - this is purely to get rid of errors first.
* Bug #1467952: os.listdir() now correctly raises an error if readdir()Georg Brandl2006-04-112-0/+9
| | | | fails with an error condition.
* Typo fix.Georg Brandl2006-04-111-1/+1
|
* Fix the code in Parser/ to also compile with C++. This was mostly casts forAnthony Baxter2006-04-117-36/+40
| | | | | | | malloc/realloc type functions, as well as renaming one variable called 'new' in tokensizer.c. Still lots more to be done, going to be checking in one chunk at a time or the patch will be massively huge. Still compiles ok with gcc.
* Try to repair what may be the last new test failure on theTim Peters2006-04-111-1/+15
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | "x86 OpenBSD trunk" buildbot due to changing Python so that Python-exposed addresses are always non-negative. test_int_pointer_arg(): This line failed now whenever the box happened to assign an address to `ci` "with the sign bit set": self.failUnlessEqual(addressof(ci), func(byref(ci))) The problem is that the ctypes addressof() inherited "all addresses are non-negative now" from changes to PyLong_FromVoidPtr(), but byref() did not inherit that change and can still return a negative int. I don't know whether, or what, the ctypes implementation wants to do about that (possibly nothing), but in the meantime the test fails frequently. So, introduced a Python positive_address() function in the test module, that takes a purported machine address and, if negative, converts it to a non-negative value "with the same bits". This should leave the test passing under all versions of Python. Belated thanks to Armin Rigo for teaching me the sick trick ;-) for determining the # of bits in a machine pointer via abuse of the struct module.
* subclasspropagation(): Squash two more bogus hash(x) == id(x)Tim Peters2006-04-111-2/+2
| | | | | | | tests. Alas, because only the "x86 OpenBSD trunk" buildbot fails these tests, and test_descr stops after the first failure, there's no sane way for me to fix these short of fixing one and then waiting for the buildbot to reveal the next one.