PySAL+ optional testing matrix #833
Closed
Conversation
This file contains 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
"exta" should have been "extra." once changed, the screen function needed slight modification to work with the rest of the pattern.
The grid was constructed using np.meshgrid over the range of the bounding box, with a computed stride. If the range and number of divisions were both integer, as was the case in the unittest, this generated floor division incorrectly. When we did initial testing in python3, we thought the unittest was correct. In fact, the unittest was incorrect, and we needed to enforce float division always.
Note that these comparators are NOT OGC-SPEC.
Refactor markov classes to use properties instead of computing everything in the init
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This sets up a multi-environment test matrix for PySAL using an environment variable,
PYSAL_PLUS& is the remaining blocker for #829. It was rebased from #830.If
PYSAL_PLUS, we include everything inrequirements_plus.txtin the testing environment. This way, if we have numba versions of computational functions, tabular methods, etc, these get tested.In theory, these should also be added to the
setup.pyextras_requireflag, if we want to appropriately incorporate this metadata by module.It makes sense to make the
PYSAL_PLUSenvironment as open as possible, as long as things were correctly wrapped in try/except orcommon.requires.I will write that up in a wiki page, too.I've written this notebook documenting things I've seen & tried.