PyCharm - tips, tricks and plugins

Introduction

I have been using Vim for a long time, but recently I have started using PyCharm too. This tool has many proper features and plugins. I will show you some of them. You will find here many gifs instead of text. In this way, you can easily see how it works, how it looks, etc.

Plugins


 .ignore
This plugin was written by my friend. Here is more info about it. It will generate new ignore files for you.



BashSupport
Supports syntax highlighting, rename refactoring, documentation lookup, inspections, quickfixes, etc.


Dash
A smart and simple plugin that provides keyboard shortcut access for Dash.


KeyPromoter
Shows you how easy you can make the same action using only a keyboard.


Lua
Support for LUA.


Markdown
Support for markdown.


YAML/Ansible support
I don't want to write again "Support for YAML/Ansible".

Tips & Tricks


You do not know what to do? Do not be scared! Just use TODO.


You have access to Terminal and Python Console in an easy way. Of course, you can decide which shell do you want to use.



Version Control. Let's say you want to see what someone has changed in this file from commit A to commit B. You just see a history of git.


And now, you want to see all commits of a particular user.


You have reached a very odd file. You want to see who has made this, when and why.


You have a better idea to name a variable, so you want to change this quickly.


If you create a docstring PyCharm will fill the docstring with parameters.


Let's say that you have changed some lines of code, and you forgot what was there before. Consequently, you want to see these changes and restore to the former state if there was a mistake.


Your project is large and you do not want to remember where lives every piece of code. Too much waste of time. Hence, you want to find these objects very quickly. You can locate them by class name, file name, symbol name, etc.


You have the class A. Other classes inherit from the class A. In class A, you have a particular method, and you want to see how this method is implemented in other classes.


That's enough for me. I am not going to convince someone to use PyCharm; I just wanted show some features that I like very much in this editor. It is the best alternative for Vim (for me of course).
Location: Wrocław, Polska

Comments

Post a Comment

Popular posts from this blog

GitLab - extends keyword

Image
In the previous post I had written about the include keyword. Now, let's dive in the extends  keyword. What can you do with this? Here is the definition from GitLab documentation: extends defines entry names that a job that uses extends inherits from. It’s an alternative to using YAML anchors and is a little more flexible and readable. So, when is it useful? It is useful when you want to be DRY and keep your setup cleanly. Let's assume that you want to build a docker image and give developers possibility to deploy the image on dev , staging and prod environments. We are going to do that without the extends keyword, and after that we will think how we can do it better. Example without the extends  keyword: As you can see, there is a lot of code which repeats itself: stage, image, when  and script . We can remove a lot of code! So, let's do that. We are going to create a hidden job .deploy  (you will not see this job in a pipeline) and the rest of the jobs will in
Read more

GitLab - trigger keyword

Image
 We are going to talk about the trigger keyword today. With this feature you can define a downstream pipeline trigger. So, you can trigger a pipeline in any project (you must have access to this project of course). There are two types of downstream pipelines: multi-project pipelines child pipelines  Let's omit child pipelines and have a look at multi-project pipelines. It is very easy to use. You just need to provide a path to the project and that's it. Remember that you only can trigger a pipeline, not a job ! You can also provide more information like environment variables. As always, I am going to provide some examples, so you will understand it better. The first example: you want to trigger a pipeline in another project after the deployment of your service/s. How to do that? Here we want to trigger this pipeline (project my/run-tests ). Let's say that we want to run some tests after each deployment: We need to add the job which will trigger this pipeline in my/run-
Read more

Managing Secrets in GitLab / Git

Image
Let's say that you have to log in via ssh into an instance, and you work with GitLab, so you want to keep the private key in GitLab somewhere. Is it secure? Let's see! Custom environment variables You can use custom environment variables. Here you can read more about them (Developers cannot change them, only Maintainers and Owners can). There are two types of variables: Variable (the runner creates an environment variable that uses the key for the name and the value for the value) File (the runner creates an environment variable that uses the key for the name. For the value, the runner writes the variable value to a temporary file and uses this path) It seems that we can use File type for our purpose. We can set up it via API or UI . So, let's do that! Go to project's Settings > CI/CD . There will be Variables section (btw, you can specify variables also per group and even for all projects (in admin panel)). Click Add Variable button and add a variable: Key:
Read more