-
Notifications
You must be signed in to change notification settings - Fork 20
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
make init
fails if pip is somehow configured in unexpected way
#439
Comments
sounds like issue in python or pip. |
@arai-a they're already at their latest versions, i think those version warnings are coming from the versions jsparagus bundles in the virtual env. |
Doesn't reproduce with:
on macOS after setting up, pip list shows the following:
which OS and python version are you using? also, what happens if you create temporary virtualenv manually and installing each item in requirements.txt ? |
how do i do this |
what does Then, try running the following commands one by one, until any error happens:
|
sorry, before doing the above, please remove |
|
Are you using debian-based distribution? if not, can you tell me which OS and distro and versions you're using? let me know if upgrading pip doesn't solve the issue. |
@arai-a i'm using arch, and all my packages are up to date (rolling release) additionally, my pip is up to date:
The out of date pip appears to be coming from virtualenv:
|
what does |
@arai-a 16.6.2 |
I don't know much about arch tho, there seems to be python-virtualenv package did you install virtualenv with that package? or somewhere else? |
virtualenv seems to have been some python2 package (i never installed it though so idk where it came from). I removed it and installed |
what does |
|
does the issue persist if you remove |
yep |
what happens if you run the following commands, in some temporary empty directory outside of jsparagus?
|
I don't think the init commands are correctly entering the virtualenv. That being said, I also don't know what the correct way is.
|
it would be nice to look into it. then, about entering virtualenv, in most case running command without activating the venv works,
|
@arai-a same issue while activated. |
can you provide the exact output? |
Ok I am learning some things: diff --git a/Makefile b/Makefile
index b94b5b7..032f5ab 100644
--- a/Makefile
+++ b/Makefile
@@ -17,8 +17,9 @@ PIP := $(VENV_BIN_DIR)/pip
all: $(PY_OUT) rust
init-venv:
- python3 -m venv jsparagus_build_venv &&\
- $(PIP) install --upgrade pip &&\
+ python3 -m virtualenv jsparagus_build_venv && \
+ $(PIP) config set install.user no && \
+ $(PIP) install --upgrade pip && \
$(PIP) install -r requirements.txt
init: init-venv It's all working now |
this will be written into your user configuration (somewhere around I'll check if there's a way to avoid getting affected from it. |
the real fix was changing |
Just to make sure, can you test the following?
|
seems like unmodified makefile works now... idk what changed 🤷♂️ |
okay, then it should be that your user configuration was affecting |
make init
fails from pyenvmake init
fails if pip is somehow configured in unexpected way
just trying to set this up and test it out, getting some cryptic errors from
make init
:The text was updated successfully, but these errors were encountered: