On 05/29/2017 08:09 PM, Ben Finney wrote:
You should probably disregard this message as I have since solved the
problem I was asking about. I originally wrote this message on 01/27/17,
how it make it back to the list I don't know.
Regards, Jim
Jim writes:
It has been suggested to me tha
Jim writes:
> It has been suggested to me that I should use a virtual environment
> and venv would be a good choice. I've read through PEP405 and this
> link [1].
One possible confusion is the terminology.
You have “a virtual environment” when you create one. The ‘venv’ module
is not itself a v
On Fri, Jan 27, 2017 at 7:47 PM, Jim wrote:
>
> [...] This question seems a little dumb and maybe I am being a little dense,
> but then what?
Imagine that you are working on 5 different Python projects, each
using different packages with different versions. We can break this
down in two situatio
On 01/27/2017 04:49 PM, Cameron Simpson wrote:
On 27Jan2017 15:47, jim wrote:
It has been suggested to me that I should use a virtual environment
and venv would be a good choice. I've read through PEP405 and this
link [1].
Though some of it seems a little confusing to me, I'm sure I can get
it
On 27Jan2017 15:47, jim wrote:
It has been suggested to me that I should use a virtual environment
and venv would be a good choice. I've read through PEP405 and this
link [1].
Though some of it seems a little confusing to me, I'm sure I can get
it up and running. This question seems a little d
It has been suggested to me that I should use a virtual environment and
venv would be a good choice. I've read through PEP405 and this link [1].
Though some of it seems a little confusing to me, I'm sure I can get it
up and running. This question seems a little dumb and maybe I am being a
little
