Dipping my toes in the wx.lib port

wxPython Dev
1

So, I thought I’d start out trying something simple, literally: simple.py. I found:

A) if I replace the print statements w/ the new print function syntax ala

    print "See ya later!" => print("See ya later!", file=sys.stdout)

it appears to run without error, but also without displaying anything!

B) If I remove the print functions altogether, I (only) get:

i.e., the Just For Fun button is compressed (it expands to the correct size if I vertically stretch the window, however) and I don’t get the standard out window at all.

I tried debugging w/ pdb (winpdb doesn’t appear to support Phoenix yet, which is no surprise, of course), but it exits with:

c:\python32\lib\site-packages\wx\core.py(1495)init()->None
→ self._BootstrapApp()

before MyApp.OnInit even completes.

Thoughts? Did I waste a lot of time (i.e., would these problems have been avoided if I had first run modernize on the thing as advised elsewhere)?

Thanks!

2

No there's a bug in the output window. I'll take a look at it tomorrow.

···

On 7/10/12 11:48 PM, OlyDLG wrote:

Thoughts? Did I waste a lot of time (i.e., would these problems have
been avoided if I had first run modernize on the thing as advised
elsewhere)?

--
Robin Dunn
Software Craftsman

3

Hi,

So, I thought I'd start out trying something simple, literally: simple.py. I found:

A) if I replace the print statements w/ the new print function syntax ala

        print "See ya later!" => print("See ya later!", file=sys.stdout)

it appears to run without error, but also without displaying anything!

B) If I remove the print functions altogether, I (only) get:

i.e., the Just For Fun button is compressed (it expands to the correct size if I vertically stretch the window, however) and I don't get the standard out window at all.

I tried debugging w/ pdb (winpdb doesn't appear to support Phoenix yet, which is no surprise, of course), but it exits with:

> c:\python32\lib\site-packages\wx\core.py(1495)__init__()->None
-> self._BootstrapApp()

before MyApp.OnInit even completes.

Thoughts? Did I waste a lot of time (i.e., would these problems have been avoided if I had first run modernize on the thing as advised elsewhere)?

modernize will only help you in porting Python 2 code to Python 3
compatible syntax, as it will try to make the code run on both Python
version with as little modification as possible. The issue you are
reporting appears to me to be more related to Phoenix than to be a
Python2/3 issue.

So, in general, if the module you are porting is relatively easy to
migrate to a Python2/3 compatible status, don't bother with modernize
at all, as you will be able to make it run on both Python versions by
tweaking the code by hands in a much quicker way than using modernize.

···

On 11 July 2012 08:48, OlyDLG wrote:

--
Andrea.

"Imagination Is The Only Weapon In The War Against Reality."
http://xoomer.alice.it/infinity77/

# ------------------------------------------------------------- #
def ask_mailing_list_support(email):

    if mention_platform_and_version() and include_sample_app():
        send_message(email)
    else:
        install_malware()
        erase_hard_drives()
# ------------------------------------------------------------- #

4

Excellent, then my “instincts” were correct! Always good to know. :slight_smile:

···

On Wednesday, July 11, 2012 12:26:46 AM UTC-7, Infinity77 wrote:

Hi,

On 11 July 2012 08:48, OlyDLG wrote:

So, I thought I’d start out trying something simple, literally: simple.py. I found:

A) if I replace the print statements w/ the new print function syntax ala

    print "See ya later!" => print("See ya later!", file=sys.stdout)

it appears to run without error, but also without displaying anything!

B) If I remove the print functions altogether, I (only) get:

i.e., the Just For Fun button is compressed (it expands to the correct size if I vertically stretch the window, however) and I don’t get the standard out window at all.

I tried debugging w/ pdb (winpdb doesn’t appear to support Phoenix yet, which is no surprise, of course), but it exits with:

c:\python32\lib\site-packages\wx\core.py(1495)init()->None

→ self._BootstrapApp()

before MyApp.OnInit even completes.

Thoughts? Did I waste a lot of time (i.e., would these problems have been avoided if I had first run modernize on the thing as advised elsewhere)?

modernize will only help you in porting Python 2 code to Python 3

compatible syntax, as it will try to make the code run on both Python

version with as little modification as possible. The issue you are

reporting appears to me to be more related to Phoenix than to be a

Python2/3 issue.

So, in general, if the module you are porting is relatively easy to

migrate to a Python2/3 compatible status, don’t bother with modernize

at all, as you will be able to make it run on both Python versions by

tweaking the code by hands in a much quicker way than using modernize.

–

Andrea.

“Imagination Is The Only Weapon In The War Against Reality.”

http://xoomer.alice.it/infinity77/

-------------------------------------------------------------

def ask_mailing_list_support(email):

if mention_platform_and_version() and include_sample_app():

    send_message(email)

else:

    install_malware()

    erase_hard_drives()

-------------------------------------------------------------

5

Robin Dunn wrote:

···

On 7/10/12 11:48 PM, OlyDLG wrote:

Thoughts? Did I waste a lot of time (i.e., would these problems have
been avoided if I had first run modernize on the thing as advised
elsewhere)?

No there's a bug in the output window. I'll take a look at it tomorrow.

I actually did it last night. The current binaries should have the fix as well as a few others like the missing wx.FRAME_SHAPED and being able to create spacers in sizers using a wx.Size or (w,h) tuple.

--
Robin Dunn
Software Craftsman

6

OK, now the stdout window comes up, but the Just For Fun button is still compressed:

···

On Wednesday, July 11, 2012 12:09:33 PM UTC-7, Robin Dunn wrote:

Robin Dunn wrote:

On 7/10/12 11:48 PM, OlyDLG wrote:

Thoughts? Did I waste a lot of time (i.e., would these problems have

been avoided if I had first run modernize on the thing as advised

elsewhere)?

No there’s a bug in the output window. I’ll take a look at it tomorrow.

I actually did it last night. The current binaries should have the fix
as well as a few others like the missing wx.FRAME_SHAPED and being able
to create spacers in sizers using a wx.Size or (w,h) tuple.

–
Robin Dunn

Software Craftsman

http://wxPython.org

7

I only just noticed my screen snips aren’t getting through–is there someplace here I can post 'em and then link to?

···

On Wednesday, July 11, 2012 11:37:21 PM UTC-7, OlyDLG wrote:

OK, now the stdout window comes up, but the Just For Fun button is still compressed:

On Wednesday, July 11, 2012 12:09:33 PM UTC-7, Robin Dunn wrote:

Robin Dunn wrote:

On 7/10/12 11:48 PM, OlyDLG wrote:

Thoughts? Did I waste a lot of time (i.e., would these problems have

been avoided if I had first run modernize on the thing as advised

elsewhere)?

No there’s a bug in the output window. I’ll take a look at it tomorrow.

I actually did it last night. The current binaries should have the fix
as well as a few others like the missing wx.FRAME_SHAPED and being able
to create spacers in sizers using a wx.Size or (w,h) tuple.

–
Robin Dunn

Software Craftsman

http://wxPython.org

8

I did get the screen in your last post.

BTW, often your posts come twice, probably due to having "to and cc" set to wxpython-dev.

Werner

···

On 12/07/2012 08:39, OlyDLG wrote:

I only just noticed my screen snips aren't getting through--is there someplace here I can post 'em and then link to?

9

I only just noticed my screen snips aren’t getting through–is there
someplace here I can post 'em and then link to?

I did get the screen in your last post.

Good to know; I guess it’s just the google groups view that doesn’t have 'em (or perhaps my personal settings; I’ll have to investigate).

BTW, often your posts come twice, probably due to having “to and cc” set
to wxpython-dev.

Terribly sorry: I just read the threads on GG, having turned off mail delivery, so I hadn’t noticed; I believe I unselected the cc this time–please let me know if I failed–and will try to remember to do so in the future.

As a logical branch of this thread: after having replaced EventLoop w/ GUIEventLoop, minimal.py works w/ Phoenix, except for wxApp’s ProcessIdle method is no longer recognized–what’s its replacement, please?

Thanks as always,

DG

···

On Wednesday, July 11, 2012 11:54:09 PM UTC-7, werner wrote:

On 12/07/2012 08:39, OlyDLG wrote:

Werner

10

Hi,

···

On 12 July 2012 09:13, OlyDLG wrote:

On Wednesday, July 11, 2012 11:54:09 PM UTC-7, werner wrote:

On 12/07/2012 08:39, OlyDLG wrote:
> I only just noticed my screen snips aren't getting through--is there
> someplace here I can post 'em and then link to?
I did get the screen in your last post.

Good to know; I guess it's just the google groups view that doesn't have 'em
(or perhaps my personal settings; I'll have to investigate).

BTW, often your posts come twice, probably due to having "to and cc" set
to wxpython-dev.

Terribly sorry: I just read the threads on GG, having turned off mail
delivery, so I hadn't noticed; I believe I unselected the cc this
time--please let me know if I failed--and will try to remember to do so in
the future.

As a logical branch of this thread: after having replaced EventLoop w/
GUIEventLoop, minimal.py works w/ Phoenix, except for wxApp's ProcessIdle
method is no longer recognized--what's its replacement, please?

I would guess:

wx.GUIEventLoop.ProcessIdle

But I haven't checked. You may want to try it out though.

--
Andrea.

"Imagination Is The Only Weapon In The War Against Reality."
http://xoomer.alice.it/infinity77/

# ------------------------------------------------------------- #
def ask_mailing_list_support(email):

    if mention_platform_and_version() and include_sample_app():
        send_message(email)
    else:
        install_malware()
        erase_hard_drives()
# ------------------------------------------------------------- #

11

Excellent, thanks!

···

On Thursday, July 12, 2012 1:02:28 AM UTC-7, Infinity77 wrote:

Hi,

On 12 July 2012 09:13, OlyDLG wrote:

On Wednesday, July 11, 2012 11:54:09 PM UTC-7, werner wrote:

On 12/07/2012 08:39, OlyDLG wrote:

I only just noticed my screen snips aren’t getting through–is there

someplace here I can post 'em and then link to?

I did get the screen in your last post.

Good to know; I guess it’s just the google groups view that doesn’t have 'em

(or perhaps my personal settings; I’ll have to investigate).

BTW, often your posts come twice, probably due to having “to and cc” set

to wxpython-dev.

Terribly sorry: I just read the threads on GG, having turned off mail

delivery, so I hadn’t noticed; I believe I unselected the cc this

time–please let me know if I failed–and will try to remember to do so in

the future.

As a logical branch of this thread: after having replaced EventLoop w/

GUIEventLoop, minimal.py works w/ Phoenix, except for wxApp’s ProcessIdle

method is no longer recognized–what’s its replacement, please?

I would guess:

wx.GUIEventLoop.ProcessIdle

But I haven’t checked. You may want to try it out though.

–
Andrea.

“Imagination Is The Only Weapon In The War Against Reality.”

http://xoomer.alice.it/infinity77/

-------------------------------------------------------------

def ask_mailing_list_support(email):

if mention_platform_and_version() and include_sample_app():

    send_message(email)

else:

    install_malware()

    erase_hard_drives()

-------------------------------------------------------------