title: Imports within a project from a repo
body: <p>I wondered if there is a smoother way to work with modules pulled from a repo than extending the path with sys.path.extension.</p>
  
  <p>We pull a project and need to save the file structure of it for every day once completed. Besides, I pull the whole project every time I start to work.</p>
  
  <p>The path extensions needed are differently deep and we just use a lot of lines of code to describe locations of modules.</p>
  
  <p>Is there an easier way to do this? Is there a way to generalize this path extensions?</p>
  
  <p>We push and pull the repo quite often and since we are talking about a small collection of scripts we always pull the whole master(project) to work locally. So setting up the project's path extensions once locally to run does not solve the problem of the next day.</p>
  
  <pre class="lang-py prettyprint-override"><code>str_rel_par_folder = os.path.dirname(os.path.dirname(os.path.realpath(__file__)))
  sys.path.extend([os.path.join(str_rel_par_folder, r'some_file')])
  </code></pre>
  
  <p>It would be very nice if someone knows this problem and handles it somehow. Maybe you have some recommendation on how to use Github differently to avoid those kinds of issues.</p>