-
Notifications
You must be signed in to change notification settings - Fork 144
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
Support editable install #93
Conversation
Hi @matham thanks for this PR! A portion of this PR looks like it solves current issue #19. Thanks! I'll review the editable install portion and try it out locally and then get back to you. Generally I've been able to install from lava repo with |
Makes sense. Feel free to edit the PR code directly. Or I can do it as well if you specific changes in mind. |
It probably makes sense to offer |
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.
+1.
Install works locally and should ease development install.
Sorry about the long review wait @matham. This is mostly down to holidays and some near term deadlines. |
Once this is merged we need to update the FAQ with updated install instructions https://github.com/lava-nc/lava/wiki/Frequently-Asked-Questions-(FAQ) and official docs need to be updated at least here |
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.
Looks good. Does this solve Issue #19?
Thanks for the review @PhilippPlank! Yes it solves #19, as I mentioned in my first comment. I've also linked it to #19. |
* Add setuptools to support editable install. * Update install docs to support editable install.
Currently, to use lava from a cloned repo, you have to mess with the
PYTHONPATH
which is not ideal.Typically, this is avoided by supporting an editable install. Then, you just have to do
pip install -e .
from the root, and things will work as any normally installed package. The problem is that you need to specifysetuptools
as a dependency inpyproject.toml
.PYTHONPATH
.python
ispython
, notpython3
.pip install -U pip
didn't work failing with some kind of permission error if I can remember correctly. Sopython -m pip install --upgrade pip
seemed like the more normal and less likely to fail command. I didn't update the linux instructions for this, although you probably should, since I didn't test.Scripts
, notbin
. So I updated that.source python3_venv/Scripts/activate
without the.bat
suffix. If you use the normal cmd/powershell terminal, thensource
doesn't work so you just dopython3_venv/Scripts/activate.bat
. But, I couldn't test this right now on cmd, so I didn't change this part.On my system, with the changes it worked: