-
Notifications
You must be signed in to change notification settings - Fork 34
Vector #17
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
base: master
Are you sure you want to change the base?
Vector #17
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@tom-de-smedt these functions aren't quite right (before), as if you passed a bytes e.g. b"a" it became 'b"a"'. Python 3 is much less forgiving!
|
@tom-de-smedt It would be good to get some expert eyes on this! (tbh I'm not sure what I'm looking for whilst debugging.) The test is |
|
bump. @tom-de-smedt ? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
IIRC without this change there was an infinite loop / recursion.
|
Actually on looking again the tests are intermittant failures. This makes me think a. we aren't seeding enough (perhaps as python 3 walks tests/dicts in a different/random order). But also there is some hidden logic failures (which may also exist on python 2). Run a few times... (nearly) all different 😢: Perhaps there is a cache which is getting propogated in a random (due to python dict no longer being ordered)... Eeeep. |
There's a failing test on py3, classification correct 50% of the time (always correct on python 2).