Plans/timeframe to support Phoenix ("wxPy3K")

31 views
Skip to first unread message

OlyDLG

unread,
Jul 11, 2012, 2:20:18 AM7/11/12
to win...@googlegroups.com
Hi!  List newbie here.

Is there a plan/time-frame for supporting Phoenix

(Kind of a "Catch-22" situation: I'd like to use winpdb in helping to port wx.lib, but when I try to import winpdb itself in Python3, I of course get:

Python 3.2.3 (default, Apr 11 2012, 07:15:24) [MSC v.1500 32 bit (Intel)] on win32
Type "help", "copyright", "credits" or "license" for more information.
>>> import winpdb
wxPython was not found.
wxPython 2.6 or higher is required to run the winpdb GUI.

I have a binary of Phoenix installed in my Python3 site-packages; is there a "naive" way to tell winpdb to try to use Phoenix, and then see where it "breaks" trying to do so?)

Thanks!

OlyDLG

Nir Aides

unread,
Jul 11, 2012, 5:09:11 AM7/11/12
to win...@googlegroups.com
Hi,

No such plans at the moment.

You can still try to debug on that machine using the winpdb command line debugger called rpdb2
or try to debug remotely with the UI client on another machine.

Nir





OlyDLG

--
You received this message because you are subscribed to the Google Groups "Winpdb" group.
To view this discussion on the web visit https://groups.google.com/d/msg/winpdb/-/7X2l20nUBrwJ.
To post to this group, send email to win...@googlegroups.com.
To unsubscribe from this group, send email to winpdb+un...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/winpdb?hl=en.

OlyDLG

unread,
Jul 11, 2012, 12:02:16 PM7/11/12
to win...@googlegroups.com
Thanks for your reply.


On Wednesday, July 11, 2012 2:09:11 AM UTC-7, Nir Aides wrote:
Hi,

No such plans at the moment.

Oh, well...maybe I'll have a go at it...
 
You can still try to debug on that machine using the winpdb command line debugger called rpdb2

Understood, but what does rpdb2 have that makes it easier to use than simply pdb?  (My lack of success w/ pdb--mostly stemming from my dependency on having a GUI when I debug, I suspect--is why I went checking on the status of winpdb, even though I knew it was almost certainly way too early for it to be Phoenix-compatible.)
 
or try to debug remotely with the UI client on another machine.

The implication--that I can use a Python2/wxPython "Classic" app to debug a Python 3 module--sounds promising: where can I read more on how to do that exactly?

Thanks again,

OlyDLG
 

Nir

Reply all
Reply to author
Forward
0 new messages