Considerations about Community PyCharm

Comparing this project and the minimal project we created in the previous chapter, FirstProject, we can see that no boilerplate code is generated in a Pure Python project. Since users of the Community edition of PyCharm only have the option to create Pure Python projects, they will have to start from scratch while working on a Django project. However, as Django developers know, a small set of simple Django commands can also achieve the same result and generate the appropriate boilerplate code and structure of the directory tree for us.

So, in the end, the Professional edition of PyCharm might allow you to skip a particular set of steps in the process of setting up a specific Python project, but these steps can also be accomplished easily and independently of PyCharm. However, this is not to say that it is better to forgo PyCharm altogether if you are using its Community edition. On the contrary, we have seen various forms of customization and flexibility that both editions of PyCharm offer, specifically when it comes to organizing our workspace, in this chapter. We will see a similar trend in future chapters as well.

On another note, if you are using the Professional edition, aside from a Django project, you can choose to create other types of Python project, as we have seen from the options in the preceding screenshot (for example, Google App Engine, Angular, or even React applications). We will go into more detail regarding two types of Python project—Django projects and Scientific projects—later on in this book, but feel free to explore other project types that you are interested in.