Repository navigation
Fix deepcopy/pickle of binary table columns with the X, P, or Q format - #4514
Merged
Merged
Conversation
Member
Author
|
Giving myself the 👍 |
embray
added a commit
that referenced
this pull request
Jan 22, 2016
Fix deepcopy/pickle of binary table columns with the X, P, or Q format
embray
added a commit
that referenced
this pull request
Jan 27, 2016
Fix deepcopy/pickle of binary table columns with the X, P, or Q format
embray
added a commit
that referenced
this pull request
Jan 27, 2016
Fix deepcopy/pickle of binary table columns with the X, P, or Q format Conflicts: astropy/io/fits/tests/test_table.py
mvnnn
pushed a commit
to mvnnn/astropy
that referenced
this pull request
Jan 30, 2016
dhomeier
pushed a commit
to dhomeier/astropy
that referenced
this pull request
Jun 12, 2016
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.
Incidentally, I came across this bug in testing to see if #520 is still an issue.