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
Reorg #925
Closed
Closed
Reorg #925
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
test failures look like an issue in the |
DOC: make code snippet in documentation compatible to Python 3
install mandatories first, then install optionals
api testing api testing stub for integration testing
…install legacy pysal
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.
Start of Makefile for exploring reorg_dist.
Note that for the modules we are bringing in (only libpysal and esda for exploration at the moment) we have to haul their package folders up one level after cloning. This works but I'm wondering if there are going to be problems induced here?
We could punt on the source redistribution and just rely on pip to install the dependencies (i.e., libpysal, esda, spint.......)? In this case the makefile could be used for setting up a local dev environment, while the dependences remain outside of the pysal/pysal upstream repository? Food for thought.
Also added a setup.py for the metapackage. This would have pip do the heaving lifting on dependencies - pysal becomes a lightweight metapackage.