Updates to table metadata #1640
Merged
Conversation
This file contains 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
larrybradley
force-pushed
the
table-meta
branch
from
d50916e
to
a927ce7
Compare
larrybradley
force-pushed
the
table-meta
branch
from
a927ce7
to
1c48de5
Compare
7 tasks
7 tasks
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.
The metadata in output tables now contains a timestamp (also with package versions).
Package versions in table metadata are now stored in the "versions" key. Previously, this key was named "version".
Also, the order of the metadata in a table is now preserved when writing to a file. The astropy Table class currently does not preserve key order when serializing
dictobjects (using yaml). However, Table.meta currently usesOrderedDictand its key order is preserved when serializing. Here, we use the default meta type to preserve key order.