Installation fails due to conflicting botocore version #500
Comments
Solution
|
|
I'm also having this issue. |
|
Is anyone working on this? I believe I can't use Secrets Manager due to this and can't find a way to install the correct versions myself. Would rather not fork. |
|
Or has anyone found a workaround? |
|
BTW, I cloned this and did 1 & 2 from @NeolithEra 's post and worked without issue. |
|
Well, I attempted to push a branch for a pull request but I don't have permission (of course). This is really frustrating. I understand this is open-source so I'm not bitching. It would just be nice to get this fixed with such a simple change. There are also a bunch of PRs from Dependabot awaiting review so not sure how active the maintainer will be. |
|
Okay, well, 5 days with no response. That's worrisome to say the least. Guess I'll have to start looking for a new tool or build my own. |
|
@zacharyabresch Sorry for my late reply. Generally, it is an automated tool (implemented as a bot on GitHub https://github.com/apps/watchman-pypi ). But there are administrators looking at your comments. : p |
|
Plus one on this issue |
Hi, users are unable to run Dmn-python-lambda due to dependency conflict with botocore package. As shown in the following full dependency graph of Dmn-python-lambda, Dmn-python-lambda requires botocore>=1.5.62,<2.0.0,while boto3==1.4.4 requires botocore>=1.5.0,<1.6.0.
According to pip’s “first found wins” installation strategy, botocore 1.16.16 is the actually installed version. However, botocore 1.16.16 does not satisfy botocore>=1.5.0,<1.6.0.
Dependency tree-----------
Thanks for your help.
Best,
Neolith
The text was updated successfully, but these errors were encountered: