Skip to content

Conversation

@mattdawkins
Copy link
Member

No description provided.

@mattdawkins mattdawkins requested a review from Purg November 19, 2019 04:05
@Purg
Copy link
Member

Purg commented Nov 19, 2019

I thought this was originally not required for this as I thought that saving the tuple-cast version of the set would use numpy format. Turns out though that when using large integers, e.g. 256-bit ints (because hash codes), numpy can't use one of its built-in types to cast to so it creates an array whose values are of python-object type. Then, because this isn't a numpy type, numpy cascades into using pickle to serialize the array components. Thus allow_pickle is required on load of that array due to the default change in numpy.

@Purg
Copy link
Member

Purg commented Nov 19, 2019

@mattdawkins Is there bandwidth to add a unit test for this as well as adding a change-note?

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.

2 participants