setuptools: adopt PEP 639 license metadata#1184
Merged
Merged
Conversation
Signed-off-by: Adam J. Stewart <ajstewart426@gmail.com>
romeokienzler
approved these changes
May 8, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The previous license syntax is deprecated and will be removed from future versions of setuptools, use the recommended PEP 639 syntax instead.
Since TerraTorch contains files under an Apache-2.0 license and an MIT license, it should be dual-licensed. It's only a few dataset-specific files, so I think these would be a good target for upstreaming to TorchGeo so that TerraTorch can go back to a single license. Similarly, if we encounter any new FMs we want under an Apache-2.0 license, we will try to push them to TerraTorch instead of TorchGeo.