e06b6b8ff5
Fix a leak and a buglet discovered by Thomas.
...
Get rid of silly lambdas in the unit test suite.
Add a TODO list to the unit test suite (TDD style).
2006-04-23 07:43:54 +00:00
5f6f27de4d
Fix test_main function so test_bytes can be run by regrtest.py.
2006-04-23 00:19:58 +00:00
4dfe8a1131
Here is a bytes type. It's very minimal but it's a start.
2006-04-22 23:28:04 +00:00
d603f645d9
Delete test_coercion.py. Coercion is dead, so this test is useless.
...
(Plus, it fails. :-)
2006-04-22 17:37:27 +00:00
d4ec0c3e2c
Merge with trunk up to revision 45620.
2006-04-21 16:44:05 +00:00
6da48561cb
Fix test_scriptpackage with pure will power.
...
I really don't know why I bother; these are all generated files.
But I don't recall how to regenerate them nor how to fix the generator.
The hardest part was fixing two mutual recursive imports;
somehow changing "import foo" into "from . import foo" where
foo and bar import each other AND both are imported from __init__.py
caused things to break. Bah.
2006-04-21 15:44:20 +00:00
7ec155f5be
Fix relative import. This fixes test_sax.py.
2006-04-21 13:52:56 +00:00
e4dea98e5a
Fix the unit tests by adding dispatch tables for DateTime and Binary.
...
I'm not convinced this is the right thing to do... InstanceType makes no sense any longer.
2006-04-21 13:45:00 +00:00
d8073285ff
Fix newly merged test for p3ykness.
2006-04-21 11:36:13 +00:00
dcc6d32ee4
Fix merge glitch.
2006-04-21 11:30:52 +00:00
49fd7fa443
Merge p3yk branch with the trunk up to revision 45595. This breaks a fair
...
number of tests, all because of the codecs/_multibytecodecs issue described
here (it's not a Py3K issue, just something Py3K discovers):
http://mail.python.org/pipermail/python-dev/2006-April/064051.html
Hye-Shik Chang promised to look for a fix, so no need to fix it here. The
tests that are expected to break are:
test_codecencodings_cn
test_codecencodings_hk
test_codecencodings_jp
test_codecencodings_kr
test_codecencodings_tw
test_codecs
test_multibytecodec
This merge fixes an actual test failure (test_weakref) in this branch,
though, so I believe merging is the right thing to do anyway.
2006-04-21 10:40:58 +00:00
9ada3d6e29
Merge trunk up to 43069, putting re.py back and hopefully making the branch
...
usable again.
2006-04-21 09:47:09 +00:00
725ccd1810
Merge trunk's 43068, deleting re.py. This leaves the branch in a broken
...
state (unless you happen to have a re.pyc lying around), but it'll be fixed
in the next merge.
2006-04-21 09:46:12 +00:00
a977329b6f
Merge part of the trunk changes into the p3yk branch. This merges from 43030
...
(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 ;)
2006-04-21 09:43:23 +00:00
d858f70617
Fix the problems in this test. Boy this is a painful thing to debug --
...
it's fundamentally unmaintainable. Should we throw away pyclbr, or rewrite
it using the AST?
2006-04-21 09:17:15 +00:00
303de6a25b
Fix (and add test for) missing check for BaseException subclasses in the C
...
API.
2006-04-20 22:42:37 +00:00
4f564bd68a
Fix typical truedivision problem (using the result of division as an index.)
2006-04-20 22:36:57 +00:00
a48a3b42dd
Fix test failures for repr.py.
...
But shouldn't we kill this module? How many pprint clones do we need?
2006-04-20 16:07:39 +00:00
08a1a9fac7
Use explicit relative import for an, ehm, relative import.
2006-04-18 21:41:36 +00:00
7ea7d90dbe
Fix the expected output file; new classes just behave differently...
...
(There are some other problems with test_class.py that aren't as
easily fixed. :-( )
2006-04-17 23:38:13 +00:00
69e8084ad6
Fix two errors that prevented "make libinstall" from working:
...
- a line indented with tabs;
- a function named 'as'.
2006-04-17 23:13:00 +00:00
07519f8712
Fix xrange tests now that xrange() (like many other places) no longer
...
silently converts floats to integers when expecting integer values.
2006-04-17 13:16:50 +00:00
4cdada9af6
Make test_class work (but still fail) even though class.__dict__ is now a
...
'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.
2006-04-15 09:19:16 +00:00
1034dadf1f
Adjust test_enumerate to accomodate for iter() blowing up sooner than
...
expected, when dealing with new-style broken-iterators.
2006-04-15 09:16:16 +00:00
c947123350
Fix tests for PyArg_Parse*; The PyArg_Parse functions no longer (noisily)
...
convert float arguments to integer-taking format characters, so fix the test
to expect the failure.
2006-04-15 09:15:11 +00:00
725af87d0a
- Remove tests for classic class behaviour
...
- Expect a new-style class tree in the getclasstree test.
2006-04-15 09:13:19 +00:00
1ae9afa829
Fix test_bisect in the same way as test_itertools: iter() blows up a lot
...
sooner for new-style broken-iterators, expect it to.
2006-04-15 09:12:14 +00:00
34729030a7
Fix the superficial augmented-assignment tests to deal with true division.
...
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
2006-04-15 09:10:43 +00:00
8690c4ed3f
Fix tests that were trying to make iteration blow up, on broken iterators.
...
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.
2006-04-15 09:07:20 +00:00
0725cf2127
Remove tests for classic-class and mixed-classic-class/new-style behaviour.
...
(New-style class behaviour was already thoroughly tested)
2006-04-15 09:04:57 +00:00
28bc768977
- Fix doctest results to account for classes being new-style, and thus
...
printing differently.
- Fix doctest for classic-class behaviour, make it test new-style behaviour
on an implicitly-new-style class instead.
2006-04-15 09:03:16 +00:00
c6fe059512
Use absolute import. (Should this go into 2.5?)
2006-03-24 08:57:54 +00:00
bcc0db82dc
Get rid of remnants of integer division
2006-03-24 08:14:36 +00:00
ed483ba63b
String exceptions are gone and so are classic classes.
2006-03-24 08:08:49 +00:00
28c31982eb
Use *absolute* imports now that they are required. (Should this go into 2.5?)
2006-03-24 08:04:47 +00:00
1e32b6927f
Must inherit from Exception now.
2006-03-24 08:02:35 +00:00
2def11a90d
Use *absolute* imports now that they are required. (Should this go into 2.5?)
2006-03-24 07:47:46 +00:00
c3e54b8480
Use *absolute* import now that it is required. (Should this go into 2.5? Hopefully not the bogus comment about using relative imports. That was just to see if anyone was paying attention.)
2006-03-24 07:38:37 +00:00
16d6510425
Use relative import now that it is required. (Should this go into 2.5?)
2006-03-24 07:35:29 +00:00
2a0c7801a5
Use relative import now that it is required. (Should this go into 2.5?)
2006-03-24 07:10:31 +00:00
2b499436b5
Ok, compiler.transformer can really be imported now
2006-03-24 07:07:34 +00:00
0fb43762d5
Must inherit from Exception now.
2006-03-24 07:02:16 +00:00
ef4f7f0298
Use relative import now that it is required. (Should this go into 2.5?)
2006-03-24 06:59:24 +00:00
abdbeff36e
Use relative imports in compiler package now that it is required. (Should this go into 2.5 or should we do compiler.XXX?)
2006-03-24 06:57:41 +00:00
a0bc30f36f
Remove another use of as as a keyword
2006-03-22 09:34:44 +00:00
914a81841f
Get doctest to pass. The problem was int/int -> float now. There
...
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.
2006-03-22 09:20:30 +00:00
f84c38a39a
Damn another occurrence of using as as a keywordf
2006-03-22 07:12:41 +00:00
e7086d409e
INPLACE_DIVIDE is no longer necessary (INPLACE_TRUE_DIVIDE is used).
2006-03-17 08:59:09 +00:00
bd2835c6ae
as is a keyword now :-)
2006-03-17 08:54:15 +00:00
7096760b25
Get rid of xreadlines() (methods).
2006-03-17 08:29:44 +00:00
Guido van Rossum
Thomas Wouters
Neal Norwitz