G'day,
I'm knocking up a Q&D program that needs a basic GUI, I have used wxPython in past (~3 years ago) and am pretty rusty, accordingly ...
I would like my program to be both 2.x and 3.x compatible (hey, I can () my prints ....). Not doing anything terribly fancy, I need a scrolling text window that I can cut & paste out of and update in close to real time and a couple of buttons, it'll run on Windows (7, 8 and 10), in a mix of 32 & 64 bit versions, and *maybe* on Linux (unsure of what versions ...).
With Phoenix, and wxPython 3.x, is this possible? Trivially easy or am I going to shoot myself in the foot bigtime by even trying?
I see that the phoenix builds are reasonably active (from wxpython.org/Phoenix/snapshot-builds), what build would you guys recommend?
Thank you,
Carl
Hello Werner,
Hi Carl,
.
I see that the phoenix builds are reasonably active (from
wxpython.org/Phoenix/snapshot-builds), what build would you guys
recommend?
For Py2 and Py3 you would have to use Phoenix, just install the latest
snapshot.
How to install wxPython - wxPyWiki
This implies that a program written that runs in both python 2 and 3, will work with wxPython Phoenix, and will make my toy future-resistant. Am I understanding correctly?
Thank you,
Carl
···
On 3/08/2015 7:21 PM, Werner wrote:
Werner
Hi Carl,
...
For Py2 and Py3 you would have to use Phoenix, just install the latest
snapshot.
How to install wxPython - wxPyWiki
This implies that a program written that runs in both python 2 and 3, will work with wxPython Phoenix, and will make my toy future-resistant. Am I understanding correctly?
Yes, you do. I converted my shareware to Phoenix, as I also want it to run against wxPython classic I have about 50 places where I do "if 'phoenix' in wx.PlatformInfo:" in an application with about 300 classes.
Werner
···
On 8/3/2015 13:28, Carl Brewer wrote:
This implies that a program written that runs in both python 2 and 3, will
work with wxPython Phoenix, and will make my toy future-resistant. Am I
understanding correctly?
Yes, you do. I converted my shareware to Phoenix, as I also want it to
run against wxPython classic I have about 50 places where I do "if
'phoenix' in wx.PlatformInfo:" in an application with about 300 classes.
and if Phoenix works for you, then you can do py2+py3 but only Phoenix, and
you should be able to not special case anything, once you do the 2-3
__future__ imports.
-CHB
···
Werner
--
You received this message because you are subscribed to the Google Groups
"wxPython-users" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to wxpython-users+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
--
Christopher Barker, Ph.D.
Oceanographer
Emergency Response Division
NOAA/NOS/OR&R (206) 526-6959 voice
7600 Sand Point Way NE (206) 526-6329 fax
Seattle, WA 98115 (206) 526-6317 main reception
Chris.Barker@noaa.gov
Sounds good to me! Is there a guide to how to use __future__ imports somewhere handy?
Thanks again!
Carl
···
On 4/08/2015 2:51 AM, Chris Barker wrote:
This implies that a program written that runs in both python 2
and 3, will work with wxPython Phoenix, and will make my toy
future-resistant. Am I understanding correctly?
Yes, you do. I converted my shareware to Phoenix, as I also want it
to run against wxPython classic I have about 50 places where I do
"if 'phoenix' in wx.PlatformInfo:" in an application with about 300
classes.
and if Phoenix works for you, then you can do py2+py3 but only Phoenix,
and you should be able to not special case anything, once you do the 2-3
__future__ imports.
This implies that a program written that runs in both python 2
and 3, will work with wxPython Phoenix, and will make my toy
future-resistant. Am I understanding correctly?
Yes, you do. I converted my shareware to Phoenix, as I also want it
to run against wxPython classic I have about 50 places where I do
"if 'phoenix' in wx.PlatformInfo:" in an application with about 300
classes.
and if Phoenix works for you, then you can do py2+py3 but only Phoenix,
and you should be able to not special case anything, once you do the 2-3
__future__ imports.
Sounds good to me! Is there a guide to how to use __future__ imports
somewhere handy?
If I'd googled before posting ...
Imports — Python-Future documentation
···
On 4/08/2015 10:52 AM, Carl Brewer wrote:
On 4/08/2015 2:51 AM, Chris Barker wrote:
Thanks again!
Carl