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.

Sign up for GitHub

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

Jump to bottom

Unpin versions in test requirements #4980

Open
marthacryan opened this issue Jan 23, 2025 · 0 comments
Open

Unpin versions in test requirements #4980

marthacryan opened this issue Jan 23, 2025 · 0 comments
Assignees
@marthacryan
Labels
infrastructure build process etc. P1 needed for current cycle testing automated tests

Comments

@marthacryan
Copy link
Collaborator

All of the test_requirements files have a bunch of pinned versions, which would prevent us from actually catching bugs with newer versions of packages. It also means that we have a separate requirements file for every version of python that we test, which makes changing the requirements unnecessarily complicated.
@gvwilson gvwilson added P1 needed for current cycle infrastructure build process etc. testing automated tests labels Feb 3, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@marthacryan marthacryan

Labels
infrastructure build process etc. P1 needed for current cycle testing automated tests
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@gvwilson @marthacryan