Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

On Py3, use cPickle Unpickler #190

Merged
merged 1 commit into from
Dec 27, 2016
Merged

Conversation

kernc
Copy link
Contributor

@kernc kernc commented Nov 18, 2016

Pure-Python unpickler, available as pickle._Unpickler, uses struct to unpack
data, and the latter can also fail with struct.error. The default
C unpickler fails with documented and expectable UnpicklingError, and
is also faster.

Dill's unpickler seems to be a very thin wrapper around pickle's unpickler, so the change is not grave in any way, just somewhat more convenient for the end user.


I'd like to help set up continuous integration build testing on Travis. What is the canonical way to run and depend on tests in the tests folder? If the files are run sequentially and all asserts pass, the build is considered passing?

@matsjoyce
Copy link
Contributor

For the CI/tests part, see #3, #139, #162. Its been on the burner for quite a while... 😄

Pure-Python unpickler, available as _Unpickler, uses `struct` to unpack
data and the latter can also fail with `struct.error`. The default
C Unpickler fails with documented and expectable UnpicklingError, and
is also faster.
@mmckerns mmckerns merged commit bfd8d06 into uqfoundation:master Dec 27, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants