Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.python > #109346
| From | Marc Brooks <marcwbrooks@gmail.com> |
|---|---|
| Newsgroups | comp.lang.python |
| Subject | Re: How to create development Python environment on Linux. |
| Date | 2016-06-01 20:30 -0400 |
| Message-ID | <mailman.81.1464857527.1839.python-list@python.org> (permalink) |
| References | <815aa265-45c4-40a4-860d-beb89cd9a78e@googlegroups.com> <CAKJDb-NxpmGihicjxHt3W3i5OUPWH22-3OO5OzwM+fc6jOV=Dg@mail.gmail.com> <mailman.19.1463415968.19823.python-list@python.org> <1833e379-3401-4d1b-9551-2760c72e01af@googlegroups.com> <CAN+KW4pNVYSuA4fQ+_+gOp-RPPvetU0D+b_9kVCOAjw08LGD+A@mail.gmail.com> |
I am pretty sure (but not 100%) that the pip that virtualenv installs when it first creates the virtualenv is the version of pip installed on the system. Here's the process I used to bootstrap a new Python 2.7 dev environment. 1. Download and install the latest version of pip as sudo so it's system wide. 2. Install virtualenv and virtualenvwrapper (a collection of utilities scripts/aliases for virtualenv). 3. Update my .bash_profile to source the virtualenvwrapper script. Then for any new virtualenvs I just type 'mkvirtualenv <foo>' I can update the version of pip in the virtualenv or run pip install for any of my required libraries at that point. One wrinkle that can come up is if you want to use virtualenvwrapper and you are not using bash. Fish (another moderately popular shell) has an addon that mimics the macros that virtualenvwrapper provides. Mar On Wed, Jun 1, 2016 at 8:17 PM, Lawrence D’Oliveiro <lawrencedo99@gmail.com> wrote: > On Tuesday, May 17, 2016 at 4:26:23 AM UTC+12, Zachary Ware wrote: > > Not what you asked for, but I would encourage you to look into whether > > it's possible for you to use Python 3 instead of Python 2 for what > > you're doing. If it's possible, starting with Python 3 will save you > > several headaches in the future. > > Let me add my vote for this. > > > sys.prefix is baked in at compile time of the python interpreter ... > > ldo@theon:~> ~/virtualenv/jupyter/bin/python -c "import sys; > print(sys.prefix)" > /home/ldo/virtualenv/jupyter > -- > https://mail.python.org/mailman/listinfo/python-list >
Back to comp.lang.python | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
How to create development Python environment on Linux. redirect.null@gmail.com - 2016-05-16 04:22 -0700
Re: How to create development Python environment on Linux. redirect.null@gmail.com - 2016-05-16 04:29 -0700
Re: How to create development Python environment on Linux. Zachary Ware <zachary.ware+pylist@gmail.com> - 2016-05-16 11:25 -0500
Re: How to create development Python environment on Linux. Lawrence D’Oliveiro <lawrencedo99@gmail.com> - 2016-06-01 17:17 -0700
Re: How to create development Python environment on Linux. Marc Brooks <marcwbrooks@gmail.com> - 2016-06-01 20:30 -0400
Re: How to create development Python environment on Linux. redirect.null@gmail.com - 2016-05-16 14:28 -0700
Re: How to create development Python environment on Linux. Michael Selik <michael.selik@gmail.com> - 2016-05-16 21:56 +0000
Re: How to create development Python environment on Linux. Zachary Ware <zachary.ware+pylist@gmail.com> - 2016-05-17 10:32 -0500
csiph-web