Skip to content

maint: avoid regression/breaking change in click and declare our dependency to the library explicitly#525

Merged
consideRatio merged 1 commit intodask:mainfrom
consideRatio:pr/avoid-click-regression
Apr 6, 2022
Merged

maint: avoid regression/breaking change in click and declare our dependency to the library explicitly#525
consideRatio merged 1 commit intodask:mainfrom
consideRatio:pr/avoid-click-regression

Conversation

@consideRatio
Copy link
Copy Markdown
Collaborator

@consideRatio consideRatio commented Apr 6, 2022

dask-gateway was dependent on click, but we didn't declare that dependency explicitly but instead relied on it showing up as a dependency from something else we had installed. Since we have a direct import click statement in the dask-gateway project, I suggest it is listed explicitly as a dependency like done in this PR now.

As part of listing click as an explicit dependency, we also pin it to avoid 8.1.0-8.1.2 which breaks things for us as discussed in #522.

@consideRatio consideRatio force-pushed the pr/avoid-click-regression branch from c90268c to e522f83 Compare April 6, 2022 09:13
@consideRatio consideRatio changed the title maint: avoid click regression and declare our dependency maint: avoid click regression and declare our dependency to click Apr 6, 2022
@consideRatio consideRatio changed the title maint: avoid click regression and declare our dependency to click maint: avoid regression in click and declare our dependency to the library explicitly Apr 6, 2022
@consideRatio consideRatio changed the title maint: avoid regression in click and declare our dependency to the library explicitly maint: avoid regression/breaking change in click and declare our dependency to the library explicitly Apr 6, 2022
@consideRatio consideRatio force-pushed the pr/avoid-click-regression branch from e522f83 to e5415df Compare April 6, 2022 09:31
@consideRatio
Copy link
Copy Markdown
Collaborator Author

Aaarrgh, I have to pin click in four separate places!!! I think its absolutely critical that we de-duplicate the dependencies we list for maintenance to be sustainable.

I'll go for a self-merge on this so I can rebase #519 and avoid this added complexity to that PR.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant