nptyping version downgrade to avoid code refactoring #76
Open
h2jaafar wants to merge 1 commit intoperfectly-balanced:masterfrom
Open
nptyping version downgrade to avoid code refactoring #76h2jaafar wants to merge 1 commit intoperfectly-balanced:masterfrom
h2jaafar wants to merge 1 commit intoperfectly-balanced:masterfrom
Conversation
Contributor
Author
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Currently, when new users pull the repository and create a venv, the requirements.txt file will install nptyping v2.0+, which seems to cause the following issue:
The syntax seems to have changed. This problem is dotted throughout the code.
A temporary fix is to simply peg the version of nptyping to 1.4.4, and avoid this problem at the moment.