Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix: #49 allow newer version of dependencies #57

Merged
merged 2 commits into from
May 13, 2021
Merged

Conversation

bhamail
Copy link
Contributor

@bhamail bhamail commented May 12, 2021

Allow newer version of dependencies.

The click library had failures when the very recently released v8.0.0 was used, so I added an upper bound to solve that issue for now.

Also fixed an error due to db.purge deprecation, replaced with db.truncate call.

cc @bhamail / @DarthHater

@bhamail
Copy link
Contributor Author

bhamail commented May 12, 2021

@jwa5426 Please holler if this looks sane to you.

Comment on lines 1 to 3
pylint>=2.6.0
responses>=0.12.0
unittest-xml-reporting>=3.0.4
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Oof, I hate seeing stuff like this. Why do we have to do it? We can't just pin to a known version?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Seems fine to pin to specific dev deps, as I'm guessing that will not interfere with Jake being used to scan projects. I will push some changes to lock these dev dep version down (as they used to be).

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Dev deps locked: 5189624

@jwa5426
Copy link
Contributor

jwa5426 commented May 13, 2021

@bhamail I agree with preventing the click 8.0.0 issue, I actually ran into that as well. For some of the other non-issue ones maybe it is a good idea to keep them pinned to known good versions or at least a tighter range.

@bhamail
Copy link
Contributor Author

bhamail commented May 13, 2021

@jwa5426 Thanks for looking this over! I was trying to fix the issues described in Issue #49, and "looser" version ranges seemed better for the reasons mentioned there. That said, I'm not against adding upper bounds to version ranges when we slam into known issues (e.g. click 8.0.0).

@jwa5426
Copy link
Contributor

jwa5426 commented May 13, 2021

@bhamail seems reasonable to me 👍

@bhamail bhamail merged commit 15553d4 into main May 13, 2021
@bhamail bhamail deleted the relax_requirements branch May 13, 2021 18:14
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

[BUG] requirements pinned to rigidly
3 participants