ENH: support HDFStore in Python3 (via PyTables 3.0.0) #3762
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
DOC: v0.11.1 updates
BUG: more encoding/decoding issues
…s in
the numexpr expressions
jreback
added a commit
that referenced
this pull request
Jun 6, 2013
ENH: support HDFStore in Python3 (via PyTables 3.0.0)
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.
closes #3750
recently released PyTables 3.0.0 (and numexpr 2.1), which now support python3
were completely broken
These changed all data to be stored as bytes (with to/from encoding/decoding)
This PR supports an encoding argument (if you really want to encode your data),
and provides transparent access for python3 (and backwards compat) to
even python2 written stores