-
-
Notifications
You must be signed in to change notification settings - Fork 1.9k
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
pipenv lock --pre won't change #2201
Comments
Sure thing! Pre-releases (I know this term doesn’t make sense) are just releases tagged with an ‘alpha’, ‘beta’, ‘dev’ or ‘rc’ tag so basically 1.0.3 is a normal release while 1.0.3rc1 is 1.0.3 release candidate 1 and is a pre-release. That just means that someday 1.0.3 will be released and that this version is a precursor to that which isn’t finished. We have had other issues specifically related to Do you still think the |
doing: #1802 (comment) |
The output is indeed a bit strange: [packages]
eth-account = "==0.1.0a2"
eth-hash = "==0.1.2"
numpy = "==1.14.2"
web3 = "==3.16.5"
Notice the log says it’s skipping pre-versions, even when I specified |
I think |
oh, I just got around to reading this. Lets look at the error message: The versions we skip aren't super useful, because if you look carefully they are usually duplicated a bunch. We skip lots of stuff, this is one of the reasons I wasn't totally on board with showing the listing of skipped prerelease versions in the first place. This is super misleading -- it implies that we skipped these versions because they were prerelease versions. What actually happened is that we skipped these versions, and also, they happened to be prerelease versions. I can tell you without looking at any code or doing any dependency resolution that there is no such version that will satisfy Anyway I've fielded dozens of issues related to this set of ethereum tooling, the maintainers just seem to randomly pin stuff that conflicts across all of their software. Pip doesn't have a dependency resolver, it will always install whatever you tell it to install. That is one of the key distinguishing features of pipenv -- if you want to install 5 packages, and 3 of them try to install conflicting versions of |
I’m not sure how the logic works, but shouldn’t 0.2.0b1, 0.2.0b2, and 0.2.0b3 all be considered matching this criteria? |
Hm yeah, you're right about that, sorry, didn't look that carefully at the actual values (been working on the release) I am willing to bet if you install and skip locking you'll find lots of conflicts, I don't really want to use this as a test case for any resolver issues. I looked for 3 seconds and found some. For instance, this is how pip resolves this particular conflict:
Or here's another one:
|
same issue. use
|
installed packages from requirements
pipenv run pip install -r requirements.txt
it works correctly
so
pipenv graph
returns same aspipenv run pip freeze
but I can not create lock file, nor
pipenv lock
, orpipenv lock --pre
eitherpipenv graph
output:notice rlp == 0.6.0 and eth-utils==0.8.1
but PIpfile.lock:
different versions.
How to make them consistent.
and Yes, I've searched for an issues,
--pre
key won't solve my problem.Could you please be more verbose in your arguments, what exactly means 'Allow pre–releases.'.
Thanks
The text was updated successfully, but these errors were encountered: