issues with pinned click version #8502
Description
We install the aws-sam-cli in our local dev environments. Due to click being pinned to 8.1.8, it creates some issues when trying to manage dependency.
Is it possible to widen the allowed range for the click version?
This is coming up when trying to constrain our common dependencies first and the constraining the various environments (dev, pipeline, etc) against those. In our case python-dotenv does not care about which click version it receives, meaning in our generated requirements.txt file you end up with the latest version of click. When our dev environment is constrained against this, it creates a resolution error.
This may be a bit of edge case but your eyes on this would be appreciated.