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 pydicom from requirements #87

Merged
merged 3 commits into from
Mar 1, 2022
Merged

Conversation

ieee8023
Copy link
Member

Based on a reviewers comment I'm making this PR. I agree it is hard to have pydicom as a requirement because it pretty low level so it could have issues installing and most of the datasets don't need it.
My concern is that I'm doing it is inefficient.

Copy link
Collaborator

@josephdviviano josephdviviano left a comment

Choose a reason for hiding this comment

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

I can't see the diffs from the notebook.

I think this is totally fine. I've seen this pattern before. A better solution would be to fully replace the use of pydicom with something more lightweight but that's a lot of work and potentially not really worth the effort.

@josephdviviano
Copy link
Collaborator

We should just make sure to clearly document the pydicom version that should be installed if the user wants to use the dataloaders, just to avoid nasty python environment mistakes which are extremely hard for the end user to debug.

@ieee8023
Copy link
Member Author

ieee8023 commented Mar 1, 2022

It seems the existing requirement was for pydicom>=1 and the current version is 2.2.2 so it seems not such a big deal for the version.

@ieee8023 ieee8023 merged commit d4b7b1f into master Mar 1, 2022
@ieee8023 ieee8023 deleted the dynamic_import_pydicom branch March 1, 2022 22:58
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.

2 participants