Make installs easier on Windows

Issue #54 resolved
Ed McDonagh
created an issue
  • Document the process clearly
    • Installation of python
    • Add Python Scripts to the path
    • Installation of pip
    • Installation of virtualenv
    • Installation of OpenREM
    • Escaping '\' in file path for database
    • Path examples don't have python2.7 in them for Windows

Comments (24)

  1. Ed McDonagh reporter
    • If using virtualenv on Windows shebang is ignored:
      • Activate virtualenv
      • Don't just call script - call python and use relative path to script, ie
      • python path\to\Scripts\

    Otherwise the .py extension means it will be run using the system wide C:\Python27 install and fail.

  2. Ed McDonagh reporter

    Corrected title underlines and a spelling, turned file paths into code to avoid the backslash disappearing, added a few spaces to make an intended codeblock work, modified the microsoft link to make that work. Refs #80 and #54.

    → <<cset 5f4cf1ffcad6>>

  3. Ed McDonagh reporter

    Added check after pip is installed to make sure it can be called directly. Removed python -m pip instruction for WIndows, as this isn't required if the scripts folder is on the path. Removed note about path for importing data for the same reason. Refs #54.

    → <<cset dc4dc341b1e0>>

  4. Log in to comment