[wingide-users] IDE Problem
scorpion032 at gmail.com
Tue Mar 17 01:28:50 MDT 2009
The problem is now solved. It was occurring as I had configured wing to use
an external console ipython.
I just removed that and all is fine. Everything else was and has been
Thanks for a timely reply and a good support.
On Mon, Mar 16, 2009 at 9:30 PM, Wingware Support <support at wingware.com>wrote:
> Lakshman Prasad wrote:
>> Try also setting the Python Executable in Project Properties to
>> a specific interpreter and verify whether or not restarting the
>> Python Shell in Wing (from its Options menu) works. It may be
>> that you installed a newer Python that is being found but
>> not supported by your version of Wing. Wing 3.1.7 supports
>> Python 2.0->2.6 but not 3.0.
>> That is not true, as I also have wing 101 also installed and it works
>> perfectly fine. Also I dint install any Python recently at all.
> That's odd. So you are saying that debugging fails w/ the "The debug
> process never connected back" error under Wing Pro and not 101 using
> the same Python version?
> Note that under 101, the gui is a bit different but in both you should
> be able to see what Python version Wing is finding by typing this
> in the Python Shell:
> import sys
> In any case, reinstalling Wing is probably a good idea. If that doesn't
> help, try turning on the Debugger / Advanced / Log File preference and
> sending us the resulting file after attempting to start debug (assuming
> it's non-empty) and _also_ submit a bug report from the Help menu in
> Wing and include the error log from there (that is the IDE-side log,
> and both are needed to see what's going on).
> Stephan Deibel
> Wingware | Python IDE
> Advancing Software Development
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the wingide-users