sipp11
10 years ago
1 changed files with 30 additions and 0 deletions
@ -0,0 +1,30 @@ |
|||||||
|
--- |
||||||
|
layout: post |
||||||
|
title: "Virtualenv with python3" |
||||||
|
author: |
||||||
|
display_name: sipp11 |
||||||
|
login: sipp11 |
||||||
|
email: sipp11@gmail.com |
||||||
|
url: '' |
||||||
|
author_login: sipp11 |
||||||
|
author_email: sipp11@gmail.com |
||||||
|
date: Jul 20, 2015 |
||||||
|
categories: |
||||||
|
- coding |
||||||
|
tags: |
||||||
|
- python3 |
||||||
|
- virtualenv |
||||||
|
--- |
||||||
|
|
||||||
|
Nowadays, although `python2` still are the production preferred choice, `python3` is maturing and surely started taking over. Testing under `python3` environment is pretty easy. |
||||||
|
|
||||||
|
On Linux, most distros have both `python2` and `python3` bundled. However, on OSX, you need to install `python3` by yourself. Fortunately, it is one command away with the magic of `brew`. |
||||||
|
|
||||||
|
$ brew install python3 |
||||||
|
|
||||||
|
Then you could check by calling `python3` if it works. Then you could make a `virtuanenv` with `python3`. |
||||||
|
|
||||||
|
$ mkvirtualenv --python=`which python3` en-py3 |
||||||
|
(en-py3) $ |
||||||
|
|
||||||
|
That's all. Nothing extra required. Happy testing your app on `python3` |
Loading…
Reference in new issue