Comment 26 for bug 893091
Revision history for this message
|
|
#26 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
67d34a1
(Get the code!)
test-standalone.py now passes under 3.x however since the rest of the tests require pygobject we are kind of screwed until that is ported. We have a hackfest in Boston in April coming up to do just that. I might also provide alternate tests based on the busy loop dispatching code in libdbus if I have time. Also, apparently the 'sets' module doesn't seem to be available in 3.x.
As for 2.x everything seems to be running there fine. It still is passing tests and we even use the standard PyInt and PyString base classes so it should be API equivalent to the current bindings when compiled under 2.x (internally the PyDBusIntBase class now stores variant_level in its dict, the same way PyDBusLongBase does).
One question does remain. How do we handle the pure python files in a clean way? Do we run them through 2to3 during compile? Do we ship two different directories for 2.x and 3.x files? Do we move them to a src directory and on 2.x just move the file and on 3.x, run 2to3 and have them output to the module directory?