-
-
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
futures==3.2.0 #1586
Comments
Quick guess:
You might somehow have a corrupted dependency cache that believes (due to previous resolver bug) that |
can no longer reproduce |
i lied |
[[source]]
url = "https://pypi.python.org/simple"
verify_ssl = true
name = "pypi"
[packages]
futures = "*"
[dev-packages]
[requires]
python_version = "3.6" leads to {
"_meta": {
"hash": {
"sha256": "defaf2233df08ddd288f75787d4a8904217ecf22fba389a152b64f50144c6ce6"
},
"pipfile-spec": 6,
"requires": {
"python_version": "3.6"
},
"sources": [
{
"name": "pypi",
"url": "https://pypi.python.org/simple",
"verify_ssl": true
}
]
},
"default": {
"futures": {
"hashes": [
"sha256:51ecb45f0add83c806c68e4b06106f90db260585b25ef2abfcda0bd95c0132fd",
"sha256:c4884a65654a7c45435063e14ae85280eb1f111d94e542396717ba9828c4337f"
],
"version": "==3.1.1"
}
},
"develop": {}
} |
This file: [[source]]
url = "https://pypi.python.org/simple"
verify_ssl = true
name = "pypi"
[packages]
futures = {version = "==3.2", python_version = "<'3.0.0'"} Leads to:
|
Current workaround: lock with Python 2 virtualenv. |
fixed. |
I am experiencing this issue again:
Why does it lock |
Adding |
@jacebrowning good question. Does |
I think i added some resolver fixes last week that aren’t released yet |
@techalchemy Yes, |
@jacebrowning are you using the version from master or the release |
@techalchemy I've been installing from Homebrew lately (which unfortunately makes it harder to test preview releases). |
Can I see the output of |
I don't seem to have a |
Oh boy. It comes with pipenv these days. Is there not one in |
I found it with
|
@jacebrowning this is a resolver bug which hasn’t been fixed in a release yet -part of the resolver changes now include otherwise excluded files, it’s including |
An ugly workaround is to change the virtualenv to Python 2.7, then freeze your requirements file |
I am also getting this when I try to install a py3 virtualenv with pipenv, the only way to get around it seems to be to change the python version being required to py2.7 but this of course breaks because the syntax is py3. Is there a better workaround somewhere? |
@LasseGravesen We’ve since removed dependency to futures altogether. You might want to consider purge your environment (i.e. uninstall everything until |
This is still an issue. at least with brew installed pipenv
Also Can you be more clear about "purge your environment" ? Can we have a link to the "unfixed bug"? @techalchemy |
Given you use |
I'm running into this same issue when installing the Installing the package using pip install works fine. It seems that the following line is not interpeted correctly; (https://github.com/Azure/azure-cosmosdb-python/blob/master/requirements.txt)
My environment:
The graph output: https://pastebin.com/wAqZZ9Ez |
You can add this to your lock file before
|
I am still seeing this issue with pipenv, version 2018.05.18 |
Grow does not install with the default python downloaded today (3.6.5) due to this same error. |
I feel like this particular issue is probably addressed and I just can't tell, but I have an odd futures issue that seems to be related to the pipenv lock file (but only seems to be an issue on a redhat system, not my mac where I have things using homebrew): In the above gist, I have tried to have a simple layout with commands and outputs and errors grouped reasonably logically. For all of my environment/software information, see the gist. The summary of the issue I'm seeing is:
Anyways, I'm not entirely sure where the source of this error is, and I don't have the time to dig in much more today. I am able to work around the issue by specifying versions that I know will work in Pipfile:
but I thought it might be reasonable to mention this issue here, for someone to follow up at some point. Thanks for any help anyone can provide! I will update here if I find any relevant info, including issues that are still open. |
can get around this for now with |
I wanted to maintain the Pipe.lock file which is used in my docker orchestration because of this issue, It fails entire application to be stable.
|
I resolved the issue by upgrading the
|
Still a problem on OS X. What the heck? |
getting this error on OS X as well, on a Python 3.6.6 virtual environment with
|
I'm having the same problem with zappa as well. After digging through pipenv 2018.7.1 I found that the issue is in how markers are handled. The and condition in the case where 2 'python_version' conditions were defined wasn't being properly handled. This is already resolved in the current master branch (just not released yet). You can use this command to install I've confirmed here that zappa 0.46.2 installs properly with this version. |
Just want to echo this solution. We found Pipenv to be inserting futures as a top level dependency even though nothing required it in the Pipfile. This in turn causing breakage for our Python3 applications since futures is not Python3 compatible causing the app not to boot. Removing Pipenv and clearing cache solved the issue. |
I was facing the same issue and getting a bunch of errors related to futures and markers. Not sure how exactly, but I did below steps and was able to successfully create the virtualenv via pipenv: pipenv --rm
pipenv lock --clear
pipenv shell
pipenv install This link helped me arrive at the |
The text was updated successfully, but these errors were encountered: