-
Notifications
You must be signed in to change notification settings - Fork 1
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
add predefined facility fulfillment option #2
Conversation
Co-authored-by: jGaboardi <[email protected]>
* ruff-en code base * remove versioneer * adopt pyproject.toml * clean up envs, etc. * update codecov * test again master and main libpysal (temp) * only test dev against libpysal@main * update other dev pins * add mapclassify, etc. to dev env * ensure all deps are installed in dev * re-ruff repo * ruff based on py39 * ruff based on py38 * resolve typing issues <3.9 [1] * resolve typing issues <3.9 [2] * address review comments
updates: - [github.com/charliermarsh/ruff-pre-commit: v0.0.252 → v0.0.254](astral-sh/ruff-pre-commit@v0.0.252...v0.0.254) Co-authored-by: pre-commit-ci[bot] <66853113+pre-commit-ci[bot]@users.noreply.github.com>
updates: - [github.com/charliermarsh/ruff-pre-commit: v0.0.254 → v0.0.255](astral-sh/ruff-pre-commit@v0.0.254...v0.0.255) Co-authored-by: pre-commit-ci[bot] <66853113+pre-commit-ci[bot]@users.noreply.github.com>
updates: - [github.com/charliermarsh/ruff-pre-commit: v0.0.255 → v0.0.257](astral-sh/ruff-pre-commit@v0.0.255...v0.0.257) Co-authored-by: pre-commit-ci[bot] <66853113+pre-commit-ci[bot]@users.noreply.github.com>
* address new ruff failures * proper stacklevel * update precommit * revisit stacklevels
updates: - [github.com/charliermarsh/ruff-pre-commit: v0.0.261 → v0.0.262](astral-sh/ruff-pre-commit@v0.0.261...v0.0.262) Co-authored-by: pre-commit-ci[bot] <66853113+pre-commit-ci[bot]@users.noreply.github.com>
updates: - [github.com/charliermarsh/ruff-pre-commit: v0.0.262 → v0.0.263](astral-sh/ruff-pre-commit@v0.0.262...v0.0.263) Co-authored-by: pre-commit-ci[bot] <66853113+pre-commit-ci[bot]@users.noreply.github.com>
updates: - [github.com/charliermarsh/ruff-pre-commit: v0.0.263 → v0.0.269](astral-sh/ruff-pre-commit@v0.0.263...v0.0.269) Co-authored-by: pre-commit-ci[bot] <66853113+pre-commit-ci[bot]@users.noreply.github.com>
@ljwolf Hi Levi! I am currently rechecking the code changed in the fulfillment of predefined facility's capacity. The problem is that I find it's hard to separate my code from yours because the options I added are based on the predefined facility section you wrote earlier. In this case, maybe I should still make a pull request directly to you? |
Hey! It's ok to open a new PR directly to pysal/spopt with your extra changes. That PR will have both what I've done and what you've added to it. That's totally ok. What @jGaboardi wanted is to have your name on the PR as the contributor, instead of mine, regardless of the authors of the individual commits 😄 Does that make sense? |
Oh Thank you!!! Now I understand! I will open a new PR when I finish this part! |
* shapely & geopandas version bump * try resolve windows pytest failure * channel-priority no longer a valid micromamba arg * try w/0 min geopandas pin * drop 3.8 support * only use pins in min CI env * bump min scipy * bump min scikit-learn * bump min shapely==2.0.1 * py38-MIN ci resolved * pin pandas in 38
updates: - [github.com/charliermarsh/ruff-pre-commit: v0.0.269 → v0.0.270](astral-sh/ruff-pre-commit@v0.0.269...v0.0.270) Co-authored-by: pre-commit-ci[bot] <66853113+pre-commit-ci[bot]@users.noreply.github.com>
Create a new class
I think this should be closed in favour of pysal#387 |
No description provided.