Write Clean, Professional, Maintainable, Quality Code in Python
51–56 of 56 posts
Re: Write Clean, Professional, Maintainable, Quality Code in Python
#52Maybe it gets better with practice, so I'll keep trying a bit more, but currently, count me as unimpressed:
1 - About code inspection. Well, I fully understand that inspecting Python code is hard, and any tool will have either false positives, or false negatives. But PyCharm gets false positives to the extreme, it complains about not resolving Python standard functions (like open), and it can't find some libraries at my virtualenv. It's so full of false positives that I'm not sure I'll be able to keep reading them - I normaly can't stand code with warnings, but in PyCharm there is no other way.
2 - About formating. It fully enforces PEP8, the most completely enforcement I've seen on any tool (no I didn't try the emacs el for that). That's a good thing if there is an option to turn it off, what I don't know, because I didn't search for it yet.
3 - About refactoring. No, PyCharm, I don't want Django to change because I changed a function name in my code. Maybe there is a way to tell it not to touch some dirs, but the default settings makes PyCharm much less reliable and slower than grepping the old name and replacing it by hand. I'll try to find such setting when I get out of work today, but it's making the case of PyCharm being easier to setup way less appealing.
Re: Write Clean, Professional, Maintainable, Quality Code in Python
#53My concern about PyCharm is that it's becoming the Microsoft Office of IDEs. I feel like there's more and more bullet points per release that are more marketing-oriented than widely useful. While my needs remain simple. Maybe everyone needs only 2% of the feature set, and a different 2%, but we all have to pay for the bloat anyway. I keep repeating a cycle where I try an IDE because it sounds interesting, but a few w…
If your text editor works better than PyCharm, then by all means use that instead. However, the article is actually trying to make some point about what an IDE can do that text editors can't so perhaps you'd want to respond to that? > Maybe everyone needs only 2% of the feature set, and a different 2%, but we all have to pay for the bloat anyway. This is not a useful mental model for thinking about software. First, b…
Jetbrains' products are not immune from bloat.
Re: Write Clean, Professional, Maintainable, Quality Code in Python
#54My concern about PyCharm is that it's becoming the Microsoft Office of IDEs. I feel like there's more and more bullet points per release that are more marketing-oriented than widely useful. While my needs remain simple. Maybe everyone needs only 2% of the feature set, and a different 2%, but we all have to pay for the bloat anyway. I keep repeating a cycle where I try an IDE because it sounds interesting, but a few w…
If your text editor works better than PyCharm, then by all means use that instead. However, the article is actually trying to make some point about what an IDE can do that text editors can't so perhaps you'd want to respond to that? > Maybe everyone needs only 2% of the feature set, and a different 2%, but we all have to pay for the bloat anyway. This is not a useful mental model for thinking about software. First, b…
So an IDE, also, can get into that state. Which is maybe why I can never find an IDE I like to use. I could only see calling PyCharm "sleek" if that was in comparison to something like Eclipse. It's a better choice than that, but still not the experience that it could be, or that I'm looking for.
Re: Write Clean, Professional, Maintainable, Quality Code in Python
#55Earlier quoted context omitted.
Nor will python. Python is dynamically typed. It may not be impossible to write big functioning python apps, but it's damn hard. And specifically, it's a lot harder than doing it in java or C++. I've seen C++ codebases that exceed 8 million lines of code and held together (not without friction, that I guarantee). I've seen java codebases with about half that that held together a lot better than the C++ ones. Even acc…
I have personally worked on a 7 man team on a 2.5m LOC codebase in Python (Python 2.4, to be precise). It wasn't public, though. Working on the code base with dynamic typing wasn't _that_ hard. Certainly not as hard as people make it out to be.
Re: Write Clean, Professional, Maintainable, Quality Code in Python
#56If this advertisement convinced you to try a Python IDE, consider giving PyDev/LiClipse a try. It's free and open.