Dec 24, 2012 at 8:46 AM
Edited Dec 24, 2012 at 9:01 AM
|
Hi,
First let me say I love PTVS, great work!
After a use of couple of days, I would like to ask and suggest some features their lackness disturbs the overall experience:
1. As I mentioned in previous post, error marking, the same error marking as in C# if possible, I find the .Net error reporting just great.
2. Allow assessment of code expressions in one click (Like in matlab) for example if I stopped in a break point, and want to evaluate the next code line, instead of copy pasting it to the IDW, I would just press F-something to send it to the IDW.
I find this feature in matlab to be a real time saver. Currently you can send it interactive (Ctrl+E), which will
evaluate the expression in python, but that is worthless since it doesn’t know the local
variables. Instead it should be "send to IDW".
3. When I enter an expression in IDW, it is evaluated, no problem. But when I want to change an already entered expression in the middle of it, I can’t just press enter and evaluate it, since the enter starts a new line. I have to press "Home"
to get to the end of the expression, and only then press enter. I find it annoying since 99% of the time I want to evaluate the modified expression and not start a new line.
4. Allow code changes while debugging, like in .Net. I usually run in debug mode on my code, find an error, fix it and want to keep going without having to restart the run. I think this should be a must for a non-compiled language, isn’t it so?
5. cant get the ipython interperter to replace the standard one... ?
Thanks again for that great work. I really wish you would fix and improve those suggestions, which would make the coding experience phenomenal!
|
|
Coordinator
Dec 24, 2012 at 9:25 PM
|
Thanks for the feedback and suggestions.
We're already working on #1 and I've created an issue for #2 (http://pytools.codeplex.com/workitem/951). For #3, you can press Ctrl+Enter anywhere in the line and it will evaluate it. And we're
already discussing #5 on another thread.
#4 is something we'd love to be able to do, but unfortunately it is impossible at this point. Because we don't "own" Python, we can't simply change it to allow Edit and Continue (both .NET and C++ have special compiler support to enable this) and
even if we did manage to get changes made to CPython, it wouldn't be available until version 3.4 (which is coming in 2014). Without changing how the interpreter works there is no way to get proper support, and even though it is possible to get partial
support, we don't think it is reliable or useful enough to spend the time on at the expense of other features.
Glad you're enjoying PTVS!
|
|
|
|
Thanks for the quick answers! Im really looking forward for the #2, and about #3 dont you think it should be the other way around? enter evaluates, Ctrl+enter new line?
I appreciate the supportg you are giving here, makes me real confident about choosing PTVS. keep on the great work!
|
|
|
|
+1 on #3. This annoyed me for a long time. I think "enter to evaluate" is the majority default for REPL environments. At least providing a config option for this would be great.
Thanks!
|
|
Coordinator
Dec 25, 2012 at 8:20 PM
|
You may be right, though I've certainly seen both approaches used in various places. An option sounds like the way to go here.
|
|