I had similar problem before.
try
"cd " until you reach the directory of "scripts" then type "activate".
same thing to deactivate.
Hadi
On Friday, 18 January 2019 12:46:03 UTC, Django Geek Aditya wrote:
>
> .\scripts\activate.bat is also not working
>>
>> THE SHELL OUTPUT IS ->
> PS
Okay, I see your problem is that you are doing it the wrong way.
Go to the path where you have your virtual environment folder such as
*cd C:\Python_project\project_name\*
if we suppose I have a virtual environment with a directory as '*venv*'
created inside my project directory *'project_name'*
I would switch over to pipenv and leave the details to that.
From: django-users@googlegroups.com [mailto:django-users@googlegroups.com] On
Behalf Of officialjoemay...@gmail.com
Sent: Friday, January 18, 2019 8:04 AM
To: Django users
Subject: Re: problem in activating virtual environment in
I had the same issue today, but i was able to fix it. I use windows 10 too.
Kindly follow this guide to setup your virtualenv:
Step One: This is really important to do because i really don't know what
is the major cause of this errors but what i discovered in my time is the
installation right
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On Thu, Jan 17, 2019 at 11:14:48AM -0800, Django Geek Aditya wrote:
> Shell Output after entering command is
> PS E:\todo> . \Scripts\activate
> . : The term '\Scripts\activate' is not recognized as the name of a cmdlet,
> function, script file, or
I'm using Windows 10
On Friday, January 18, 2019 at 8:39:08 AM UTC+5:30, kannamshivakumar417
wrote:
>
> Can you tell which os ur using.
>
> On Fri 18 Jan, 2019 12:48 am Django Geek Aditya wrote:
>
>> Shell Output after entering command is
>> PS E:\todo> . \Scripts\activate
>> . : The term
>
> .\scripts\activate.bat is also not working
>
> THE SHELL OUTPUT IS ->
PS E:\todo> .\Scripts\activate.bat
.\Scripts\activate.bat : The term '.\Scripts\activate.bat' is not
recognized as the name of a cmdlet, function, script
file, or operable program. Check the spelling of the name, or if a
In Windows, you can active by 'cmd' :D
Vào 02:18:35 UTC+7 Thứ Sáu, ngày 18 tháng 1 năm 2019, Django Geek Aditya đã
viết:
>
> Shell Output after entering command is
> PS E:\todo> . \Scripts\activate
> . : The term '\Scripts\activate' is not recognized as the name of a
> cmdlet, function, script
Use this command this worked for me. Set-ExecutionPolicy
Unrestricted
On Friday, January 18, 2019 at 12:48:35 AM UTC+5:30, Django Geek Aditya
wrote:
>
> Shell Output after entering command is
> PS E:\todo> . \Scripts\activate
> . : The term '\Scripts\activate' is not recognized as the
Can you tell which os ur using.
On Fri 18 Jan, 2019 12:48 am Django Geek Aditya Shell Output after entering command is
> PS E:\todo> . \Scripts\activate
> . : The term '\Scripts\activate' is not recognized as the name of a
> cmdlet, function, script file, or operable
> program. Check the
if linux, then activating the env is source/bin/activate
after changing to that directory
On Thu, Jan 17, 2019 at 10:22 PM Jorge Gimeno wrote:
> I assume that's in Windows Powershell. I think it's .\Scripts\activate.bat
>
> I would also check to ensure that the Scripts folder exists in your
>
I assume that's in Windows Powershell. I think it's .\Scripts\activate.bat
I would also check to ensure that the Scripts folder exists in your current
directory.
-Jorge
On Thu, Jan 17, 2019 at 11:18 AM Django Geek Aditya
wrote:
> Shell Output after entering command is
> PS E:\todo> .
try .\scripts\activate.bat
On Thu, Jan 17, 2019 at 2:18 PM Django Geek Aditya
wrote:
> Shell Output after entering command is
> PS E:\todo> . \Scripts\activate
> . : The term '\Scripts\activate' is not recognized as the name of a
> cmdlet, function, script file, or operable
> program. Check
13 matches
Mail list logo
