Below you will find pages that utilize the taxonomy term “Pycharm”
Programs used for Programming in 2023
I didn’t really use any new programs this year. I just continued expanding on programs I’ve used in the past.
Python
For Python I continued to mostly use Pycharm. I’ve spoken about it for the past few years, but JetBrains continues to add features that make it easier to work with Python. For example, this year they added a model explorer to have better visibility into your models in Django. They also make running development servers for Django, Flask, and FastAPI a breeze. (Including restarting the server after every save).
Software I used for Programming in 2022
Python
This year I really worked a lot on Python web technologies so I came to appreciate all the work that the JetBrains team does to make all the little things (like running Django test server commands) incredibly easy. I essentially did all my Python development in Pycharm. I’ve had access to the paid JetBrains suite because of the work I’ve done for my open source project: Extra Life Donation Tracker. Since development has slowed a bit on there, I may not be able to renew the subscription. If that’s the case, there’s a big chance that I’ll start saving up some money for a Pycharm Professional license. The only real exception to using Pycharm for programming was when I was editing code on a server. There I would use vim or nvim (more on that later).
Software I used for Programming in 2021
Overall, there was a continuation of trends from last year with just a few changes.
Python
Pycharm
PyCharm has continued to be my IDE of choice for Python programming. The devs haven’t been resting on their laurels, either. Recently they added some extra features to support FastAPI. And they also added some features that I don’t 100% understand that make it easier to test against fake HTTP endpoints. It’s really awesome and definitely worth the price if you program primarily in Python. As I predicted last year, its git features ended up making GitQlient and Git Kraken (on Linux) more or less obsolete for me.
PyCharm 1 week Update
I’ve been using PyCharm for about a week now across a couple projects. I’d like to note a few things I’m really enjoying:
- PyCharm is aware of your venv config and you can use it to pip install new packages. Ok, so pip is easy to use for installing. But it also provides a quick at-a-glance view of the packages you’ve installed and their versions - and I find it easier to view than a pip freeze.
- I know KDevelop has this for C++, but it doesn’t really have the same support for Python - being able to run my Python files from within PyCharm as well as being able to run the debugger from within PyCharm is like how new cars unlock for you when you get close. It’s not necessary. It’s not even that huge of an improvement. But it’s a quality of life thing that you miss when it’s not there.
- PyCharm is very smart about git. With KDevelop, I could add files withink the GUI (which is nice for making sure the project is aware of the file and provides a quick visual cue). But then I had to remember to git add it (either in the GUI or on the commandline). With PyCharm, every time I add a file through the GUI, it asks me if I want to add it to version control.
PyCharm asking if I want to add the new file to source control
Hey, Pycharm, hey.
Back in September I wrote about moving to KDevelop for my larger Python projects and also staying with Kate for my smaller projects. I’ve REALLY been enjoying all the features as I work on more and more complex packages involving lots of files. But for a few episodes of Python Bytes now (and/or maybe Talk Python to Me - they share a host) they’ve been talking about how awesome it is to use an IDE that has a Python debugger built in. It may be that KDevelop has that ability (I’m pretty sure it does for C++), but I’m not sure. I am nearly certain that Pycharm does have a debugger built-in. A while ago I’d set up the Pycharm COPR repo on my laptop. I tried playing with it a little at the time, but I was coding on a very small project without a venv, so things didn’t work out well. (Pycharm is pretty opinionated about the way a Python project should work)