Re:Python past, present, and future with Guido van Rossum [a...
by crdoconnor on Thursday February 23, 2017 @10:07AM
(#13714408)
>Pycharm tries really hard to paper over the lack of static typing in Python.
It does and IMO this is the wrong approach. I usually fire off a test and use that the push the code to the line I'm interested in, at which point I fire up IPython.embed().
That gives you perfect code completion, instant variable inspection (including instant docstring and code lookup) and the ability to execute and inspect on the fly.
You can then fairly easily copy and paste the lines you want back to the text editor.
IMO that's a step ahead of just having autocomplete in an IDE.
Re:Python past, present, and future with Guido van Rossum [a...
by vosper on Thursday February 23, 2017 @04:48PM
(#13718136)
That sounds interesting, do you have any details (blog post, tutorial) on exactly how to do that?
Re:Python past, present, and future with Guido van Rossum [a...
by mixmastamyk on Thursday February 23, 2017 @11:57AM
(#13715415)
Typing is now available in recent versions of the language.
I love Pycharm, and I think people who go without IDE support are masochists (I did it for a few years with Python, and I'm not going back) but it's not like the kind of tooling support you get from a proper statically typed language, where the IDE can do so much to help you.
And I say this as someone who's been full time in Python for years. It's a fun language to write, with a wonderful ecosystem, but it's not good enough when your codebase gets big or you need to do major refactoring.