-
Notifications
You must be signed in to change notification settings - Fork 3.6k
Patch jsonargparse for Python >= 3.12.8 #20479
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
Conversation
Codecov ReportAttention: Patch coverage is
Additional details and impacted files🚀 New features to boost your workflow:
|
4069d3b to
ce4763d
Compare
22e6412 to
47c36ad
Compare
aa7d781 to
68677d3
Compare
788d419 to
48b944c
Compare
ee13a3e to
78ba069
Compare
5181443 to
918f2c6
Compare
|
Seems like this patch is actually causing things to break now that jsonargparse is updated? TorchGeo CI is not happy with the 2.5.0 release: https://github.com/microsoft/torchgeo/actions/runs/12438070046/job/34729248038?pr=2484 |
|
hey @adamjstewart looking into this, will issue a post release that fixes this in the next few minutes |
|
ok so should we bump |
|
My vote would be to remove the patch and allow users to use any version of jsonargparse. This is a bug in jsonargparse, not a bug in lightning. Let users complain to jsonargparse, and then let jsonargparse tell them to upgrade to newer jsonargparse if they want to use newer Python. Users on older Python can still use older jsonargparse with newer lightning, lightning has no problems with older jsonargparse. |
What does this PR do?
This PR is a temporary fix to omni-us/jsonargparse#641
so that users are not impacted even prior to the upstream fix being released.
This undoes pinning introduced in #20476
📚 Documentation preview 📚: https://pytorch-lightning--20479.org.readthedocs.build/en/20479/