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

Find a way to get notified of package incompatibilities #124

Open
GeorgianaElena opened this issue Feb 24, 2021 · 1 comment
Open

Find a way to get notified of package incompatibilities #124

GeorgianaElena opened this issue Feb 24, 2021 · 1 comment
Labels
enhancement New feature or request

Comments

@GeorgianaElena
Copy link
Member

Proposed change

In a recent attempt to use dependabot and frozen dependencies with traefik-proxy, @manics and @minrk presented very great points on how to find package incompatibilities the "right way" for python libraries (like traefik-proxy).
The discussion about this is here.

Available options

A short summary of the possible options to find package incompatibilities (from the discussion mentioned about):

Who would use this feature?

Developers would use this to find out when a certain dependency new release becomes incompatible with traefik-proxy and fix it, rather than reacting to it.

(Optional): Suggest a solution

@GeorgianaElena GeorgianaElena added the enhancement New feature or request label Feb 24, 2021
@consideRatio
Copy link
Member

consideRatio commented Oct 18, 2021

There is also this trick by @minrk! To test against the oldest dependencies, and find them via a requirements.txt file that for example has package_name_here>=1.2.3 and converts it to package_name_here==1.2.3 to force the oldest version to be used in a test suite.

https://github.com/jupyterhub/jupyterhub/blob/534dda3dc73ab603037989dbf1e17318dfffd6b6/.github/workflows/test.yml#L123-L129

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants