1
Vote

Missing print statements

description

First of all, great Job, Python Tools makes it overall a beauty to code in VS and it is great I don't have to switch to another tool.
But there are a few little things I feel missing and would be brilliant, if they could be added.
First of all, you should be able to ctrl+click on a (self-defined) function and it should jump to that, even in another file if that is easily possible.

And another issue I have noticed a few times. When I have really short testing codes with prints and I run the program, then it opens the command line for a second, shows the print statements and closes it, before I can read anything. And in VS studio in the "show output from: Debug" modules it often doesn't show the prints. That is actually my only real complaint. I think one of two things should happen: Either, the obvious one, VS should constantly and reliably show all print statements in the Output dialog, or there should be an option, that the cmd console stays open after the program finished executing.

Oh, and the last thing, I think I should mention, I think the Intellisens could use some improvement as well.

Anyway, thanks for that plugin and keep up the good work! Cheers

comments

Zooba wrote Jan 28 at 3:38 PM

I think we can satisfy all of your requests:

The Productivity Power Tools extension provides Ctrl+Click support (among other helpful features), which works fine with PTVS.

We have three options that may help you with the second request. Under Tools->Options->Python Tools->Advanced you will want to ensure that "Wait for input when program exits abnormally", "Wait for input when program exits normally" and "Tee program output to Debug Output window" are selected.

Selecting "...exits normally" (which is unchecked by default) will keep the console window open. "Tee program output..." should already be selected, so if your script is not showing all its prints then there's probably a bug. Are you able to share the script that causes it so we can figure out why?

I'm currently working on making some significant changes to IntelliSense that should improve it a lot for our next release. Could you be more specific about what it's currently getting wrong or how you would like it to be improved?

Thanks for the kind words.

Rosswold wrote Jan 31 at 1:51 PM

Thanks for pointing out that plugin for me, it does pretty much what I was asking for.

Also thank for pointing out nr2, tough I do think there is an error on your site (or maybe it has somehing to do with VS). Basically it is not like it never prints the print statements, sometimes I start the exact same code and it does show the prints and a few min later it does not.
Even now, I have just been testing
print("hello")
(using python 3.3)
and just been pressing the Start button in VS 10 times or so (as in, pressing button, waiting until cmd pops up and disappears, and then pressing it again) and there it "just" shows the print output maybe 9 times.

And about the IntelliSense, I have to be honest, I haven't given it any conscious thought yet, but I have seen two other issues, which seem to make sense:
Autocompletion does not work for modules specified in PYTHONPATH
enable C++ like intellisense (type any part, not just 1st letters)

And one last thing, I quite like, is how the "new" eclipse 4.x tries to guess what method or variable you want to use and then puts them on top (afaik, is uses more than just information on how often you have used a certain function before). But that point is really the least important point on the wishlist.

If I can think of anything more I'll let you know.
Cheers