-
Notifications
You must be signed in to change notification settings - Fork 6
Patching parsing issues with approval #11
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?
Conversation
| clean_exit = False | ||
| if isinstance(err, SystemExit): | ||
| clean_exit = True if err.code == 0 else clean_exit |
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.
I find this construction kind of convoluted and therefore a bit difficult to follow. How about something like just
clean_exit = isinstance(err, SystemExit) and err.code == 0?
| clean_exit = False | ||
| if isinstance(err, SystemExit): | ||
| clean_exit = True if err.code == 0 else clean_exit |
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.
same comment
| lookup_key[index] = index_count | ||
| index_count += 1 | ||
| non_functional_cols = [i for i, elem in enumerate(data) if data[i] != 'functional'] | ||
| non_functional_cols = [i for i, elem in enumerate(data) if np.all(data[i] != 'functional')] # Numpy now requires the user cast to a scalar when performing boolean checks on arrays |
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.
This seems confusing, or at least not the optimal way to check. What's being checked for here is just whether data[i] is a string with value 'functional', or a numpy array. Better would probably be to just check if data[i] is a numpy array. Same for the following changes using np.all.
| 1. Make sure you have the following already installed: | ||
| * Either Python v2.7 or later or Python v3 | ||
| * NumPy and SciPy libraries for python (NumPy v0.9.0 or | ||
| * Either Python v2.7 or later or Python v3.8 or later |
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.
Does the use of packaging for versioning break compatibility with Python 2.7? If so, we should just remove 2.7 here, there's no real need to support it any longer.
Patches:
I've cherry-picked the commits on top of the
revert-9-fixesbranch somastercan be fast forwarded once #10 is merged.