On 10/14/2013 10:38 AM, Werner F. Bruhin wrote:
On 14/10/2013 18:35, Paul McNett wrote:
On 10/14/13 3:39 AM, Werner F. Bruhin wrote:
What are the plans in supporting Python 3 for Dabo?
Um, you are in charge of that. :)
Haha
Do you want to support Py 2 and 3 with the same code base?
Ideally, yes. If it is going to be too tough to accomplish, the
fallback will be
maintaining two codebases.
From what I read up to now doing 2.7+ and 3.2+ in one code base should
be doable, it is also what Robin is shooting for with Phoenix and what
is also my reading of http://python3porting.com/noconv.html.
But if we could have a single codebase working with both:
python 2.7.7 and wxPython 2.8.12.1
python 3.1 + and wxPython Phoenix
I don't think that Robin plans to support 3.1, currently there are
snapshots for 2.7, 3.2 and 3.3.
Just to be sure, it is 2.8.12 and Phoenix and not 2.8.12, 3.0 Classic
and 3.0 Phoenix?
If the later then it would be:
Py 2.7x - wxPython 2.8.12, 3.0 Classic, 3.0 Phoenix
Py 3.2+ - wxPython 3.0 Phoenix
wxPython 3.0 Classic might be useful for people wanting to move to 3.0
but don't have the time to adjust to Phoenix.
BTW, I use the ReportDesigner and ReportWriter (obviously only a small
subset of Dabo) currently with the latest wxPython 2.9.5, so to
support 3.0 classic should hopefully not be too much additional work.
I am on Py 2.7.5, for the moment that is the only version I will work
on for Phoenix support at this point.
Werner
I have time to work on this for the next couple of days.
But I'm not to sure what the difference would be between the versions?
Johnf
_______________________________________________
Post Messages to: [email protected]
Subscription Maintenance: http://mail.leafe.com/mailman/listinfo/dabo-dev
Searchable Archives: http://leafe.com/archives/search/dabo-dev
This message: http://leafe.com/archives/byMID/[email protected]
