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.
As a library, this should not pin to a specific version of botocore or boto3
See original GitHub issueAs a library, aiobotocre should not require a specific version of any of these in the setup.py:
botocoreboto3awscli
If this were an application, it would be different. But in order to use this library with a wide variety of other libraries, you want to use >= not a combination of >= and < which is effectively an ==.
I have had to regretfully remove this and things that depend on it from a JupyterHub/JupyterLab system I maintain because it wouldn’t allow me to upgrade to the latest version of botocore and boto3 and hence prevented other tools from working properly.
Issue Analytics
- State:
- Created a year ago
- Reactions:4
- Comments:7
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
Yeah especially with the new pip resolver that fails on conflicts the current setup makes it very difficult to include
aiobotocorein anythingI’m not even sure how that would work, because when in botocore it does an import it will need to import from the vendored copy as well, which I think means we have to re-write all the import statements