Skip to content
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

Can't install Django-shop on Mac OS #845

Open
ay0000 opened this issue Feb 8, 2021 · 9 comments
Open

Can't install Django-shop on Mac OS #845

ay0000 opened this issue Feb 8, 2021 · 9 comments

Comments

@ay0000
Copy link

ay0000 commented Feb 8, 2021

Hello all,

I'm having an issue installing a fresh copy of Django-shop in a new pipenv environment in Pycharm. I'm following the instructions on the Django-shop website and the issue occurs at the
pipenv install --sequential step (see terminal output below)

I've done this a few times over the last few weeks but this is the first time I've encountered this issue. I'm using Django 3.1.6 and Python 3.8.2.

Courtesy Notice: Pipenv found itself running within a virtual environment, so it will automatically use that environment, instead of creating its own for any project. You can set PIPENV_IGNORE_VIRTUALENVS=1 to force pipenv to ignore that environment and create its own instead. You can set PIPENV_VERBOSITY=-1 to suppress this warning. Pipfile.lock not found, creating... Locking [dev-packages] dependencies... Building requirements... ✔ Success! Locking [packages] dependencies... ✘ Locking Failed! [ResolutionFailure]: File "/Users/aarronyounan/Library/Python/3.8/lib/python/site-packages/pipenv/resolver.py", line 741, in _main [ResolutionFailure]: resolve_packages(pre, clear, verbose, system, write, requirements_dir, packages, dev) [ResolutionFailure]: File "/Users/aarronyounan/Library/Python/3.8/lib/python/site-packages/pipenv/resolver.py", line 702, in resolve_packages [ResolutionFailure]: results, resolver = resolve( [ResolutionFailure]: File "/Users/aarronyounan/Library/Python/3.8/lib/python/site-packages/pipenv/resolver.py", line 684, in resolve [ResolutionFailure]: return resolve_deps( [ResolutionFailure]: File "/Users/aarronyounan/Library/Python/3.8/lib/python/site-packages/pipenv/utils.py", line 1395, in resolve_deps [ResolutionFailure]: results, hashes, markers_lookup, resolver, skipped = actually_resolve_deps( [ResolutionFailure]: File "/Users/aarronyounan/Library/Python/3.8/lib/python/site-packages/pipenv/utils.py", line 1108, in actually_resolve_deps [ResolutionFailure]: resolver.resolve() [ResolutionFailure]: File "/Users/aarronyounan/Library/Python/3.8/lib/python/site-packages/pipenv/utils.py", line 833, in resolve [ResolutionFailure]: raise ResolutionFailure(message=str(e)) [pipenv.exceptions.ResolutionFailure]: Warning: Your dependencies could not be resolved. You likely have a mismatch in your sub-dependencies. First try clearing your dependency cache with $ pipenv lock --clear, then try the original command again. Alternatively, you can use $ pipenv install --skip-lock to bypass this mechanism, then run $ pipenv graph to inspect the situation. Hint: try $ pipenv lock --pre if it is a pre-release dependency. ERROR: Could not find a version that matches django<3.1,<3.2,<4.0,>=1.6,>=1.8,>=1.8.0,>=2.0,>=2.1,>=2.2,>=3,>=3.1 (from -r /var/folders/29/40q6jzf10mn1jnz1lx3f6x9h0000gn/T/pipenvk0dkq9jyrequirements/pipenv-ifoj0nh4-constraints.txt (line 33)) Tried: 1.1.3, 1.1.4, 1.2, 1.2.1, 1.2.2, 1.2.3, 1.2.4, 1.2.5, 1.2.6, 1.2.7, 1.3, 1.3.1, 1.3.2, 1.3.3, 1.3.4, 1.3.5, 1.3.6, 1.3.7, 1.4, 1.4.1, 1.4.2, 1.4.3, 1.4.4, 1.4.5, 1.4.6, 1.4.7, 1.4.8, 1.4.9, 1.4.10, 1.4.11, 1.4.12, 1.4.13, 1.4.14, 1.4.15, 1.4.16, 1.4.17, 1.4.18, 1.4.19, 1.4.20, 1.4.21, 1.4.22, 1.5, 1.5.1, 1.5.2, 1.5.2, 1.5.3, 1.5.4, 1.5.5, 1.5.6, 1.5.7, 1.5.8, 1.5.8, 1.5.9, 1.5.10, 1.5.11, 1.5.12, 1.5.12, 1.6, 1.6, 1.6.1, 1.6.1, 1.6.2, 1.6.2, 1.6.3, 1.6.3, 1.6.4, 1.6.4, 1.6.5, 1.6.5, 1.6.6, 1.6.6, 1.6.7, 1.6.7, 1.6.8, 1.6.8, 1.6.9, 1.6.9, 1.6.10, 1.6.10, 1.6.11, 1.6.11, 1.7, 1.7, 1.7.1, 1.7.1, 1.7.2, 1.7.2, 1.7.3, 1.7.3, 1.7.4, 1.7.4, 1.7.5, 1.7.5, 1.7.6, 1.7.6, 1.7.7, 1.7.7, 1.7.8, 1.7.8, 1.7.9, 1.7.9, 1.7.10, 1.7.10, 1.7.11, 1.7.11, 1.8, 1.8, 1.8.1, 1.8.1, 1.8.2, 1.8.2, 1.8.3, 1.8.3, 1.8.4, 1.8.4, 1.8.5, 1.8.5, 1.8.6, 1.8.6, 1.8.7, 1.8.7, 1.8.8, 1.8.8, 1.8.9, 1.8.9, 1.8.10, 1.8.10, 1.8.11, 1.8.11, 1.8.12, 1.8.12, 1.8.13, 1.8.13, 1.8.14, 1.8.14, 1.8.15, 1.8.15, 1.8.16, 1.8.16, 1.8.17, 1.8.17, 1.8.18, 1.8.18, 1.8.19, 1.8.19, 1.9, 1.9, 1.9.1, 1.9.1, 1.9.2, 1.9.2, 1.9.3, 1.9.3, 1.9.4, 1.9.4, 1.9.5, 1.9.5, 1.9.6, 1.9.6, 1.9.7, 1.9.7, 1.9.8, 1.9.8, 1.9.9, 1.9.9, 1.9.10, 1.9.10, 1.9.11, 1.9.11, 1.9.12, 1.9.12, 1.9.13, 1.9.13, 1.10, 1.10, 1.10.1, 1.10.1, 1.10.2, 1.10.2, 1.10.3, 1.10.3, 1.10.4, 1.10.4, 1.10.5, 1.10.5, 1.10.6, 1.10.6, 1.10.7, 1.10.7, 1.10.8, 1.10.8, 1.11, 1.11, 1.11.1, 1.11.1, 1.11.2, 1.11.2, 1.11.3, 1.11.3, 1.11.4, 1.11.4, 1.11.5, 1.11.5, 1.11.6, 1.11.6, 1.11.7, 1.11.7, 1.11.8, 1.11.8, 1.11.9, 1.11.9, 1.11.10, 1.11.10, 1.11.11, 1.11.11, 1.11.12, 1.11.12, 1.11.13, 1.11.13, 1.11.14, 1.11.14, 1.11.15, 1.11.15, 1.11.16, 1.11.16, 1.11.17, 1.11.17, 1.11.18, 1.11.18, 1.11.20, 1.11.20, 1.11.21, 1.11.21, 1.11.22, 1.11.22, 1.11.23, 1.11.23, 1.11.24, 1.11.24, 1.11.25, 1.11.25, 1.11.26, 1.11.26, 1.11.27, 1.11.27, 1.11.28, 1.11.28, 1.11.29, 1.11.29, 2.0, 2.0, 2.0.1, 2.0.1, 2.0.2, 2.0.2, 2.0.3, 2.0.3, 2.0.4, 2.0.4, 2.0.5, 2.0.5, 2.0.6, 2.0.6, 2.0.7, 2.0.7, 2.0.8, 2.0.8, 2.0.9, 2.0.9, 2.0.10, 2.0.10, 2.0.12, 2.0.12, 2.0.13, 2.0.13, 2.1, 2.1, 2.1.1, 2.1.1, 2.1.2, 2.1.2, 2.1.3, 2.1.3, 2.1.4, 2.1.4, 2.1.5, 2.1.5, 2.1.7, 2.1.7, 2.1.8, 2.1.8, 2.1.9, 2.1.9, 2.1.10, 2.1.10, 2.1.11, 2.1.11, 2.1.12, 2.1.12, 2.1.13, 2.1.13, 2.1.14, 2.1.14, 2.1.15, 2.1.15, 2.2, 2.2, 2.2.1, 2.2.1, 2.2.2, 2.2.2, 2.2.3, 2.2.3, 2.2.4, 2.2.4, 2.2.5, 2.2.5, 2.2.6, 2.2.6, 2.2.7, 2.2.7, 2.2.8, 2.2.8, 2.2.9, 2.2.9, 2.2.10, 2.2.10, 2.2.11, 2.2.11, 2.2.12, 2.2.12, 2.2.13, 2.2.13, 2.2.14, 2.2.14, 2.2.15, 2.2.15, 2.2.16, 2.2.16, 2.2.17, 2.2.17, 2.2.18, 2.2.18, 3.0, 3.0, 3.0.1, 3.0.1, 3.0.2, 3.0.2, 3.0.3, 3.0.3, 3.0.4, 3.0.4, 3.0.5, 3.0.5, 3.0.6, 3.0.6, 3.0.7, 3.0.7, 3.0.8, 3.0.8, 3.0.9, 3.0.9, 3.0.10, 3.0.10, 3.0.11, 3.0.11, 3.0.12, 3.0.12, 3.1, 3.1, 3.1.1, 3.1.1, 3.1.2, 3.1.2, 3.1.3, 3.1.3, 3.1.4, 3.1.4, 3.1.5, 3.1.5, 3.1.6, 3.1.6 Skipped pre-versions: 1.8a1, 1.8b1, 1.8b2, 1.8rc1, 1.9a1, 1.9b1, 1.9rc1, 1.9rc2, 1.10a1, 1.10a1, 1.10b1, 1.10b1, 1.10rc1, 1.10rc1, 1.11a1, 1.11b1, 1.11rc1, 1.11rc1, 2.0a1, 2.0b1, 2.0rc1, 2.1a1, 2.1b1, 2.1rc1, 2.2a1, 2.2a1, 2.2b1, 2.2b1, 2.2rc1, 2.2rc1, 3.0a1, 3.0a1, 3.0b1, 3.0b1, 3.0rc1, 3.0rc1, 3.1a1, 3.1a1, 3.1b1, 3.1b1, 3.1rc1, 3.1rc1, 3.2a1, 3.2a1 There are incompatible versions in the resolved dependencies: django>=3 (from -r /var/folders/29/40q6jzf10mn1jnz1lx3f6x9h0000gn/T/pipenvk0dkq9jyrequirements/pipenv-ifoj0nh4-constraints.txt (line 33)) django<3.1,>=2.1 (from django-shop==1.2.4->-r /var/folders/29/40q6jzf10mn1jnz1lx3f6x9h0000gn/T/pipenvk0dkq9jyrequirements/pipenv-ifoj0nh4-constraints.txt (line 30)) django<3.2,>=1.8 (from django-admin-sortable2==0.7.8->-r /var/folders/29/40q6jzf10mn1jnz1lx3f6x9h0000gn/T/pipenvk0dkq9jyrequirements/pipenv-ifoj0nh4-constraints.txt (line 20)) django<4.0,>=2.2 (from django-filer==2.0.2->-r /var/folders/29/40q6jzf10mn1jnz1lx3f6x9h0000gn/T/pipenvk0dkq9jyrequirements/pipenv-ifoj0nh4-constraints.txt (line 4)) django>=1.6 (from django-fsm-admin==1.2.4->-r /var/folders/29/40q6jzf10mn1jnz1lx3f6x9h0000gn/T/pipenvk0dkq9jyrequirements/pipenv-ifoj0nh4-constraints.txt (line 2)) django>=1.8.0 (from django-rest-auth==0.9.5->-r /var/folders/29/40q6jzf10mn1jnz1lx3f6x9h0000gn/T/pipenvk0dkq9jyrequirements/pipenv-ifoj0nh4-constraints.txt (line 11)) django>=2.0 (from django-allauth==0.44.0->-r /var/folders/29/40q6jzf10mn1jnz1lx3f6x9h0000gn/T/pipenvk0dkq9jyrequirements/pipenv-ifoj0nh4-constraints.txt (line 14)) django>=2.1 (from django-angular==2.3->-r /var/folders/29/40q6jzf10mn1jnz1lx3f6x9h0000gn/T/pipenvk0dkq9jyrequirements/pipenv-ifoj0nh4-constraints.txt (line 8)) django>=2.1 (from django-polymorphic==3.0.0->-r /var/folders/29/40q6jzf10mn1jnz1lx3f6x9h0000gn/T/pipenvk0dkq9jyrequirements/pipenv-ifoj0nh4-constraints.txt (line 12)) django>=2.2 (from django-cms==3.8.0->-r /var/folders/29/40q6jzf10mn1jnz1lx3f6x9h0000gn/T/pipenvk0dkq9jyrequirements/pipenv-ifoj0nh4-constraints.txt (line 26)) django>=2.2 (from django-filter==2.4.0->-r /var/folders/29/40q6jzf10mn1jnz1lx3f6x9h0000gn/T/pipenvk0dkq9jyrequirements/pipenv-ifoj0nh4-constraints.txt (line 16)) django>=2.2 (from django-phonenumber-field==5.0.0->-r /var/folders/29/40q6jzf10mn1jnz1lx3f6x9h0000gn/T/pipenvk0dkq9jyrequirements/pipenv-ifoj0nh4-constraints.txt (line 13)) django>=2.2 (from django-post-office==3.5.3->-r /var/folders/29/40q6jzf10mn1jnz1lx3f6x9h0000gn/T/pipenvk0dkq9jyrequirements/pipenv-ifoj0nh4-constraints.txt (line 27)) django>=2.2 (from django-select2==7.6.1->-r /var/folders/29/40q6jzf10mn1jnz1lx3f6x9h0000gn/T/pipenvk0dkq9jyrequirements/pipenv-ifoj0nh4-constraints.txt (line 28)) django>=2.2 (from djangorestframework==3.12.2->-r /var/folders/29/40q6jzf10mn1jnz1lx3f6x9h0000gn/T/pipenvk0dkq9jyrequirements/pipenv-ifoj0nh4-constraints.txt (line 15)) django>=3.1 (from djangocms-cascade==2.0->-r /var/folders/29/40q6jzf10mn1jnz1lx3f6x9h0000gn/T/pipenvk0dkq9jyrequirements/pipenv-ifoj0nh4-constraints.txt (line 10))

@VManuelSM
Copy link

Same trouble!!!! Help!!!

@SudoStain
Copy link

download the code and run it the traditional way.

@bozorgmehr96
Copy link

bozorgmehr96 commented Aug 7, 2021

The problem caused by conflict between djangocms-cascade requiring django >=3.1 and django-shop requiring django <3.1

@alexakarpov
Copy link

@bozorgmehr96 thanks for the observation as to what's causing the problem; any suggestions as to how to work around it? I never used this coockie-cutter thing before - it sounds like this dependencies inconsistency comes from there. Would you say that editing the dependency in generated Pipfile is a good approach?

@alexakarpov
Copy link

interesting; reading around the issue reported by @ay0000 , I found one suggested workaround; the following indeed works:
$ pipenv install --sequential --skip-lock

, but check reports two errors (same root cause, apparently):

ERRORS:
<class 'filer.admin.folderadmin.FolderAdmin'>: (admin.E039) An admin for model "User" has to be registered to be referenced by FolderAdmin.autocomplete_fields.
<class 'filer.admin.permissionadmin.PermissionAdmin'>: (admin.E039) An admin for model "User" has to be registered to be referenced by PermissionAdmin.autocomplete_fields.

System check identified 2 issues (1 silenced).

@dorrayahyaoui
Copy link

interesting; reading around the issue reported by @ay0000 , I found one suggested workaround; the following indeed works: $ pipenv install --sequential --skip-lock

, but check reports two errors (same root cause, apparently):

ERRORS:
<class 'filer.admin.folderadmin.FolderAdmin'>: (admin.E039) An admin for model "User" has to be registered to be referenced by FolderAdmin.autocomplete_fields.
<class 'filer.admin.permissionadmin.PermissionAdmin'>: (admin.E039) An admin for model "User" has to be registered to be referenced by PermissionAdmin.autocomplete_fields.

System check identified 2 issues (1 silenced).

interesting; reading around the issue reported by @ay0000 , I found one suggested workaround; the following indeed works: $ pipenv install --sequential --skip-lock

, but check reports two errors (same root cause, apparently):

ERRORS:
<class 'filer.admin.folderadmin.FolderAdmin'>: (admin.E039) An admin for model "User" has to be registered to be referenced by FolderAdmin.autocomplete_fields.
<class 'filer.admin.permissionadmin.PermissionAdmin'>: (admin.E039) An admin for model "User" has to be registered to be referenced by PermissionAdmin.autocomplete_fields.

System check identified 2 issues (1 silenced).

im struggling with the same error .. any help

@chandave
Copy link

It looks like an issue with versions of django-filer newer than 2.0.2. I was able to bypass the filer.admin.folderadmin.FolderAdmin class issue by declaring django-filer==2.0.2 in cookiecutter-django-shop/{{cookiecutter.project_slug}}/Pipfile.

I also enabled django-compressor, i.e. answered "y" to "use_compressor" question when executing "cookiecutter ...".

For those of you that don't want to fork and modify the Pipfile yourself, you can use my fork. Just execute:

cookiecutter https://github.com/chandave/cookiecutter-django-shop

and answer "y" for the "use compressor" question.

@artforlife
Copy link

artforlife commented Jun 13, 2022

It looks like an issue with versions of django-filer newer than 2.0.2. I was able to bypass the filer.admin.folderadmin.FolderAdmin class issue by declaring django-filer==2.0.2 in cookiecutter-django-shop/{{cookiecutter.project_slug}}/Pipfile.

I also enabled django-compressor, i.e. answered "y" to "use_compressor" question when executing "cookiecutter ...".

For those of you that don't want to fork and modify the Pipfile yourself, you can use my fork. Just execute:

cookiecutter https://github.com/chandave/cookiecutter-django-shop

and answer "y" for the "use compressor" question.

Just wanted to report that your suggestions do not work when applied to the current version of this repository. I have been getting the same error. However, they do work, when applied to your fork.

@chandave
Copy link

It looks like an issue with versions of django-filer newer than 2.0.2. I was able to bypass the filer.admin.folderadmin.FolderAdmin class issue by declaring django-filer==2.0.2 in cookiecutter-django-shop/{{cookiecutter.project_slug}}/Pipfile.
I also enabled django-compressor, i.e. answered "y" to "use_compressor" question when executing "cookiecutter ...".
For those of you that don't want to fork and modify the Pipfile yourself, you can use my fork. Just execute:
cookiecutter https://github.com/chandave/cookiecutter-django-shop
and answer "y" for the "use compressor" question.

Just wanted to report that your suggestions do not work when applied to the current version of this repository. I have been getting the same error. However, they do work, when applied to your fork.

"... current version of this repository ..." as in cookiecutter-django-shop or do you mean django-shop?

My fork of cookiecutter-django-shop assumes django-shop v1.2.4.

If you are not using cookiecutter-django-shop then you can achieve the same django-filer limitation by editing django-shop's setup.py:

  • Change 'django-filer>=1.7' to 'django-filer==2.0.2'

You might also need to add:

'django-treebeard==4.4'

Into the REQUIREMENTS list.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

8 participants