Development Setup on Windows

[jayvdb]

https://api.coala.io/en/latest/Developers/Development_Setup.html mentions source, which is not going to work on Windows if the developer is trying those commands in a cmd.exe

Also Windows doesnt have python3 ; it only has python. Yippee.

[gitmate-bot]

GitMate.io thinks possibly related issues are #196 (Windows support), #130 (windows support), #390 (windows build), #291 (Windows: UnicodeEncodeError), and #496 (glob: windows support).

[VickedVic]

https://api.coala.io/en/latest/Developers/Development_Setup.html uses venv, but windows doesn't recognize that, it works fine with .\foo

[VickedVic]

c:\>virtualenv .\foo ==> to create virtual environment

and

c:\> .\foo\scripts\activate ==> to activate it

[VickedVic]

detailed steps with changes
https://github.com/VickedVic/r1/blob/sarah/GSoC/sarah1/development-setup-notes(windows).txt

[VickedVic]

Okay, i've tried this the entire day, and it seems to works only in this way at the moment:

Setting up virtualenv with foo and activating scripts:

C:\> cd working_dir #move into the dir where you want to create virtual environment for both
#command prompt and powershell

now we will need to run the virtualenv using .\foo

C:\Path\to\your\directory>virtualenv .\foo
Using base prefix 'c:\Path\to\appdata\local\programs\python\python36-32'
New python executable in C:\Path\to\your\directory\foo\Scripts\python.exe
Installing setuptools, pip, wheel...done.

now activate it using the scripts of .\foo

C:\Path\to\your\directory> .\foo\scripts\activate

Powershell has slightly different method:

PS C:> Set-ExecutionPolicy AllSigned

PS C:> virtualenv .\foo
New python executable in C:\foo\Scripts\python.exe
Installing setuptools................done.
Installing pip...................done.
PS C:> .\foo\scripts\activate

Do you want to run software from this untrusted publisher?
File C:\foo\scripts\activate.ps1 is published by E=jannis@leidel.info,
CN=Jannis Leidel, L=Berlin, S=Berlin, C=DE, Description=581796-Gh7xfJxkxQSIO4E0
and is not trusted on your system. Only run scripts from trusted publishers.
[V] Never run [D] Do not run [R] Run once [A] Always run [?] Help
(default is "D") : A

(foo) PS C:>

To deactivate, simply type:

(foo)C:\Path\to\your\directory> deactivate
C:\Path\to\your\directory>

installing from git:

(foo)C:\Path\to\your\directory>
(foo)C:\Path\to\your\directory> git clone https://github.com/coala/coala
(foo)C:\Path\to\your\directory> cd coala
(foo)C:\Path\to\your\directory> pip3 install .
(foo)C:\Path\to\your\directory> cd.. #cd- doesn't work in command prompt
(foo)C:\Path\to\your\directory> git clone https://github.com/coala/coala-bears
(foo)C:\Path\to\your\directory> cd coala-bears
(foo)C:\Path\to\your\directory> pip3 install .

[Jitender46559]

I want to work on this issue can you please assign me

[shivank1234]

Is this issue open?

[ghost]

The 'install coala' & 'get started' section in https://coala.io/#/home?lang=Python have similar problems on Windows.

Should I file a new issue for that?