James Gaboardi

testing against oldest dependencies across federation

1

Many of the federated packages are not testing against oldest versions of their dependencies. While this is not a critical need, we should keep track of which ones do/don't and...

I'd like to adopt standard linting & formatting w/ `ruff` across the ecosystem to improve diagnostic time when troubleshooting both issue in the codebase & infrastructure. This will also be...

* `...-min` -- minimal dependencies -- only hard requirements -- "no optional" * `...-oldest` -- pinned to oldest supported Python version & packages * `...-latest` -- no pins (accept Python...

Testing against Python 3.12 across federation ------------------------ * [x] `pysal/pysal` * [x] `pysal/access` – https://github.com/pysal/access/pull/62 * [x] `pysal/esda` * [x] `pysal/giddy` – https://github.com/pysal/giddy/pull/228 * [x] `pysal/gwlearn` * [x] `pysal/inequality` *...

removing `spvcm` from meta release -- archived - #1330

8

This PR removing `spvcm` from meta release, as it is now archived - https://github.com/pysal/spvcm/issues/18 * resolves #1330

modernize *GitHub Standard Operating Procedures*

1

The document - [*GitHub Standard Operating Procedures*](https://github.com/pysal/pysal/wiki/GitHub-Standard-Operating-Procedures) - we have linked for contributing guidelines[^1][^2] needs a ***major*** overhaul. [^1]: https://github.com/pysal/pysal/blob/main/.github/CONTRIBUTING.md [^2]: https://pysal.org/docs/devs/

inclusion of `spvcm` in PySAL meta-release

5

https://github.com/pysal/spvcm/issues/17#issuecomment-2217980601 > 3. As for distribution with `pysal/pysal`... > 1. Should we: > 1. ... update the README, docs, landing page, etc. that `spvcm` will not be distributed in the...

We should update the docs and README to reflect the current state of PySAL, especially with the inclusion of the `libpysal.graph` * add `graph` to [PySAL Core](https://github.com/pysal/pysal/blob/main/docs/api.rst#modpysallib-pysal-core) * add `legendgram`...

`v24.1` not available via `conda-forge` / `anaconda`

2

Seems like `v24.1` never made it into [`conda-forge`](https://github.com/conda-forge/pysal-feedstock?tab=readme-ov-file#current-release-info) > [`anaconda`](https://anaconda.org/conda-forge/pysal). The latest release over there is `v23.7`

* cut `v24.07rc2` - release action failed - xref #1313 * xref #1321