Closed imcom closed 9 years ago
I had this same issue a while back. The problem is newer versions of pip
have stopped trusting hosts by default, so the old local pypi workflow described in the docs will not work anymore.
I just submitted PR #134 that fixes this by added any explicitly defined pypi server as a trusted host when calling pip
.
Hope that helps!
hi @mzbyszynski
I've tried your approach or a similar one,
I add --trusted-host 0.0.0.0
to the build command like this:
cmd = [os.path.join(self.path, "bin", "pip"), "install", package, "--trusted-host 0.0.0.0"]
but still got no luck ...and I did not see how is it different from your PR ... I mean technically they are identical right?
hi @mzbyszynski
Turns out, your approach or my dirty hack is working ... but it just does not work with virtualenv.
I re-installed the customized pyleus in the host env instead of a virtual one then I got things work out like a charm ...
when I used virtualenv, the binary pyleus
I installed in virtual env seemed to be not called, and the one in host env was called instead ... it is confusing
Hmm, I believe virtualenv was working for me last time I tried with this fix. I did have to first do pip install /path/to/project/pyleus/dist/pyleus-0.2.4.tar.gz
to in my virtual env first, before running any of the pyleus commands.
when using the dev config as stated in document:
I could not get rid of the error message:
when run
pyleus build ...yaml
thepip install
would fail with the local pypi server.I even tried to add
--trusted-host
tobuild.py
and reinstall pyleus from source, but it is still a no go.Please help to clarify how should I set up a dev environment.
I am going to open a pull request for adding some more config to topology, I really need a dev environment up and running ...