On Dec 4, 10:59 am, "Edward K. Ream" <[EMAIL PROTECTED]> wrote:
> I am about to push to the trunk changes to make Leo's code base
> syntactically compatible with Python 3.0. However, neither PyQt4 nor
> Tkinter appear to be ready for Py3k.
>
> Furthermore, running Leo on Python 2.6 generates several warnings, so
> for now I'll concentrate on getting everything to run cleanly on
> Python 2.6.
Some updates:
1. Phil Thompson of Riverbank Computing said in response to my
question that Qt will be ported to Python 3.0 in about four months.
This seems reasonable to me. So my choice is to wait until then to
work on Leo3K, or to port Pmw to Py3K now. I doubt that many people
will care much one way or the other.
2. The warnings generated by python 2.6 with the -3 option enabled had
to do with the ast module, which does not exist in Py3K. So it looks
like Leo's code base is clean, provided that the g.isPython3 constant
is used to distinguish between modules that do and don't exist in
Py3k.
I'm about to suggest to the Python folk that their -3 warnings in such
cases could be clearer, but that's a nit.
Edward
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"leo-editor" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/leo-editor?hl=en
-~----------~----~----~----~------~----~------~--~---
