-
-
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
Unexpected Dependancy Graph Issue #2529
Comments
Hey @JBKahn Any update on this? |
I had been slammed at work, it seems to be possibly related to my build environment as this didn't happen on my machine but inside an alpine python docker container. Was going to dig in before I included all the details. |
I think I'm experiencing the same issue with a different package:
and it's true, After running the suggested
I'm just investigating how much work it is to switch over to using
So, maybe this comes down to, how do I find out where that bogus version spec comes from? |
yeah, the real difficulty is that when there is a collision, the output isn't showing where the different requirements come from. I've been super busy these past few days but I'll try to get to this ASAP. |
Literally dealing with this right now, it's impossible to track down which package is causing issues |
$ pipenv --supportPipenv version: Pipenv location: Python location: Other Python installations in
PEP 508 Information:
System environment variables:
Pipenv–specific environment variables: Debug–specific environment variables:
Contents of [[source]]
url = "https://pypi.org/simple"
verify_ssl = true
name = "pypi"
[packages]
lxml = "*"
nose = "*"
django-extensions = "*"
django-tinymce = "*"
sorl-thumbnail = "*"
"suds-py3" = "*"
feedparser = "*"
python-dateutil = "*"
python-memcached = "*"
django-pipeline = "*"
requests = "*"
django-pipeline-forgiving = "*"
django-ckeditor = "*"
django-filebrowser = "*"
raven = "*"
celery = {version = "*", extras = ["redis"]}
"psycopg2-binary" = "*"
django-crispy-forms = "*"
pyotp = "*"
newrelic = "*"
djangorestframework = "*"
djangorestframework-xml = "*"
djangorestframework-jwt = "*"
django-filter = "*"
parsedatetime = "*"
simple-salesforce = "*"
django-allauth = "*"
apache-libcloud = "*"
django-storages = "*"
"boto3" = "*"
sortedcontainers = "*"
redis = "*"
hiredis = "*"
msgpack-python = "*"
django-waffle = "*"
django-report-builder = "*"
django-markupfield = "*"
django-cors-headers = "*"
arrow = "*"
django-redis = "*"
"mailchimp3" = "*"
dotmailer = {editable = true, git = "https://github.com/savingschampion/dotmailer.git"}
simplejson = "*"
zeep = "*"
djangorestframework-jsonp = "*"
requests-oauthlib = "*"
django-ipware = "*"
hypothesis = {version = "*", extras = ["pytz"]}
drf-yasg = {version = "*", extras = ["validation"]}
Django = ">=2.0"
Pillow = "*"
uWSGI = "*"
"Django-Select2" = "*"
Collectfast = "*"
Markdown = "*"
Faker = "*"
rest_condition = "*"
django-rest-knox = "*"
django-simple-history = "*"
wagtail = "*"
wagtail-metadata-mixin = "*"
[dev-packages]
[requires]
python_version = "3.6"
I have no idea where the ==2.1 comes from, listing of all requirements from graph with Django in the name
|
It’s from Wagtail, you need to pin And yes, I know the resolver should be able to pin this automatically, but right now it’s what it is. |
Is it easy to write tests for the resolver. I haven't taken a look at the code but I'd help out if it isn't too bad to get started. |
I'm running into the same issue with
Running
|
@OliverHofkens see #2596. Running |
@mjdunn Great, thanks! |
still seeing this, but with a different package now:
but according to
|
With which version of pipenv |
sorry, missed that! in 2018.10.9. I think that's the latest, right? |
Issue description
I had a requirement pinned to "<4.0.0" and a sub-dependancy that required it to be "==3.3.0". I checked the graph and as expected, that was the only dependancy that required the protobuf package.
That gave me a dependancy resolution error of:
Could not find a version that matches protobuf<4.0.0,==3.3.0,==3.6.0
Expected result
I expected it to resolve to "==3.3.0"
Actual result
I was able to get it to be happy by changing my local "<4.0.0" to "==3.3.0".
Steps to replicate
I will fill this is later today, but wanted to spell out the issue just in case it is known.
Provide the steps to replicate (which usually at least includes the commands and the Pipfile).
Please run
$ pipenv --support
, and paste the results here. Don't put backticks (`
) around it! The output already contains Markdown formatting.If you're on macOS, run the following:
If you're on Windows, run the following:
The text was updated successfully, but these errors were encountered: