On 2016-11-06, Michael Torrie wrote:
> I'm guessing that it notices by examining the path it was launched from
> and looks for virtual environment files relative to that path.
Indeed, the mysterious thing is what are "virtual environment files"?
The official docs say "A venv is a directory tree w
On 2016-11-06, Chris Angelico wrote:
> On Sun, Nov 6, 2016 at 4:27 PM, Jon Ribbens wrote:
>>> 2) If Python notices that its executable comes from a venv, it uses it.
>>
>> Yes. My question is *how does it notice*?
>
> I could answer this question, but since you don't appear to be
> following the
On 11/05/2016 11:27 PM, Jon Ribbens wrote:
>> 2) If Python notices that its executable comes from a venv, it uses it.
>
> Yes. My question is *how does it notice*?
I'm guessing that it notices by examining the path it was launched from
and looks for virtual environment files relative to that path
On Sun, Nov 6, 2016 at 4:27 PM, Jon Ribbens wrote:
>> 2) If Python notices that its executable comes from a venv, it uses it.
>
> Yes. My question is *how does it notice*?
I could answer this question, but since you don't appear to be
following the thread properly, I'll point out that it's alread
On 2016-11-06, Ben Finney wrote:
> Jon Ribbens writes:
>
>> He […] lied about me "not arguing in good faith"
>
> I find you to be not arguing in good faith;
I find that to be particularly pompous of you. I am arguing in good
faith regardless of your misguided opinion.
I wasn't actually even try
Jon Ribbens writes:
> He […] lied about me "not arguing in good faith"
I find you to be not arguing in good faith; if you consistently engage
someone in a manner that requires response, that's not consistent with
also “wondering when they'd shut up”.
> So yes, I view him bowing out of the conve
On 2016-11-06, Ben Finney wrote:
> Jon Ribbens writes:
>> On 2016-11-06, Steve D'Aprano wrote:
>> > *plonk*
>>
>> Thank feck for that, I was beginning to think he'd never shut up.
>
> Really? I didn't see a single message from Steven that wasn't solicited
> by an assertion from you that needed r
On 2016-11-06, Chris Angelico wrote:
> On Sun, Nov 6, 2016 at 3:03 PM, Jon Ribbens wrote:
>> I don't suppose anyone else more constructive and informed actually
>> knows the answer to my rather simple question of how Python knows
>> it's in a venv? ;-)
>
> Two ways.
>
> 1) Normally, you 'activate
Jon Ribbens writes:
> On 2016-11-06, Steve D'Aprano wrote:
> > *plonk*
>
> Thank feck for that, I was beginning to think he'd never shut up.
Really? I didn't see a single message from Steven that wasn't solicited
by an assertion from you that needed response.
If your concept of “won't shut up”
On Sun, Nov 6, 2016 at 3:03 PM, Jon Ribbens wrote:
> I don't suppose anyone else more constructive and informed actually
> knows the answer to my rather simple question of how Python knows
> it's in a venv? ;-)
Two ways.
1) Normally, you 'activate' the venv by sourcing a script into your
shell.
On 2016-11-06, Steve D'Aprano wrote:
> *plonk*
Thank feck for that, I was beginning to think he'd never shut up.
I don't suppose anyone else more constructive and informed actually
knows the answer to my rather simple question of how Python knows
it's in a venv? ;-)
--
https://mail.python.org/m
On Sun, 6 Nov 2016 07:55 am, Jon Ribbens wrote:
>> The implication is that the answer to your question is Yes, you can run
>> Python in the context of a virtualenv by just invoking that virtualenv's
>> local Python without running 'activate' first.
>
> So you were wrong earlier when you said you
Steve D'Aprano writes:
> Oh, and ironically, you'll see that Ben anticipated and answered your
> question about activate. Here's the link again, to save you scrolling up:
>
> https://mail.python.org/pipermail/python-list/2016-October/715994.html
>
> where he says:
>
> If you already have a sp
On 2016-11-05, Steve D'Aprano wrote:
> On Sun, 6 Nov 2016 02:55 am, Jon Ribbens wrote:
>> I'm afraid I can only suggest that you try re-reading the subthread
>> again until you manage to understand it. It wasn't really that
>> complicated but you seem to have confused yourself greatly.
>
> Are you
On Sun, Nov 6, 2016 at 3:53 AM, Steve D'Aprano
wrote:
> [1] Technically, the application being run may invoke different behaviour
> depending on the name it was invoked by. Some editors do that, e.g.
> the "joe" editor. But I don't believe Python does anything like this.
>
> http://joe-editor.sour
On Sun, 6 Nov 2016 02:55 am, Jon Ribbens wrote:
> I'm afraid I can only suggest that you try re-reading the subthread
> again until you manage to understand it. It wasn't really that
> complicated but you seem to have confused yourself greatly.
Are you serious?
Okay. Here's the start of the thre
On 2016-11-05, Steve D'Aprano wrote:
> Your implied question here:
>
>> Maybe he meant what you are saying, I don't know, but
>> it isn't what he wrote. He clearly implied that you can run Python
>> in the context of a virtualenv by just invoking that virtualenv's
>> local Python without running
On Sat, 5 Nov 2016 08:45 pm, Jon Ribbens wrote:
> On 2016-10-31, Steve D'Aprano wrote:
>> On Mon, 31 Oct 2016 07:21 pm, Jon Ribbens wrote:
>>> On 2016-10-31, Ben Finney wrote:
Instead, you should invoke the exact Python interpreter you want – and,
by extension, the Python environment i
On 2016-10-31, Steve D'Aprano wrote:
> On Mon, 31 Oct 2016 07:21 pm, Jon Ribbens wrote:
>> On 2016-10-31, Ben Finney wrote:
>>> Instead, you should invoke the exact Python interpreter you want – and,
>>> by extension, the Python environment into which you want packages
>>> installed.
>>>
>>>
On Mon, 31 Oct 2016 07:21 pm, Jon Ribbens wrote:
> On 2016-10-31, Ben Finney wrote:
>> Instead, you should invoke the exact Python interpreter you want – and,
>> by extension, the Python environment into which you want packages
>> installed.
>>
>> $ /foo/bar/virtualenv/bin/python3 -m pip inst
On 2016-10-31, Ben Finney wrote:
> Instead, you should invoke the exact Python interpreter you want – and,
> by extension, the Python environment into which you want packages
> installed.
>
> $ /foo/bar/virtualenv/bin/python3 -m pip install LoremIpsum
I'm slightly curious about that. /foo/bar
> How do I fix this?
Maybe:
$ brew uninstall python3
$ brew install python3
--
https://mail.python.org/mailman/listinfo/python-list
Vishal Subbiah writes:
> Hi,
(Please don't top-post in responses. Instead, post your responses
interleaved with only the quoted material you are responding to
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style>.)
> Thanks Ben for the response. I followed your suggestion and this is
>
On Mon, Oct 31, 2016 at 12:15 PM, Vishal Subbiah
wrote:
> "python3 -m pip install LoremIpsum
> /usr/local/opt/python3/bin/python3.5: No module named pip"
>
> How do I fix this?
This is the one that ought to work. Something's gone wrong with the
installation; as part of the install of recent Pytho
Hi,
Thanks Ben for the response. I followed your suggestion and this is what i
get:
"python3 -m pip3 install LoremIpsum
/usr/local/opt/python3/bin/python3.5: No module named pip3"
"python3 -m pip install LoremIpsum
/usr/local/opt/python3/bin/python3.5: No module named pip"
How do I fix this?
R
Vishal Subbiah writes:
> So I wads trying to install some packages for python3. when I run pip3
> in terminal
There is no guarantee that a command named ‘pip3’ will be installed.
Instead, you should invoke the exact Python interpreter you want – and,
by extension, the Python environment into wh
26 matches
Mail list logo
