-
-
Notifications
You must be signed in to change notification settings - Fork 617
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
Unexpected piptools.exceptions.NoCandidateFound based on -e #562
Comments
To isolate the issue, could you try performing a As a sidenote, I should mention that |
I renamed the above
|
That would point out there's a difference between how the If I compare: and pip-tools/piptools/scripts/compile.py Line 172 in 2439a7f
I don't have the time to go through |
I will experiment with that. |
this is now fixed in pipenv. Please note that |
thanks for the help, @vphilippon! |
Good call @vphilippon :-)
Le mar. 19 sept. 2017 à 18:59, Kenneth Reitz <[email protected]> a
écrit :
… thanks for the help, @vphilippon <https://github.com/vphilippon>!
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#562 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ABX6cvnrbAOnHReveNl9vyg5uU1h_1tBks5sj_MHgaJpZM4PbjwT>
.
|
@kennethreitz On pipenv 7.3.2 the Separately, can you share (or link me to) more details about what's wrong with Flask 0.9's setup.py?
|
try again with latest |
pipenv, version 7.3.6 Two new errors. This:
And:
which looks like the same as https://github.com/kennethreitz/pipenv/issues/512#issuecomment-330670460 |
I have the same issue, but I'm trying to install
As you can see My
|
Closing since the pip-tools error no longer happens. However the pipenv problems remains, I opened https://github.com/kennethreitz/pipenv/issues/671 |
Trying to use pipenv causes an unexcepted NoCandidatesFound piptools error. I was sent here from https://github.com/kennethreitz/pipenv/issues/468 (cc @kennethreitz) and have simplified to a reproducible case below.
It seems that the
-e
syntax is not properly being respected for pinning my desired version of Flask-SQLAlchemy.Environment
requirements.txt:
Expected
Running
pipenv install
should work, installing Flask==0.9, flask-migrate==1.8.0, and Flask-SQLAlchemy to my forked version of 2.1.Actual
Error, as shown below.
Steps:
Piptools seems to not be respecting the
-e
line and instead is pulling the non-forked version of Flask-SQLAlchemy which requires Flask >=0.10 instead of my fork which only requires Flask>=0.9.The text was updated successfully, but these errors were encountered: