pynio causes dependency conflicts in py36 CI build
See original GitHub issueOn Saturday night, all Python 3.6 CI builds started failing. Python 3.7 is unaffected. See https://dev.azure.com/xarray/xarray/_build/results?buildId=362&view=logs
MacOSX py36:
UnsatisfiableError: The following specifications were found to be in conflict:
- pynio
- python=3.6
- rasterio
Linux py36:
UnsatisfiableError: The following specifications were found to be in conflict:
- cfgrib[version='>=0.9.2']
- h5netcdf
- pynio
Issue Analytics
- State:
- Created 4 years ago
- Reactions:1
- Comments:9 (7 by maintainers)
Top Results From Across the Web
How to identify and resolve a dependency conflict
Find Divio's how-to guide to identifying and resolving a dependency conflict. Learn what steps to take if a deployment in the cloud or...
Read more >The Nine Circles of Python Dependency Hell - Medium
It recursively checks the requirements of each library and prints out any conflicts. It can be used to fail your build when a...
Read more >Debugging Composer Dependency Conflicts - Mediacurrent
That issue is caused because of more strict package versions in composer.json -- especially with the nikic/php-parser package.
Read more >Solving Dependency Conflicts in Maven - DZone
Maven dependency conflicts can be really hard to solve. The purpose of this post is for readers to better understand what a version...
Read more >npm ci giving Conflicting peer dependency - Stack Overflow
I also started to get this error on pipe. What is interesting I always have had peer dependency conflict but it was only...
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
OK, this is fixed for now by removing
pynio
from the CI builds.Closed by #3340