feat: Conflicting requirements after copier installation, is it possible to bump up them?
See original GitHub issueCopier v6 installed from git repo master.
After installation i get the following:
# pip check
twine 3.7.1 has requirement pkginfo>=1.8.1, but you have pkginfo 1.7.1.
redis 4.1.0 has requirement packaging>=21.3, but you have packaging 20.9.
nltk 3.6.7 has requirement regex>=2021.8.3, but you have regex 2020.11.13.
flask 2.0.2 has requirement Jinja2>=3.0, but you have jinja2 2.11.3.
black 21.12b0 has requirement pathspec<1,>=0.9.0, but you have pathspec 0.8.1.
Could you please bump up requirements? Thanks
Issue Analytics
- State:
- Created 2 years ago
- Comments:8 (5 by maintainers)
Top Results From Across the Web
Top 6 Fixes for MSI Mystic Light Not Working Error [New Update]
Under this circumstance, removing the conflicting programs is recommended. What are conflicting applications?
Read more >git-checkout Documentation - Git
If the branch exists in multiple remotes and one of them is named by the checkout.defaultRemote configuration variable, we'll use that one for...
Read more >School Conflict Management: Evaluating Your Conflict ...
Those stages are detailed in the following table: Stage. Description. Assess Needs. Identify the goals and resources for your school. Assess the.
Read more >Performing a standard RHEL 9 installation Red Hat Enterprise ...
An installation source is required for the Boot ISO image file only if you decide not to register and install RHEL from the...
Read more >8 Things You Should Know About HP® Instant Ink® Before ...
This article serves to inform HP printer users on what the HP Instant Ink program is and the disclaimers you should know about...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
I think this makes sense.
We could also provide Copier as a nix flake, making it 100% reproducible under any environment.
Finally, I think the original problem is not being properly understood. For example, in your error log you have:
However, we also require a newer Jinja:
https://github.com/copier-org/copier/blob/af0dbac4ab2b0d2be35e6c7a1171e258697ddec0/pyproject.toml#L35
So the problem does not seem to be in Copier’s dependencies, but in the ones installed in your venv. You’ll need to fix those downstream.
I’ll close this issue, where there seems to be no action to take in our side, and open the other two.
Thanks everyone, feel free to keep commenting here if needed. 😊
Surely you didn’t offend me 😊, on the contrary i found you very kind in your attempts to give indications according to your experience. 😉