Hi wxPythoners
I have delayed any learning process on Python 3 due to few modules.
One of critical modules for me is the wxPython. Is Robin and the team
planning to release any? I currently stick to my old best friend,
Python 2.5.4
Thanks!
Hi,
2009/8/2 evstevemd:
Hi wxPythoners
I have delayed any learning process on Python 3 due to few modules.
One of critical modules for me is the wxPython. Is Robin and the team
planning to release any? I currently stick to my old best friend,
Python 2.5.4
This subject comes out quite often in the mailing list. I don't think
Robin has done major works on wxPython in the direction of supporting
Python 3, and preliminary support *might* be available towards
wxPython 3.0 (as far as I remember, please someone correct me if I am
saying stupid things).
As far as I am concerned, I have run a hacked version of the
slooooooooow 2to3.py script in Python 2.6 on the wxPython library: it
came up with approximately 1560 "inconsistencies" which will need to
be corrected to support Python 3 (if anyone is interested in the 2to3
results please let me know). Not to mention, obviously, that possibly
some major work may be done on the SWIG interfaces (although I am not
sure) and backward compatibility with Python 2.X (which is still the
version used by the vast majority of programmers) will be problematic.
Other than that, none of the major libraries that I know of have been
ported to Python 3.
Andrea.
"Imagination Is The Only Weapon In The War Against Reality."
http://xoomer.alice.it/infinity77/
Thanks Andrea
···
On Aug 2, 12:30 pm, Andrea Gavana <andrea.gav...@gmail.com> wrote:
Hi,
2009/8/2 evstevemd:
> Hi wxPythoners
> I have delayed any learning process on Python 3 due to few modules.
> One of critical modules for me is the wxPython. Is Robin and the team
> planning to release any? I currently stick to my old best friend,
> Python 2.5.4This subject comes out quite often in the mailing list. I don't think
Robin has done major works on wxPython in the direction of supporting
Python 3, and preliminary support *might* be available towards
wxPython 3.0 (as far as I remember, please someone correct me if I am
saying stupid things).As far as I am concerned, I have run a hacked version of the
slooooooooow 2to3.py script in Python 2.6 on the wxPython library: it
came up with approximately 1560 "inconsistencies" which will need to
be corrected to support Python 3 (if anyone is interested in the 2to3
results please let me know). Not to mention, obviously, that possibly
some major work may be done on the SWIG interfaces (although I am not
sure) and backward compatibility with Python 2.X (which is still the
version used by the vast majority of programmers) will be problematic.Other than that, none of the major libraries that I know of have been
ported to Python 3.Andrea.
"Imagination Is The Only Weapon In The War Against Reality."http://xoomer.alice.it/infinity77/http://thedoomedcity.blogspot.com/
The only major library I can think of off the top of my head that has
support for 2.x and 3.x is PyWin32. I don't know how Mark H. et al do
it, but they did.
It looks like Django is working on 3.0 support, but they say it will
take 1-2 years to complete the transition. TurboGears can't do
anything until it gets upstream support.
- Mike
···
On Aug 2, 4:30 am, Andrea Gavana <andrea.gav...@gmail.com> wrote:
Hi,
2009/8/2 evstevemd:
> Hi wxPythoners
> I have delayed any learning process on Python 3 due to few modules.
> One of critical modules for me is the wxPython. Is Robin and the team
> planning to release any? I currently stick to my old best friend,
> Python 2.5.4This subject comes out quite often in the mailing list. I don't think
Robin has done major works on wxPython in the direction of supporting
Python 3, and preliminary support *might* be available towards
wxPython 3.0 (as far as I remember, please someone correct me if I am
saying stupid things).As far as I am concerned, I have run a hacked version of the
slooooooooow 2to3.py script in Python 2.6 on the wxPython library: it
came up with approximately 1560 "inconsistencies" which will need to
be corrected to support Python 3 (if anyone is interested in the 2to3
results please let me know). Not to mention, obviously, that possibly
some major work may be done on the SWIG interfaces (although I am not
sure) and backward compatibility with Python 2.X (which is still the
version used by the vast majority of programmers) will be problematic.Other than that, none of the major libraries that I know of have been
ported to Python 3.Andrea.
pygame 1.9.0 is now support 3.1 but only for window platform so far.
···
On Aug 3, 1:40 pm, Mike Driscoll <kyoso...@gmail.com> wrote:
On Aug 2, 4:30 am, Andrea Gavana <andrea.gav...@gmail.com> wrote:
> Hi,
> 2009/8/2 evstevemd:
> > Hi wxPythoners
> > I have delayed any learning process on Python 3 due to few modules.
> > One of critical modules for me is the wxPython. Is Robin and the team
> > planning to release any? I currently stick to my old best friend,
> > Python 2.5.4> This subject comes out quite often in the mailing list. I don't think
> Robin has done major works on wxPython in the direction of supporting
> Python 3, and preliminary support *might* be available towards
> wxPython 3.0 (as far as I remember, please someone correct me if I am
> saying stupid things).> As far as I am concerned, I have run a hacked version of the
> slooooooooow 2to3.py script in Python 2.6 on the wxPython library: it
> came up with approximately 1560 "inconsistencies" which will need to
> be corrected to support Python 3 (if anyone is interested in the 2to3
> results please let me know). Not to mention, obviously, that possibly
> some major work may be done on the SWIG interfaces (although I am not
> sure) and backward compatibility with Python 2.X (which is still the
> version used by the vast majority of programmers) will be problematic.> Other than that, none of the major libraries that I know of have been
> ported to Python 3.> Andrea.
The only major library I can think of off the top of my head that has
support for 2.x and 3.x is PyWin32. I don't know how Mark H. et al do
it, but they did.It looks like Django is working on 3.0 support, but they say it will
take 1-2 years to complete the transition. TurboGears can't do
anything until it gets upstream support.- Mike
pyqt supports python 2 and python 3.
coffeeGT wrote:
···
pygame 1.9.0 is now support 3.1 but only for window platform so far.
On Aug 3, 1:40 pm, Mike Driscoll <kyoso...@gmail.com> wrote:
On Aug 2, 4:30 am, Andrea Gavana <andrea.gav...@gmail.com> wrote:
Hi,
2009/8/2 evstevemd:Hi wxPythoners
I have delayed any learning process on Python 3 due to few modules.
One of critical modules for me is the wxPython. Is Robin and the team
planning to release any? I currently stick to my old best friend,
Python 2.5.4This subject comes out quite often in the mailing list. I don't think
Robin has done major works on wxPython in the direction of supporting
Python 3, and preliminary support *might* be available towards
wxPython 3.0 (as far as I remember, please someone correct me if I am
saying stupid things).
As far as I am concerned, I have run a hacked version of the
slooooooooow 2to3.py script in Python 2.6 on the wxPython library: it
came up with approximately 1560 "inconsistencies" which will need to
be corrected to support Python 3 (if anyone is interested in the 2to3
results please let me know). Not to mention, obviously, that possibly
some major work may be done on the SWIG interfaces (although I am not
sure) and backward compatibility with Python 2.X (which is still the
version used by the vast majority of programmers) will be problematic.
Other than that, none of the major libraries that I know of have been
ported to Python 3.
Andrea.The only major library I can think of off the top of my head that has
support for 2.x and 3.x is PyWin32. I don't know how Mark H. et al do
it, but they did.It looks like Django is working on 3.0 support, but they say it will
take 1-2 years to complete the transition. TurboGears can't do
anything until it gets upstream support.- Mike
>
pyqt supports python 2 and python 3.
That reminds me of a glaring omission on my part: Tkinter. Oh well...I
know they exist, but there's just not that many out yet. Thanks for
the info!
- Mike
···
On Aug 4, 12:34 am, "Stephen M. Gava" <elgua...@python.net> wrote:
coffeeGT wrote:
> pygame 1.9.0 is now support 3.1 but only for window platform so far.> On Aug 3, 1:40 pm, Mike Driscoll <kyoso...@gmail.com> wrote:
>> On Aug 2, 4:30 am, Andrea Gavana <andrea.gav...@gmail.com> wrote:>>> Hi,
>>> 2009/8/2 evstevemd:
>>>> Hi wxPythoners
>>>> I have delayed any learning process on Python 3 due to few modules.
>>>> One of critical modules for me is the wxPython. Is Robin and the team
>>>> planning to release any? I currently stick to my old best friend,
>>>> Python 2.5.4
>>> This subject comes out quite often in the mailing list. I don't think
>>> Robin has done major works on wxPython in the direction of supporting
>>> Python 3, and preliminary support *might* be available towards
>>> wxPython 3.0 (as far as I remember, please someone correct me if I am
>>> saying stupid things).
>>> As far as I am concerned, I have run a hacked version of the
>>> slooooooooow 2to3.py script in Python 2.6 on the wxPython library: it
>>> came up with approximately 1560 "inconsistencies" which will need to
>>> be corrected to support Python 3 (if anyone is interested in the 2to3
>>> results please let me know). Not to mention, obviously, that possibly
>>> some major work may be done on the SWIG interfaces (although I am not
>>> sure) and backward compatibility with Python 2.X (which is still the
>>> version used by the vast majority of programmers) will be problematic.
>>> Other than that, none of the major libraries that I know of have been
>>> ported to Python 3.
>>> Andrea.
>> The only major library I can think of off the top of my head that has
>> support for 2.x and 3.x is PyWin32. I don't know how Mark H. et al do
>> it, but they did.>> It looks like Django is working on 3.0 support, but they say it will
>> take 1-2 years to complete the transition. TurboGears can't do
>> anything until it gets upstream support.>> - Mike
Wow, pyqt support 3 too? Really hope wxPython can catch it up
quickly....
···
On Aug 4, 10:29 am, Mike Driscoll <kyoso...@gmail.com> wrote:
On Aug 4, 12:34 am, "Stephen M. Gava" <elgua...@python.net> wrote:
> pyqt supports python 2 and python 3.
That reminds me of a glaring omission on my part: Tkinter. Oh well...I
know they exist, but there's just not that many out yet. Thanks for
the info!- Mike
> coffeeGT wrote:
> > pygame 1.9.0 is now support 3.1 but only for window platform so far.> > On Aug 3, 1:40 pm, Mike Driscoll <kyoso...@gmail.com> wrote:
> >> On Aug 2, 4:30 am, Andrea Gavana <andrea.gav...@gmail.com> wrote:> >>> Hi,
> >>> 2009/8/2 evstevemd:
> >>>> Hi wxPythoners
> >>>> I have delayed any learning process on Python 3 due to few modules.
> >>>> One of critical modules for me is the wxPython. Is Robin and the team
> >>>> planning to release any? I currently stick to my old best friend,
> >>>> Python 2.5.4
> >>> This subject comes out quite often in the mailing list. I don't think
> >>> Robin has done major works on wxPython in the direction of supporting
> >>> Python 3, and preliminary support *might* be available towards
> >>> wxPython 3.0 (as far as I remember, please someone correct me if I am
> >>> saying stupid things).
> >>> As far as I am concerned, I have run a hacked version of the
> >>> slooooooooow 2to3.py script in Python 2.6 on the wxPython library: it
> >>> came up with approximately 1560 "inconsistencies" which will need to
> >>> be corrected to support Python 3 (if anyone is interested in the 2to3
> >>> results please let me know). Not to mention, obviously, that possibly
> >>> some major work may be done on the SWIG interfaces (although I am not
> >>> sure) and backward compatibility with Python 2.X (which is still the
> >>> version used by the vast majority of programmers) will be problematic.
> >>> Other than that, none of the major libraries that I know of have been
> >>> ported to Python 3.
> >>> Andrea.
> >> The only major library I can think of off the top of my head that has
> >> support for 2.x and 3.x is PyWin32. I don't know how Mark H. et al do
> >> it, but they did.> >> It looks like Django is working on 3.0 support, but they say it will
> >> take 1-2 years to complete the transition. TurboGears can't do
> >> anything until it gets upstream support.> >> - Mike
Wow, pyqt support 3 too? Really hope wxPython can catch it up
quickly....
Well, the people behind pyqt sell commercial versions and support. So
in a way, they are paid to keep pyqt up to date, whereas the people
behind wxPython are not. They do all their programming on a volunteer
basis.
- Mike
···
On Aug 4, 3:12 pm, coffeeGT <pytho...@gmail.com> wrote:
On Aug 4, 10:29 am, Mike Driscoll <kyoso...@gmail.com> wrote:
> On Aug 4, 12:34 am, "Stephen M. Gava" <elgua...@python.net> wrote:
> > pyqt supports python 2 and python 3.
> That reminds me of a glaring omission on my part: Tkinter. Oh well...I
> know they exist, but there's just not that many out yet. Thanks for
> the info!> - Mike
> > coffeeGT wrote:
> > > pygame 1.9.0 is now support 3.1 but only for window platform so far.> > > On Aug 3, 1:40 pm, Mike Driscoll <kyoso...@gmail.com> wrote:
> > >> On Aug 2, 4:30 am, Andrea Gavana <andrea.gav...@gmail.com> wrote:> > >>> Hi,
> > >>> 2009/8/2 evstevemd:
> > >>>> Hi wxPythoners
> > >>>> I have delayed any learning process on Python 3 due to few modules.
> > >>>> One of critical modules for me is the wxPython. Is Robin and the team
> > >>>> planning to release any? I currently stick to my old best friend,
> > >>>> Python 2.5.4
> > >>> This subject comes out quite often in the mailing list. I don't think
> > >>> Robin has done major works on wxPython in the direction of supporting
> > >>> Python 3, and preliminary support *might* be available towards
> > >>> wxPython 3.0 (as far as I remember, please someone correct me if I am
> > >>> saying stupid things).
> > >>> As far as I am concerned, I have run a hacked version of the
> > >>> slooooooooow 2to3.py script in Python 2.6 on the wxPython library: it
> > >>> came up with approximately 1560 "inconsistencies" which will need to
> > >>> be corrected to support Python 3 (if anyone is interested in the 2to3
> > >>> results please let me know). Not to mention, obviously, that possibly
> > >>> some major work may be done on the SWIG interfaces (although I am not
> > >>> sure) and backward compatibility with Python 2.X (which is still the
> > >>> version used by the vast majority of programmers) will be problematic.
> > >>> Other than that, none of the major libraries that I know of have been
> > >>> ported to Python 3.
> > >>> Andrea.
> > >> The only major library I can think of off the top of my head that has
> > >> support for 2.x and 3.x is PyWin32. I don't know how Mark H. et al do
> > >> it, but they did.> > >> It looks like Django is working on 3.0 support, but they say it will
> > >> take 1-2 years to complete the transition. TurboGears can't do
> > >> anything until it gets upstream support.> > >> - Mike
2009/8/4 Mike Driscoll:
Wow, pyqt support 3 too? Really hope wxPython can catch it up
quickly....Well, the people behind pyqt sell commercial versions and support. So
in a way, they are paid to keep pyqt up to date, whereas the people
behind wxPython are not. They do all their programming on a volunteer
basis.
In addition to that, I can't see a particular reason to hurry to
support Python 3. It's a lot of work for little or no gain at all. I
would very much prefer if Robin (and Kevin and others) developers
focus on the new wxWidgets features (fixing bugs, wrapping more
methods and so on), leaving Python 3 close to the end of the shopping
list.
Other than that, my personal experience is that pyqt is in a light
year below wxPython.
Andrea.
"Imagination Is The Only Weapon In The War Against Reality."
http://xoomer.alice.it/infinity77/
···
On Aug 4, 3:12 pm, coffeeGT <pytho...@gmail.com> wrote:
Andrea Gavana wrote:
In addition to that, I can't see a particular reason to hurry to
support Python 3. It's a lot of work for little or no gain at all. I
would very much prefer if Robin (and Kevin and others) developers
focus on the new wxWidgets features (fixing bugs, wrapping more
methods and so on), leaving Python 3 close to the end of the shopping
list.
Strongly agreed. At the moment, there seems to be minimal gain from switching over to Py3, like losing some old classes/modules that weren't used and some deprecation. At the moment, Py3 is also around 10% slower than 2.5.4 - of course, this will change over the years, but to me it seems there's very little to gain