Specify python3 when creating a virtualenv in README
This app is now python3 only so we must specify python3 when creating a virtualenv. Yes this assumes that most people are using python2 as default, most distros still ship this way.
This commit is contained in:
		
							parent
							
								
									db3e6bbffe
								
							
						
					
					
						commit
						60308952fd
					
				
					 1 changed files with 6 additions and 3 deletions
				
			
		|  | @ -45,10 +45,13 @@ VirtualEnv | |||
| 
 | ||||
| Not all things are lovely, so we use constraints to force the versions we | ||||
| we wish for without having to do anything ugly.  This may require a newer | ||||
| version of pip than is packaged with distros virtualenv | ||||
| version of pip than is packaged with distros virtualenv. | ||||
| 
 | ||||
| - ``virtualenv2 ve2`` | ||||
| - ``source ./ve2/bin/activate`` | ||||
| Note that this application is python 3 only so you must create your virtualenv | ||||
| with a python3 interpretter. | ||||
| 
 | ||||
| - ``virtualenv -p `which python3` venv`` | ||||
| - ``source ./venv/bin/activate`` | ||||
| - ``pip install -c constraints.txt -r requirements.txt`` | ||||
| 
 | ||||
| Pre-post-start configuration | ||||
|  |  | |||
		Loading…
	
	Add table
		
		Reference in a new issue
	
	 Jamie Lennox
						Jamie Lennox