Effective PyCharm Transcripts
Chapter: PyCharm Projects
Lecture: Concept: Mark directory as...
0:00 As our applications get more complicated. It's really important that we were able to point PyCharm in the right direction.
0:07 And one of the main ways that we do that is with the 'Mark directory' as options. We saw that we can say some sections.
0:14 This just happens to be included with the files but we don't want to think of it as part of the code of this project so we can exclude things in the
0:22 web. We might want to carefully control how the static files that are mapped into the web directory. How those are found by PyCharm.
0:35 And if we want to treat a directory as a sub application within our project, we're going to go there and say mark this as a 'Sources root'.
0:44 So all sorts of cool things we can do here to help PyCharm better understand
0:48 a more complicated directory structure rather than just here's a folder with a file or two Now, if we dive into these we have Sources root.
0:58 The official definition is these roots contain the actual source files and resources PyCharm uses
1:04 the source roots as the starting point for resolving imports. We saw that when I said from shared UI import header helper,
1:12 whatever I call it, UI helper. Those who had all squiggles under them because PyCharm knew that that relative directory structure
1:19 didn't make sense until we told it about that. Sources root and then it did. The 'Resource roots' are for things like style sheets and CSS 'Excluded'
1:29 Tell us by term to almost ignore them. Usually it won't go and index them and so on, but you can still go and find them.
1:37 And then the template folder contains things like Jinja templates, Camelia templates, Django templates and so on.
1:44 Those are your rich templates for your Web application.