graphql-core | A Python 36+ port of the GraphQLjs reference implementation of GraphQL | GraphQL library

The problem seems to be that graphene-django only has version 2.15.0 according to PyPI https://pypi.org/project/graphene-django/. But for some reason in this commit of the library django-graphql-jwt it asks for a version 3.0.0b1. Which I think is the issue that shows in your log:

I'd venture the issue is that recreating from a YAML that includes versions and builds will establish those versions and builds as explicit specifications for that environment moving forward. That is, Conda will regard explicit specifications as hard requirements that it cannot mutate and so if even a single one of the dependencies of cudatoolkit also needs to be updated in order to use version 11, Conda will not know how to satisfy it without violating those previously specified constraints.

Specifically, this is what I see when searching (assuming linux-64 platform):

This is an issue with graphql version. For example on version 0.5.3 I got the same issue as you.

It was finally a bug, reported to the library owners and they've fixed it here.

N.B. It's going to be a little difficult to answer this without seeing how your settings.py is configured, but double-check that you went through every step. I went through the quickstart too but still missed a few spots.

I ran into a similar "Connection refused" error, but the issue was that my settings were not configured properly.

Edit: After further local development and toggling with individual settings, I realized that my "Connection refused error was related to not having EMAIL_BACKEND configured. It was trying to connect to any SMTP server that wasn't running. Make sure you have EMAIL_BACKEND = "django.core.mail.backends.console.EmailBackend" set to log this functionality to your console.

Here's a slightly abbreviated copy of my settings.py from a scratch project I was using, just to be sure that you have it configured correctly:

Source: django-graphql-auth quickstart.

N.B.: It's a little long, make sure to scroll all the way through

Seems the issue came from graphql-core version which need to be >=3.

I was unabled to install the version >=3 so I upgraded Python to 3.8. When installing Ariadne, I get the same version 0.11.0 but now the graphql-core version 3.0.5 and no more the error.

This doesn't sound good: "When i installed python and anaconda i set both the installers to ADD TO PATH."

1. Anaconda is a Python distribution. You need this one installer only.
2. Don't add Anaconda's python.exe to the PATH. This is not how environments work.
3. If you want to work with Anaconda, you need to activate at least the base environment using the 'conda' environment manager. This is how Python can find e.g. numpy's C-libraries.
4. You can install Python from python.org in parallel to Anaconda, but this is asking for trouble.

I believe johnnydep can help with that:

I have no skills in Django, but it seems that tensorflow is trying to find a package (with a strange name) and failing.

I'd first suggest to try and fix your docker container setup, and check that pipenv lock -r yield the same result inside and outside your container.

1) as you said in the commentaries, on the host pc