question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Error in Setting up the Wagtail codebase

See original GitHub issue

Issue Summary

While setting up a local copy of the Wagtail git repository, running the command $ pip install -e .[testing,docs] -U generates the following error: -

ERROR: Cannot install myst_parser and wagtail because these package versions have conflicting dependencies.

The conflict is caused by:
    jinjalint 0.5 depends on attrs==17.2.0
    markdown-it-py 2.0.1 depends on attrs<22 and >=19
    jinjalint 0.5 depends on attrs==17.2.0
    markdown-it-py 2.0.0 depends on attrs<22 and >=19
    jinjalint 0.5 depends on attrs==17.2.0
    markdown-it-py 1.1.0 depends on attrs<22 and >=19
    jinjalint 0.5 depends on attrs==17.2.0
    markdown-it-py 1.0.0 depends on attrs<21 and >=19

To fix this you could try to:
1. loosen the range of package versions you've specified
2. remove package versions to allow pip attempt to solve the dependency conflict

Steps to Reproduce

  1. Clone a copy of the Wagtail codebase using the following commands: -
$ git clone https://github.com/wagtail/wagtail.git
$ cd wagtail
  1. With your preferred virtualenv activated, install the Wagtail package in development mode with the included testing and documentation dependencies: $ pip install -e .[testing,docs] -U

  2. The error will pop up.

There is something wrong with documentation dependencies.
$ pip install -e .[testing] -U works absolutely fine.

  • I have confirmed that this issue can be reproduced as described on a fresh Wagtail project: Yes

Technical details

  • Python version: 3.10
  • Django version: 4.0.3
  • Wagtail version: 2.17a0
  • Operating System: Windows/ Mac

Issue Analytics

  • State:closed
  • Created 2 years ago
  • Comments:6 (5 by maintainers)

github_iconTop GitHub Comments

2reactions
thibaudcolascommented, Mar 10, 2022

#8101 ready for review! Thank you for reporting this so quickly and thoroughly @gitkaarma, makes it much much easier to figure out what the issue is.

0reactions
thibaudcolascommented, Mar 11, 2022

@gitkaarma should be all resolved, sorry about that! Please let us know if you encounter further issues like this.

Read more comments on GitHub >

github_iconTop Results From Across the Web

How to fix error upgrading Wagtail 2.10.2 to 2.11.8?
Uninstall the Wagtail package with pip uninstall wagtail , then reinstall the same version that you had - this should remove the autogenerated ......
Read more >
Several errors during installation · Issue #240 - GitHub
Several errors during installation #240 ... Running setup.py (path:/Users/PDXIII/Envs/wagtail/build/django-compressor/setup.py) egg_info for ...
Read more >
Contributing to Wagtail — Wagtail 1.13.4 documentation
First, check to see if your bug or feature request has already been submitted at github.com/wagtail/wagtail/issues. If it has, and you have some...
Read more >
Coders of Colour - Introduction to Wagtail
When a 500 (internal server error) occurs, it's important to look through the ... Open up mysite/settings/production.py and change it to look like...
Read more >
Wagtail CMS - Pegasus documentation
If you want to try Wagtail make sure you enable the “Use Wagtail” option in the Pegasus codebase creator. After you set up...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found