On Mon, 20 May 2013 19:40:28 +0100
Stestagg wrote:
> . bin/activate will only work with bash compatible shells.
>
> Try . bin/activate.fish. instead
Ahh, stupid me. :-(
It' OK now...
Sincerely,
Gour
--
Perform your prescribed duty, for doing so is better than not
working. One cannot even
Sorry, I see the chain now, you knew that
The snippet you pasted did use the bash version tho
Steve
On 20 May 2013 19:40, "Stestagg" wrote:
> . bin/activate will only work with bash compatible shells.
>
> Try . bin/activate.fish. instead
>
> Steve
> On 20 May 2013 19:12, "Gour" wrote:
>
>> On
. bin/activate will only work with bash compatible shells.
Try . bin/activate.fish. instead
Steve
On 20 May 2013 19:12, "Gour" wrote:
> On Fri, 21 Sep 2012 13:46:25 +0100
> Peter Flood wrote:
>
> > I had exactly that problem until I updated virtualenv to 1.8.2 (I
> > think I was on 1.7.? befor
On Fri, 21 Sep 2012 13:46:25 +0100
Peter Flood wrote:
> I had exactly that problem until I updated virtualenv to 1.8.2 (I
> think I was on 1.7.? before), now all is good. I assume the
> activate.fish script has been updated in the latest version (you'll
> have to delete and recreate your virtuale
On Fri, 21 Sep 2012 13:46:25 +0100
Peter Flood wrote:
> I had exactly that problem until I updated virtualenv to 1.8.2 (I
> think I was on 1.7.? before), now all is good.
Thanks...it seems I've to wait for 1.8.2 package.
> I assume the activate.fish script has been updated in the latest
> ver
I had exactly that problem until I updated virtualenv to 1.8.2 (I think
I was on 1.7.? before), now all is good. I assume the activate.fish
script has been updated in the latest version (you'll have to delete and
recreate your virtualenvs to use the new script, use a requirements file
to do so)
On Sun, 12 Aug 2012 15:31:27 +1000
Christopher Nilsson
wrote:
> That's odd. I see the updated activate.fish in the latest 1.7.2
> release (that github account linked to is the upstream).
After updating virtualenv to 1.8.2, I've new problem with it..
Here is result of 'activating' virtualenv:
g
On Sun, 12 Aug 2012 15:31:27 +1000
Christopher Nilsson
wrote:
> That's odd. I see the updated activate.fish in the latest 1.7.2
> release (that github account linked to is the upstream).
/me nods
> While you've updated your virtualenv version, the existing projects
> you've created won't automa
Hey Gour,
That's odd. I see the updated activate.fish in the latest 1.7.2 release
(that github account linked to is the upstream).
While you've updated your virtualenv version, the existing projects you've
created won't automatically get updated. You'll either need to copy the
new files to your
On Sat, 11 Aug 2012 18:25:28 +1000
Christopher Nilsson
wrote:
Hiya Chris,
> That fix of mine eventually got hacked on, and wonderfully superceded
> with a version that skips needing any temp files at all.
>
> https://github.com/pypa/virtualenv
>
> Looks like that went in at least 4 months ago.
Hi Gour,
Been a while since I looked at this. But yep, tempfile wasn't as common as
I initially thought.
There's a slightly more recent version of the "activate.fish" script here:
https://bitbucket.org/otherchirps/virtualenv
This one relies on the GNU coreutils 'mktemp' command instead.
BUT,
Hello,
I've problem when trying to use virtualenv:
gour@atmarama ~/p/mezzanine $ . bin/activate.fish
fish: Unknown command “tempfile”
/home/gour/prj/mezzanine/bin/activate.fish (line 1): tempfile
^
in command substitution
called on li
12 matches
Mail list logo
