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

Remove unnecessary pyzmq requirement #612

Merged
merged 1 commit into from
Aug 5, 2024

Conversation

xiacunshun
Copy link
Contributor

'pyzmq' is not used in sources, which was pulled in in 79b0b02

'pyzmq' is not used in sources, which was pulled in in 79b0b02

Signed-off-by: cunshunxia <cunshunxia@tencent.com>
@xiacunshun
Copy link
Contributor Author

pyzmq is required by ipykernel and we don't need this in our requirement list.

@dalthviz
Copy link
Collaborator

dalthviz commented Aug 1, 2024

Thank you @xiacunshun for your feedback and submitting a PR with the required changes! Checking seems like #416 was the PR where the pyzmq dependency was introduced. To be honest I'm not sure why it was introduced at that time (maybe to make tests past due to some package installation error over CI?). Should the dependency be removed @ccordoba12 ? Seems like tests pass without it. The error over a couple of CI jobs seems like comes from the Upload coverage to Codecov step so not related with this 🤔

@ccordoba12 ccordoba12 added the task label Aug 2, 2024
@ccordoba12 ccordoba12 added this to the 5.6.0 milestone Aug 2, 2024
@ccordoba12
Copy link
Collaborator

I think this is fine but I don't understand how it'll help your use case @xiacunshun given that IPykernel is (and will continue to be) a dependency of this package.

@ccordoba12 ccordoba12 changed the title remove unused requirement 'pyzmq' Remove unnecessary pyzmq requirement Aug 2, 2024
@xiacunshun
Copy link
Contributor Author

@ccordoba12 I am one of the maintainers of the pipdeptree project and also the maintainer of the OpenCloudOS distribution. Currently, I am developing a Python dependency checking tool. This tool will scan and identify dependencies that do not match the modules actually used in the source code. The aim is to make the dependency relationships of Python projects clearer, which can facilitate us in trimming some unnecessary dependencies when creating images.

@xiacunshun
Copy link
Contributor Author

It's possible that this module may be depended upon by other software, but in reality, it's irrelevant to the current project. If one day the dependent Python project changes its own dependencies, the current project would be unaware of it.

@minrk
Copy link
Member

minrk commented Aug 5, 2024

pyzmq's a transitive dependency via jupyter-client, etc., so removing it won't remove the dependency, but it may affect the constraint. I think this is looser than others now anyway, so it probably has no effect and can be safely removed. If it's not used directly and if there aren't version constraints specific to this package (there may have been in the past), it doesn't need to be here.

@ccordoba12
Copy link
Collaborator

Thanks @xiacunshun for the extra info and @minrk for chiming in. I think both arguments make sense so I'm going to merge this PR.

Copy link
Collaborator

@ccordoba12 ccordoba12 left a comment

Choose a reason for hiding this comment

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

Thanks for your contribution @xiacunshun!

Note: The failures in our tests are unrelated to these changes.

@ccordoba12 ccordoba12 merged commit d592079 into jupyter:main Aug 5, 2024
20 of 22 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants