-
Notifications
You must be signed in to change notification settings - Fork 17
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
README: Update all setup/installation instructions #33
README: Update all setup/installation instructions #33
Conversation
(Look here to view the document with formatting.) |
[global] | ||
target=C:\SomeDir\Where\Your\Account\Can\Write\To | ||
```sh | ||
python3 -m venv venv |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I guess the same way as for pipenv local
we need to add here source venv/bin/activate
.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Fixed.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think GitHub actions has to be updated to use python 3.10.6
6d31cf7
to
6776a8a
Compare
Added. |
0fd6548
to
945560f
Compare
945560f
to
b1a621f
Compare
Rebased on master because #32 has been merged |
Meeting decision to merge |
Additional updates. We have a lot of different ways to install now. I had been using
pyenv
but recently Mikhail addedpython -m venv venv
, which is yet another thing, not identical topyenv
as I understand it.So, maybe there are too many ways now but I think this README at least documents them.
I also deprecated
pipenv
method until we get a setup that seems to work correctly.