[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]
Re: [pygame] pygame for S60 update
Hi Jussi,
Good work. Contrary to my earlier argument that Python 2.3 compatibility
should be dropped, this is a good reason to keep backwards compatibility
in Pygame for the time being, even if it is for 2.2. It was mentioned in
an earlier post the Python will soon be updated on the S60. Any idea to
what version?
Jussi Toivola wrote:
2009/1/18 René Dudfield <renesd@xxxxxxxxx>:
[snip]
Do the tests run on the phone?
I haven't looked at the tests yet. Just tried to get the basics up
until now. I expected that they don't work out-of-the-box so those
would have taken too much of time. But now the port is complete enough
so I can start working on the details and removing the less obvious
bugs that the tests hopefully reveal.
The test aren't designed for Python 2.2. It will need patching in
unittest_patch.py.
A set() is used in TestTags.__call__():
combined = set()
A place in getTestCaseNames may pass a tuple to str.startswith() when
the --incomplete option is invoked:
def test_wanted(attrname, testCaseClass=testCaseClass,
prefix=self.testMethodPrefix):
if not attrname.startswith(prefix): return False # <== Here
else:
actual_attr = getattr(testCaseClass, attrname)
return (
callable(actual_attr) and
not [t for t in get_tags(actual_attr) if t in
self.exclude]
)
Also the subprocess option probably won't work. So just run the tests
without any options. Alternatively, they can be executed individually.
Lenard
--
Lenard Lindstrom
<len-l@xxxxxxxxx>