installation into a virtualenv is heavily recommended. 1.2.1 virtualenv Virtualenv is probably what you want to use for developing Click applications. What problem does virtualenv solve? Chances are have conflicting dependencies? 1.2. Quickstart 5 Click Documentation, Release 3.3 Virtualenv to the rescue! Virtualenv enables multiple side-by-side installations of Python, one for each project. It doesn’t isolated. Let’s see how virtualenv works. If you are on Mac OS X or Linux, chances are that one of the following two commands will work for you: $ sudo easy_install virtualenv or even better: $ sudo

installation into a virtualenv is heavily recommended. 1.2.1 virtualenv Virtualenv is probably what you want to use for developing Click applications. What problem does virtualenv solve? Chances are conflicting dependencies? 1.2. Quickstart 5 Click Documentation, Release 4.2.dev0 Virtualenv to the rescue! Virtualenv enables multiple side-by-side installations of Python, one for each project. It doesn’t isolated. Let’s see how virtualenv works. If you are on Mac OS X or Linux, chances are that one of the following two commands will work for you: $ sudo easy_install virtualenv or even better: $ sudo

installation into a virtualenv is heavily recommended. 1.2.1 virtualenv Virtualenv is probably what you want to use for developing Click applications. What problem does virtualenv solve? Chances are have conflicting dependencies? 1.2. Quickstart 5 Click Documentation, Release 6.7 Virtualenv to the rescue! Virtualenv enables multiple side-by-side installations of Python, one for each project. It doesn’t isolated. Let’s see how virtualenv works. If you are on Mac OS X or Linux, chances are that one of the following two commands will work for you: $ sudo easy_install virtualenv or even better: $ sudo

installation into a virtualenv is heavily recommended. 1.2.1 virtualenv Virtualenv is probably what you want to use for developing Click applications. What problem does virtualenv solve? Chances are conflicting dependencies? 1.2. Quickstart 5 Click Documentation, Release 5.2.dev0 Virtualenv to the rescue! Virtualenv enables multiple side-by-side installations of Python, one for each project. It doesn’t isolated. Let’s see how virtualenv works. If you are on Mac OS X or Linux, chances are that one of the following two commands will work for you: $ sudo easy_install virtualenv or even better: $ sudo

Caution Installation Python Version Dependencies Virtual environments Install Flask Install virtualenv Quickstart A Minimal Application What to do if the Server does not Start Debug Mode Routing Static Open a Shell Environments Debug Mode Environment Variables From dotenv Environment Variables From virtualenv Custom Commands Plugins Custom Scripts PyCharm Integration Development Server Command Line In version of Python, you can continue on to the next section. If you’re using Python 2, see Install virtualenv first. Create an environment Create a project folder and a venv folder within: $ mkdir myproject

that you have a reasonably recent version of virtualenv installed and that you have some basic familiarity with it. Create and activate a virtual env virtualenv env source env/bin/activate Note that if if you’re using Windows, to activate the virtualenv you’ll need: env\Scripts\activate Use the django CMS installer The django CMS installer [https://github.com/nephila/djangocms-installer] is a helpful Install the application from its GitHub repository using pip -e - this also places it in your virtualenv’s src directory as a cloned Git repository: pip install -e git+http://git@github.com/divio/django-

version of Python, you can continue on to the next section. If you’re using Python 2, see Install virtualenv first. Create an environment Create a project folder and a venv folder within: $ mkdir myproject needed to install virtualenv because you are using Python 2, use the following command instead: 1.3. Installation 5 Flask Documentation (1.1.x), Release 1.1.4 $ python2 -m virtualenv venv On Windows: Windows: > \Python27\Scripts\virtualenv.exe venv Activate the environment Before you work on your project, activate the corresponding environment: $ . venv/bin/activate On Windows: > venv\Scripts\activate

that you have a reasonably recent version of virtualenv installed and that you have some basic familiarity with it. Create and activate a virtual env virtualenv env source env/bin/activate Note that if you’re you’re using Windows, to activate the virtualenv you’ll need: env\Scripts\activate Use the django CMS installer The django CMS installer is a helpful script that takes care of setting up a new project. app Install the application from its GitHub repository using pip -e - this also places it in your virtualenv’s src directory as a cloned Git repository: pip install -e git+http://git@github.com/divio/django-polls

that you have a reasonably recent version of virtualenv installed and that you have some basic familiarity with it. Create and activate a virtual env virtualenv env source env/bin/activate Note that if if you’re using Windows, to activate the virtualenv you’ll need: env\Scripts\activate Use the django CMS installer The django CMS installer is a helpful script that takes care of setting up a new project Install the application from its GitHub repository using pip -e - this also places it in your virtualenv’s src directory as a cloned Git repository: pip install -e git+http://git@github.com/divio/django-polls

revisions will cause your database size to increase. Installing in a virtualenv using pip Installing inside a virtualenv [http://www.virtualenv.org] is the preferred way to install any Django installation. This first step is to create the virtualenv: #!/bin/sh sudo pip install --upgrade virtualenv virtualenv --distribute --no-site-packages env You can switch to your virtualenv at the command line by typing: 4 and install libmysqlclient-dev (on Debian-based distro) One example of a script to create a virtualenv Python environment is as follows: #!/bin/sh env/bin/pip install --download-cache=~/.pip-cache