summaryrefslogtreecommitdiffstats
Commit message (Collapse)AuthorAgeFilesLines
* Merge part of the trunk changes into the p3yk branch. This merges from 43030Thomas Wouters2006-04-21116-704/+3404
| | | | | | | | | | | | (branch-creation time) up to 43067. 43068 and 43069 contain a little swapping action between re.py and sre.py, and this mightily confuses svn merge, so later changes are going in separately. This merge should break no additional tests. The last-merged revision is going in a 'last_merge' property on '.' (the branch directory.) Arbitrarily chosen, really; if there's a BCP for this, I couldn't find it, but we can easily change it afterwards ;)
* Fix the problems in this test. Boy this is a painful thing to debug --Guido van Rossum2006-04-211-1/+3
| | | | | it's fundamentally unmaintainable. Should we throw away pyclbr, or rewrite it using the AST?
* Fix (and add test for) missing check for BaseException subclasses in the CThomas Wouters2006-04-202-1/+28
| | | | API.
* Fix typical truedivision problem (using the result of division as an index.)Thomas Wouters2006-04-201-2/+2
|
* Fix test failures for repr.py.Guido van Rossum2006-04-202-16/+10
| | | | But shouldn't we kill this module? How many pprint clones do we need?
* Use explicit relative import for an, ehm, relative import.Thomas Wouters2006-04-181-1/+1
|
* Fix the expected output file; new classes just behave differently...Guido van Rossum2006-04-171-39/+5
| | | | | (There are some other problems with test_class.py that aren't as easily fixed. :-( )
* Fix two errors that prevented "make libinstall" from working:Guido van Rossum2006-04-172-3/+3
| | | | | - a line indented with tabs; - a function named 'as'.
* Fix xrange tests now that xrange() (like many other places) no longerThomas Wouters2006-04-171-1/+4
| | | | silently converts floats to integers when expecting integer values.
* Mention how __coerce__ has been removed.Brett Cannon2006-04-151-0/+2
|
* Make test_class work (but still fail) even though class.__dict__ is now aThomas Wouters2006-04-151-2/+5
| | | | | | | | 'dictproxy' (which is a read-only non-dict mapping type that can't be passed to exec.) The failures the test finds are behavioural differences between old- and new-style classes that may or may not be intended.
* Adjust test_enumerate to accomodate for iter() blowing up sooner thanThomas Wouters2006-04-151-1/+1
| | | | expected, when dealing with new-style broken-iterators.
* Fix tests for PyArg_Parse*; The PyArg_Parse functions no longer (noisily)Thomas Wouters2006-04-151-6/+6
| | | | | convert float arguments to integer-taking format characters, so fix the test to expect the failure.
* - Remove tests for classic class behaviourThomas Wouters2006-04-151-77/+7
| | | | - Expect a new-style class tree in the getclasstree test.
* Fix test_bisect in the same way as test_itertools: iter() blows up a lotThomas Wouters2006-04-151-2/+2
| | | | sooner for new-style broken-iterators, expect it to.
* Fix the superficial augmented-assignment tests to deal with true division.Thomas Wouters2006-04-152-10/+22
| | | | | | Add (equally superficial) >>=/<<= test in the process. Relies on floats that should be extremely close to the int '6' printing as '6.0', but I believe that's a valid assumption ;P
* Fix tests that were trying to make iteration blow up, on broken iterators.Thomas Wouters2006-04-151-12/+12
| | | | | | Since the broken iterators are now new-style classes, iter() was able to do the valid-iterator check sooner (on instantiation instead of on first call), making the tests blow up sooner than expected.
* Remove tests for classic-class and mixed-classic-class/new-style behaviour.Thomas Wouters2006-04-151-146/+2
| | | | (New-style class behaviour was already thoroughly tested)
* - Fix doctest results to account for classes being new-style, and thusThomas Wouters2006-04-151-9/+9
| | | | | | printing differently. - Fix doctest for classic-class behaviour, make it test new-style behaviour on an implicitly-new-style class instead.
* Make 'python -tt' the default, meaning Python won't allow mixing tabs andThomas Wouters2006-04-142-46/+8
| | | | | | | | spaces for indentation. Adds a '-ttt' option to turn the errors back into warnings; I'm not yet sure whether that's desireable for Py3K. Also remove the magic for setting the size of tabs based on emacs/vim-style comments. Python now always considers tabstops to be every-8-spaces.
* Fix the version number to be 3.0.Guido van Rossum2006-03-302-12/+12
|
* Use absolute import. (Should this go into 2.5?)Neal Norwitz2006-03-241-1/+1
|
* Get rid of remnants of integer divisionNeal Norwitz2006-03-2428-212/+47
|
* String exceptions are gone and so are classic classes.Neal Norwitz2006-03-241-40/+0
|
* Use *absolute* imports now that they are required. (Should this go into 2.5?)Neal Norwitz2006-03-241-1/+1
|
* Must inherit from Exception now.Neal Norwitz2006-03-241-1/+1
|
* Use *absolute* imports now that they are required. (Should this go into 2.5?)Neal Norwitz2006-03-243-9/+9
|
* Use *absolute* import now that it is required. (Should this go into 2.5? ↵Neal Norwitz2006-03-241-1/+1
| | | | Hopefully not the bogus comment about using relative imports. That was just to see if anyone was paying attention.)
* Use relative import now that it is required. (Should this go into 2.5?)Neal Norwitz2006-03-241-1/+1
|
* Use relative import now that it is required. (Should this go into 2.5?)Neal Norwitz2006-03-241-1/+1
|
* Ok, compiler.transformer can really be imported nowNeal Norwitz2006-03-243-6/+6
|
* Must inherit from Exception now.Neal Norwitz2006-03-241-2/+2
|
* Use relative import now that it is required. (Should this go into 2.5?)Neal Norwitz2006-03-241-1/+2
|
* Use relative imports in compiler package now that it is required. (Should ↵Neal Norwitz2006-03-241-3/+3
| | | | this go into 2.5 or should we do compiler.XXX?)
* Remove another use of as as a keywordNeal Norwitz2006-03-221-5/+5
|
* Finish getting rid of statichere/staticforwardNeal Norwitz2006-03-228-25/+25
|
* Get doctest to pass. The problem was int/int -> float now. ThereNeal Norwitz2006-03-221-11/+11
| | | | | | | | | | were some cases where an int was assumed. Also had to change the string of the exception when dividing and int by zero. Not sure what the best error message should be. Currently 5 / 0 yields the message: ZeroDivisionError: float division That isn't entirely correct. But I'm not sure what else to do.
* Remove staticforward and statichereNeal Norwitz2006-03-223-18/+5
|
* Damn another occurrence of using as as a keywordfNeal Norwitz2006-03-221-2/+2
|
* remove test fileBarry Warsaw2006-03-211-1/+0
|
* testing svn emailsBarry Warsaw2006-03-211-1/+1
|
* testing svn emailsBarry Warsaw2006-03-211-1/+1
|
* testing svn emailsBarry Warsaw2006-03-211-1/+1
|
* testing svn emailsBarry Warsaw2006-03-211-1/+1
|
* testing svn emailsBarry Warsaw2006-03-211-1/+1
|
* testing svn emailsBarry Warsaw2006-03-211-1/+1
|
* testing svn emailsBarry Warsaw2006-03-211-0/+1
|
* Some more TODO items of things I'd like to start with.Guido van Rossum2006-03-201-1/+17
| | | | Mention the builtins that Neal killed.
* Remove PyArg_NoArgs() and PyArg_GetInt()Neal Norwitz2006-03-173-11/+2
|
* INPLACE_DIVIDE is no longer necessary (INPLACE_TRUE_DIVIDE is used).Neal Norwitz2006-03-175-9/+3
|