Comment 28 for bug 893091
Revision history for this message
|
|
#28 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
0e1f616
(Get the code!)
(In reply to comment #21)
This is the correct place for patches. I use Bytes there because the spec only allows characters in the ASCII range (it is mapped to String for Python 2.x). I have no issue with having it be Unicode for 3.x though.
As for the Python source files I haven't decided how we want to handle 2.x compatibility. It was my thought that the build would run 2to3 on intermediate files. The source needs to run on at least Python 2.5 if not 2.4. We want to merge into master as soon as possible.
In any case I'm working with pygi right now but once I am done I plan on running the test cases using the new py3k branch of pygobject. I will also decide how we are going to support 2.x and 3.x from the same source at this time.