Conversation
No AI slop here!
* Adds skip to all the v1 tests by default * Unskip v1 tests or files using `passing_v2` marker
Member
|
There is a new pytest marker that you can add to a v1 file or specific test to "turn it on" for this branch. I turned on Output |
Member
|
☝🏻 8d615c2 should be green |
Member
|
Ok! I am skipping |
* If the file exists, read it * Just write it if it's windows and not obvioiusly a url * Use the DEFAULT_READER even in the validator
Member
|
I think the windows tests will pass now and we'll be all green |
* Add bands as a top-level constuct * Add repr for bands
* New implementation of CommonMetadata * Add common metadata protocols to Item and Asset
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
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.
PySTAC v2.0 is a ground-up re-write of PySTAC. Our high-level design goals are a form of Postel's law:
To do so, we have some specific implementation strategies.
Item,Catalog,Collection, etc. We shouldn't change the external APIs unless there's a good reason to.Item,Catalog, etc are the "what" of pystac. Things likeStacIOare the "how". We should create replacement structures for any of these "how" interfaces that we want to dramatically change, rather than try to "fix" the existing ones. Backwards compatibility will be much more difficult for these "how" interfaces, so we shouldn't even try. If possible we should re-write the existing "how" structure (e.g.StacIO) to use the new API, but this should be a lower-priority objective.pystac.read_file.We've got v2 docs here: https://stac-utils.github.io/pystac/
v1 test compatibility
To break the API as little as possible, we're keeping the v1 test suite in
tests/v1. As we build v2, we'll update this table to show how close we are to passing all1 v1 tests:Footnotes
Some tests, such as those that check for exceptions that we've relaxed, we mark as
xfail↩