botocore: botocore 1.14.4 blocks users from updating docutils to 0.16
Hi!
When botocore is used in a virtualenv next to other packages or in context of a whole GNU/Linux distribution, this line in setup.py
https://github.com/boto/botocore/blob/70c7767374c42bd86a896391dff55fc25ebfac27/setup.py#L27
blocks users from updating to docutils 0.16 which is not ideal. Can the upper boundary be dropped or be turned into semver-like <1 at least to be more friendly to other packages and user freedom?
Thanks and best, Sebastian
PS: I have seen #900 and #933 (but I don’t consider this the right direction while docutils is imported from public botocore API).
About this issue
- Original URL
- State: closed
- Created 4 years ago
- Reactions: 17
- Comments: 22 (9 by maintainers)
Commits related to this issue
- Downgrade docutils so that boto works See https://github.com/boto/botocore/issues/1942 and related threads. — committed to locusrobotics/catkin_virtualenv by MJohnson459 4 years ago
- Downgrade docutils so that boto works (#66) See https://github.com/boto/botocore/issues/1942 and related threads. — committed to locusrobotics/catkin_virtualenv by MJohnson459 4 years ago
This is not an enhancement, It’s a bug.
Thank you for your post. Marking this as feature request.
It would be nice to have this dependency removed. This issue is going to break a lot of projects in October when PIP starts using its new dependency resolver in PIP version 20.3 (https://pip.pypa.io/en/stable/user_guide/#changes-to-the-pip-dependency-resolver-in-20-2-2020). This version of PIP will be more strict with respect to pinned dependencies.