I agree with Jed, I think this is the time to branch 2.2 and leave the
work on python3 for 2.3. Else it would take us longer to release 2.2,
when I think we've almost finished all things left to be done.
Cheers,
Carlos
El 28/12/12 11:51, Jed Ludlow escribió:
I've just been able to run the application without an (immediate)
error:
http://spyderlib.googlecode.com/files/spyder_python3-1.png
It's quite encouraging but I think there are a lot of remaining
issues.
I won't push too far on the v21 branch but it's very useful to proceed
like this: I will use the recent changelog of this branch as a
checklist to migrate the default Hg branch.
From a logistical perspective, are you thinking of a 2.2 release prior
to the Python 3 migration? If so, it may make sense to either clone
the default repository to a v22 or create a named v22 branch inside of
the default repo before the Python 3 migration work. I guess I'm
wondering how much destabilization you expect from the Python 3 migration.
Either way, I would agree with your earlier suggestion that we finish
the integration of any major outstanding work before committing any
Python 3 compatibility changes to the default repo. I've queued up a
few for review.
--
You received this message because you are subscribed to the Google
Groups "spyder" 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/spyderlib?hl=en.
--
You received this message because you are subscribed to the Google Groups
"spyder" 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/spyderlib?hl=en.
