Where in a virtualenv does the custom code go?

Viewed 49673

What sort of directory structure should one follow when using virtualenv? For instance, if I were building a WSGI application and created a virtualenv called foobar I would start with a directory structure like:

/foobar
  /bin
    {activate, activate.py, easy_install, python}
  /include
    {python2.6/...}
  /lib
    {python2.6/...}

Once this environment is created, where would one place their own:

  • python files?
  • static files (images/etc)?
  • "custom" packages, such as those available online but not found in the cheese-shop?

in relation to the virtualenv directories?

(Assume I already know where the virtualenv directories themselves should go.)

5 Answers

I have asked this question myself and then I found a very helpful video on YouTube that clearly explains how to set up a venv environment and the reason not to add your working files inside the venv directory.

Here is the video link:

https://www.youtube.com/watch?v=APOPm01BVrk&t=18s
Related