[wingide-users] Improving Wingware workflow

Christopher Fry cfry1 at MIT.EDU
Sun Oct 14 21:23:53 EDT 2012

Thanks John
I know your hands are somewhat tied with Python's inflexibilites,
so the tools I spoke of are just easier to implement in better langs,
which is part of the reason they're better in the first place.
(Python is better in some ways than those languages, but
not in core lang design issues like this)

After reflecting on my original message, I realized what was
really going on is that I wanted to merge the functionality
of your "debug probe", and your "Python shell".
Although I occassionally want to have a "clean shell",
that is, in practice a very rare need in the IDEs I spoke of
that have just one "shell".

Perhaps the easiest thing you could do in the near term is to
make the "Stack Data" inspector work on data/vars in the Python Shell.
(I've mentioned this before)

In any case, I'd be happy to help you with the details of the design
of such new tools when the time is right for you.

Wingware remains the best Python IDE I've seen. 
Keep up the good work!

From: Wing IDE Support [support at wingware.com]
Sent: Sunday, October 14, 2012 1:08 PM
To: Christopher Fry
Cc: wingide-users at wingware.com; lieber at media.mit.edu
Subject: Re: [wingide-users] Improving Wingware workflow

On 10/12/12 8:01 PM, Christopher Fry wrote:
> What I am proposing is a way to work that was common on the Lisp Machine,

There are a number of good ideas here and we plan to build more support
for interactively changing a program without restarting a process after
Wing 5 is out.  Interestingly, many of the requests for this come from
scientific / numerical programmers who are coming from Matlab and
similar environments for working with data.

My thinking is to add this sort of interactive functionality as an
option; Wing will continue to support the debug-edit-debug process that
many developers are used to.  One thing to keep in mind is that the
Python runtime has limited support for code reloading and that any such
environment will need to work within the context of the CPython vm can do.

Our priority right now is on the port to qt for Wing 5.  I can't give a
timeline for Wing 5 now, but we are working on it.  After that is
released, we'll explore what can be done to improve Wing's interactive
development support.



More information about the wingide-users mailing list