i was actually going through a tutorial where i specifically needed 
pyenv-virtualenv. 
but thanks for ur consideration @gerardo.palazuelos

On Sunday, 10 January 2021 at 22:16:43 UTC+5:30 Gerardo Palazuelos wrote:

> Hi Sohail,
> I read your interest for pipenv in Windows. Seems are wasting precious 
> time and not productive because of this pipenv tool, which is not even the 
> point of Django.
>
> If that keeps resulting complicated, may I suggest you to use venv which 
> comes integrated in recent Python installation. You have to install nothing 
> else other than Python.
>
> I code Python in Windows using venv - no issues.
>
> In your desired folder, to create virtual environment:
> python -m venv the-name-of-my-virtual environment 
>
> Usually I do this (yes, I put a dot in name of my virtual environment):
> python -m venv .venv
>
> Then, using gitbash, to activate virtual environment in Windows (assuming 
> you are in same desired folder):
> . \.venv\Scripts\activate
>
> If not using gitbash, enter to folder .venv\Scripts and run activate - 
> it’s a .bat program 
>
> That should work.
> Regards,
>
> ---
> Gerardo
>
>
>
> El 10 ene 2021, a la(s) 9:28, Sohail Tanveer <sohailta...@gmail.com> 
> escribió:
>
> the git repo to which google directs me is 
> https://github.com/pyenv/pyenv-virtualenv
>
> the command it wants me to execute in my cmd is   $ git clone 
> https://github.com/pyenv/pyenv-virtualenv.git $(pyenv 
> root)/plugins/pyenv-virtualenv 
> and whenever i execute this it shows an error like 
>
>
>
> fatal: Too many arguments.
>
> usage: git clone [<options>] [--] <repo> [<dir>]
>
>     -v, --verbose         be more verbose
>     -q, --quiet           be more quiet
>     --progress            force progress reporting
>     -n, --no-checkout     don't create a checkout
>     --bare                create a bare repository
>     --mirror              create a mirror repository (implies bare)
>     -l, --local           to clone from a local repository
>     --no-hardlinks        don't use local hardlinks, always copy  
>     -s, --shared          setup as shared repository
>     --recurse-submodules[=<pathspec>]
>                           initialize submodules in the clone      
>     --recursive ...       alias of --recurse-submodules
>     -j, --jobs <n>        number of submodules cloned in parallel 
>     --template <template-directory>
>                           directory from which templates will be used
>     --reference <repo>    reference repository
>     --reference-if-able <repo>
>                           reference repository
>     --dissociate          use --reference only while cloning      
>     -o, --origin <name>   use <name> instead of 'origin' to track 
> upstream
>     -b, --branch <branch>
>                           checkout <branch> instead of the remote's HEAD
>     -u, --upload-pack <path>
>                           path to git-upload-pack on the remote   
>     --depth <depth>       create a shallow clone of that depth    
>     --shallow-since <time>
>                           create a shallow clone since a specific 
> time
>     --shallow-exclude <revision>
>                           deepen history of shallow clone, excluding rev
>     --single-branch       clone only one branch, HEAD or --branch 
>     --no-tags             don't clone any tags, and make later fetches not 
> to follow them
>     --shallow-submodules  any cloned submodules will be shallow   
>     --separate-git-dir <gitdir>
>                           separate git dir from working tree      
>     -c, --config <key=value>
>                           set config inside the new repository    
>     --server-option <server-specific>
>                           option to transmit
>     -4, --ipv4            use IPv4 addresses only
>     -6, --ipv6            use IPv6 addresses only
>     --filter <args>       object filtering
>     --remote-submodules   any cloned submodules will use their 
> remote-tracking branch
>     --sparse              initialize sparse-checkout file to include only 
> files at root 
>
> On Sunday, 10 January 2021 at 20:20:02 UTC+5:30 Kasper Laudrup wrote:
>
>> On 09/01/2021 19.27, Sohail Tanveer wrote: 
>> > im facing difficulty to install pyenv-virtual env on my windows 10 
>> > i googled it several times but it directs me to a git repo where there 
>> > is an installation process but is of no use because, the command that 
>> is 
>> > displayed is not working in my cmd 
>>
>> It would greatly improve your chances of getting some useful help if you 
>> clarify which git repo you are talking about, which command you are 
>> trying to using and what exactly you mean by "not working". 
>>
>> Unless you want to leave that as an exercise for the reader. 
>>
>> Kind regards, 
>>
>> Kasper Laudrup 
>>
> -- 
>
> You received this message because you are subscribed to the Google Groups 
> "Django users" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to django-users...@googlegroups.com.
>
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/django-users/86f2fc8d-a20f-4a94-bda6-81d1e4177fb8n%40googlegroups.com
>  
> <https://groups.google.com/d/msgid/django-users/86f2fc8d-a20f-4a94-bda6-81d1e4177fb8n%40googlegroups.com?utm_medium=email&utm_source=footer>
> .
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-users/98f7471b-31d3-4bba-ac50-005dcd772a9fn%40googlegroups.com.

Reply via email to