By all means, let's make the python code compatible with both 2.6 and 3.x. What types of changes are required? -- D
Jeremy Cowles wrote: > That's not entirely true, you can keep one code base and support both 2.6 > and 3.x without too much effort. We are in the process of doing this now > with PyMW. > > Besides, the BOINC Python code must be upgraded at /some/ point; I know that > doesn't need to be today, but this problem isn't going to go away. > > -- > Jeremy > > > > 2010/6/19 Nicolás Alvarez <[email protected]> > >> On 6/19/10, Jeremy Cowles <[email protected]> wrote: >>> We are in the midst of porting PyMW to Python 3. During this process, I >>> realized that we can't fully support Python 3 unless BOINC supports it as >>> well. >>> >>> I'm assuming BOINC does not support Python 3 currently, is there a plan >> for >>> it in the future? >>> >>> Having done this conversion with PyMW, I am willing to help out with the >>> transition, if extra brain/code is needed :) >> Python3 is not backwards-compatible. You would need a lot of redundant >> code and version checks to keep code compatible with *both* 2.x and >> 3.x; and I doubt devs are willing to require projects to upgrade to >> Python 3.x... >> >> -- >> Nicolas >> > _______________________________________________ > boinc_dev mailing list > [email protected] > http://lists.ssl.berkeley.edu/mailman/listinfo/boinc_dev > To unsubscribe, visit the above URL and > (near bottom of page) enter your email address. _______________________________________________ boinc_dev mailing list [email protected] http://lists.ssl.berkeley.edu/mailman/listinfo/boinc_dev To unsubscribe, visit the above URL and (near bottom of page) enter your email address.
