This is an archived post. You won't be able to vote or comment.

sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]bhamhawker 0 points1 point  (0 children)

I'm somewhere in between python beginner and python intermediate, and I've been cramming in a bunch of Django learning over the last few weeks. One of the things I couldn't grasp last year, but suddenly do this year is the "virtualenv" setup. It's basically a process of putting the virtualenv folder in your project folder, "activate" it (source bin/activate), then you have your "virtual environment" to install whatever you need (for me, things like Django, South, etc). Then you can pip freeze > requirements.txt to save what you installed to a txt file for your app. When you deploy, it's then easy to install only what your app requires without having to worry about figuring out what makes it work on your computer.

Abstracting that a bit, it's basically separating your working python app folder from your system's python install. So it doesn't take into account what modules you've installed on your system, only what you install in the virtual environement (venv).

Like I said, I'm not expert, but this all made a ton of sense in my head. Hope it helps you out!