Skip to content
This repository has been archived by the owner on Apr 18, 2023. It is now read-only.

Running test.sh on Windows 10 #127

Open
bghughes opened this issue Jan 8, 2020 · 2 comments
Open

Running test.sh on Windows 10 #127

bghughes opened this issue Jan 8, 2020 · 2 comments

Comments

@bghughes
Copy link

bghughes commented Jan 8, 2020

I am trying to run the test.sh script on Windows 10 after installation. I noticed that virtualenv on Windows 10 downloads the activate/deactivate files into the "Scripts" folder (vs bin on Linux). After changing the test.sh file to:
source _virtualenv/Scripts/activate
I am able to launch the virtualenv for testing purposes as intended. However, it does not seem that the PYTHONPATH line is working on my system. I receive the error (after doing the above and running test.sh):

File "C:\Users\XYZ\workspace\market-maker-keeper\tests\conftest.py", line 20, in <module>
    from pymaker.deployment import Deployment
ModuleNotFoundError: No module named 'pymaker'

This leads me to believe that there is an issue with test.sh changing the pythonpath for the tests. Any guidance on how I can get my tests performed on Windows 10 would be greatly appreciated. Love the project - Thanks!

@grandizzy
Copy link
Contributor

grandizzy commented Feb 11, 2020

for windows is a little bit different, you have to
set PYTHONPATH=%PYTHONPATH%;C:\My_python_lib
see https://docs.python.org/3.6/using/windows.html#excursus-setting-environment-variables

best way to do that would be to run tests in Docker containers (so will be same for all OSes) similar with what we do in pymaker

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants
@bghughes @grandizzy and others