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

Bump requirements python3.8 #15

Closed
wants to merge 6 commits into from
Closed

Bump requirements python3.8 #15

wants to merge 6 commits into from

Conversation

camila-ud
Copy link
Contributor

Bump requirements to be compatible with python 3.8

Hi @percevalw,

We would like to integrate a NER operation in medkit using the model developed in this paper: Privacy-preserving mimic models for clinical named entity recognition in French

We have developed the operation, but we have found some issues with the requirements of nlstruct v0.1.

I made this PR with the suggested versions of torchmetrics, pytorch_lightning and others.
For info, these packages have removed support for Python <= 3.7 in the latest versions.

I have tested the operation in inference, and it works fine.
Please let me know what you think about this PR.

Torchmetrics 0.8 has removed support for versions of Pytorch-Lightning
lower than v1.5 (#788)
The argument was remove in torchmetrics v0.9. Keep the argument in __init__
for backward compatibility only.
@percevalw
Copy link
Owner

percevalw commented Dec 12, 2023

Hi Camila, thank you for looking into this! Indeed, pytorch-lightning & co dependencies have been quite tricky due to their many changes since the start of this project. The problem with simply relaxing the constraints is that many of pytorch lightning's features and methods have been moved around or deprecated, and the library needs to be able to perform inference as well as training (which fails under the relaxed constraints). I'll look into this shortly to try and work around some of the pl deprecations

@percevalw
Copy link
Owner

I wasn't able to commit in this PR, so I've moved some of your work to #16 to solve some compatibility issues with pytorch-lightning v2 mostly.

@camila-ud
Copy link
Contributor Author

I close this PR because the discussion has been moved to #16

@camila-ud camila-ud closed this Dec 13, 2023
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