search

Formulka / django-fperms-iscore

iscore extension for django-perms
MIT License
0 stars 2 forks source link

Conflicts between django-fperms-iscore and python-mimeparse #3

Open NeolithEra opened 4 years ago

NeolithEra commented 4 years ago

Hi, users are unable to run django-fperms-iscore due to dependency conflict with python-mimeparse package. As shown in the following full dependency graph of django-fperms-iscore, django-is-core requires python-mimeparse ==0.1.4，while django-pyston requires python-mimeparse >=1.6.0.

According to pip’s “first found wins” installation strategy, python-mimeparse 0.1.4 is the actually installed version. However, python-mimeparse 0.1.4 does not satisfy >=1.6.0.

Dependency tree-----------

django-fperms-iscore - 0.2.8 
| +- django-fperms(install version:0.4.5 version range:==0.4.5)
| | +- django(install version:3.0 version range:>=1.11)
| +- django-is-core(install version:2.18.0 version range:==2.18.0)
| | +- django(install version:3.0 version range:>=1.10)
| | +- django-block-snippets(install version:2.0.1 version range:==2.0.1)
| | | +- django(install version:3.0 version range:>=1.10)
| | +- django-chamber(install version:0.5.16 version range:<0.6,>=0.5.2)
| | +- django-ipware(install version:2.1.0 version range:<11,>=1.0.0)
| | +- django-pyston(install version:2.9.22 version range:<2.10,>=2.9.16)
| | | +- django(install version:3.0 version range:>=1.11)
| | | +- django-chamber(install version:0.5.16 version range:>=0.5.6)
| | | +- pyparsing(install version:2.4.5 version range:>=2.4.2)
| | | +- python-mimeparse(install version:1.6.0 version range:>=1.6.0)
| | +- python-dateutil(install version:2.8.1 version range:<3,>=2.2)
| | +- python-mimeparse(install version:0.1.4 version range:==0.1.4)
| | +- pytz(install version:2019.3 version range:*)
| | +- unidecode(install version:1.1.1 version range:>=0.04.16)

Thanks for your help. Best, Neolith

NeolithEra commented 4 years ago

Suggested Solution

  1. Fix your direct dependency to be django-is-core >2.18.0. I have checked this revision will not affect your downstream projects now.
  2. Fix your direct dependency to be django-is-core ==2.19.0. I have checked this revision will not affect your downstream projects now.

@Formulka Which solution do you prefer, 1, 2? Please let me know your choice. I can submit a PR to solve this issue.