summaryrefslogtreecommitdiffstats
Commit message (Collapse)AuthorAgeFilesLines
* Fix comment for indenting in C files.Brett Cannon2006-08-311-1/+1
|
* Fix latex2html compile errorGeorge Yoshida2006-08-301-1/+1
|
* Get rid of more coerce cruft (really check in this time :-)Neal Norwitz2006-08-297-57/+2
|
* Get rid of more coerce cruft, update NEWSNeal Norwitz2006-08-291-6/+15
|
* Get parsermodule working again after adding set literalsNeal Norwitz2006-08-291-4/+4
|
* Fix another typo.Neal Norwitz2006-08-291-1/+1
|
* Get rid of some more cases of backquotes. parsermodule.c doesn't compileNeal Norwitz2006-08-296-17/+3
| | | | but looks like that was a problem before this change.
* Get rid of most of the remaining uses of <>. There's still Tools/* thogh.Neal Norwitz2006-08-2916-49/+23
|
* Fix str() and repr() of empty sets.Georg Brandl2006-08-282-5/+16
|
* Small fix for compiler module ./. set literals.Georg Brandl2006-08-281-1/+1
|
* Fix set literals not being visited in symtable creation.Georg Brandl2006-08-282-1/+4
|
* SF patch 1547796 by Georg Brandl -- set literals.Guido van Rossum2006-08-2822-72/+229
|
* Vestige of code from removing backticks.Brett Cannon2006-08-271-14/+0
| | | | Closes patch #1500623. Thanks, Collin Winter.
* Part of SF patch #1513870 (the still relevant part) -- add reduce() toGuido van Rossum2006-08-2611-78/+168
| | | | functools, and adjust docs etc.
* Inspired by SF patch #860326, make the exception formatting byGuido van Rossum2006-08-266-8/+13
| | | | | traceback.py be closer to the built-in formatting. A few unittests had to be fixed, too.
* The daily ritual: fix C89 violations.Guido van Rossum2006-08-261-2/+4
|
* Don't use a fixed temporary name (gdbm).Guido van Rossum2006-08-252-4/+4
| | | | | Don't use our own temp name creation (dbm). Should be backported to 2.5.
* SF patch 1546297 (with some tweaks):Guido van Rossum2006-08-253-15/+177
| | | | | Create a real zip iterator object; not using itertools.izip (Brian Holmes).
* Remove the UNARY_CONVERT opcode (was used for backticks). Also bumped up theBrett Cannon2006-08-2512-74/+4
| | | | import MAGIC number.
* Remove more '<>' usage.Brett Cannon2006-08-251-10/+10
| | | | | ``python -m compileall -f`` is really handy for finding Python files that use invalid syntax.
* Remove support for backticks from the grammar and compiler.Brett Cannon2006-08-257-154/+86
| | | | Still need to remove traces of the UNARY_CONVERT opcode.
* UNARY_CONVERT can no longer be generated, so remove a test for the peepholerBrett Cannon2006-08-251-1/+0
| | | | optimization for it.
* Change test of assignment of backticked expression to be an "invalid syntax"Brett Cannon2006-08-251-1/+1
| | | | | | | | | SyntaxError. This is probably not the proper solution to this failing test, but removing the test itself causes 19 other tests to fail for some odd reason because doctest doesn't expect a complete traceback (or something; rather odd problem for just removing a single test).
* Check in new output for test_tokenize.Brett Cannon2006-08-251-12/+13
|
* Switch to using %r in the format string.Brett Cannon2006-08-252-2/+2
|
* Don't test AST for backticks.Brett Cannon2006-08-251-3/+0
|
* The backtick removal crusade continues ...Brett Cannon2006-08-251-2/+2
|
* Remove usage of backticks.Brett Cannon2006-08-2513-16/+14
|
* Remove more '<>' usage.Brett Cannon2006-08-251-1/+1
|
* Back out rev. 51583 as this file is auto-generated. Obviously the program thatBrett Cannon2006-08-251-1/+1
| | | | auto-generates this file will need to get fixed.
* For some reason Vim was just not wanting to tell me there was more instances ofBrett Cannon2006-08-251-1/+1
| | | | '<>'.
* Even more removals of '<>'; I can hear Barry shedding a manly tear ...Brett Cannon2006-08-252-2/+2
|
* Remove a use of 'as' as a parameter.Brett Cannon2006-08-251-1/+1
|
* Remove some uses of '<>'.Brett Cannon2006-08-252-2/+2
|
* Get rid of all two uses of backticks (bad Jeremy!).Brett Cannon2006-08-242-2/+2
|
* Fix a bunch of compiler warnings. In at least one case these were serious bugs!Guido van Rossum2006-08-242-8/+8
|
* Got test_mutants.py working. One set of changes was straightforward:Guido van Rossum2006-08-242-23/+32
| | | | | | | | | use __eq__ instead of __cmp__. The other change is unexplained: with a random hash code as before, it would run forever; with a constant hash code, it fails quickly. This found a refcount bug in dict_equal() -- I wonder if that bug is also present in 2.5...
* Make built-in zip() equal to itertools.izip().Guido van Rossum2006-08-246-140/+63
| | | | | | | I mea, *really* equal -- for now, the implementation just imports itertools. :-) The only other changes necessary were various unit tests that were assuming zip() returns a real list. No "real" code made this assumption.
* Get rid of empty file.Guido van Rossum2006-08-241-1/+0
|
* Fix the bsddb3 unit tests.Guido van Rossum2006-08-242-7/+19
| | | | | | This essentially meant fixing one case where a list of custom objects was being sorted, and fixing one genuine bug where a method call was missing parentheses.
* Fix the datetime comparison conundrum.Guido van Rossum2006-08-242-120/+100
| | | | | The special-casing of other objects with a timetuple attribute is gone. Let's hope Tim agrees.
* Implement == and != comparisons for code objects by value.Guido van Rossum2006-08-241-39/+55
| | | | This makes test_codeop and test_marshal pass.
* Fix fallout from Anna's file -> open changes.Guido van Rossum2006-08-241-4/+6
|
* Killed the <> operator. You must now use !=.Guido van Rossum2006-08-2436-178/+171
| | | | | Opportunistically also fixed one or two places where '<> None' should be 'is not None' and where 'type(x) <> y' should be 'not isinstance(x, y)'.
* Anna Ravenscroft identified many occurrences of "file" used to open a fileAlex Martelli2006-08-2417-53/+53
| | | | | | in the stdlib and changed each of them to use "open" instead. At this time there are no other known occurrences that can be safely changed (in Lib and all subdirectories thereof).
* Fix another comparison between None and 0.Guido van Rossum2006-08-241-1/+2
|
* Make it compile with C89.Guido van Rossum2006-08-241-1/+2
|
* Restructure comparison dramatically. There is no longer a defaultGuido van Rossum2006-08-2457-899/+969
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | *ordering* between objects; there is only a default equality test (defined by an object being equal to itself only). Read the comment in object.c. The current implementation never uses a three-way comparison to compute a rich comparison, but it does use a rich comparison to compute a three-way comparison. I'm not quite done ripping out all the calls to PyObject_Compare/Cmp, or replacing tp_compare implementations with tp_richcompare implementations; but much of that has happened (to make most unit tests pass). The following tests still fail, because I need help deciding or understanding: test_codeop -- depends on comparing code objects test_datetime -- need Tim Peters' opinion test_marshal -- depends on comparing code objects test_mutants -- need help understanding it The problem with test_codeop and test_marshal is this: these tests compare two different code objects and expect them to be equal. Is that still a feature we'd like to support? I've temporarily removed the comparison and hash code from code objects, so they use the default (equality by pointer only) comparison. For the other two tests, run them to see for yourself. (There may be more failing test with "-u all".) A general problem with getting lots of these tests to pass is the reality that for object types that have a natural total ordering, implementing __cmp__ is much more convenient than implementing __eq__, __ne__, __lt__, and so on. Should we go back to allowing __cmp__ to provide a total ordering? Should we provide some other way to implement rich comparison with a single method override? Alex proposed a __key__() method; I've considered a __richcmp__() method. Or perhaps __cmp__() just shouldn't be killed off...
* Fix buglet in slice assignment of bytesobjects: assigning to b[3:0] ('stop'Thomas Wouters2006-08-232-0/+5
| | | | | being before 'start') would actually assign to b[0:0] (or whatever 'stop' was)
* Check for exceptions set by PyDict_GetItem().Jeremy Hylton2006-08-231-0/+2
|
generated by cgit v0.12 at 2024-11-30 17:13:28 (GMT)