James Gaboardi

Seems like no initial tag was ever made. I would suggest `v0.0.1`. When you are ready to create the tag from you machine do: ``` git tag -a v0.0.1 -m...

No, the failure is coming from the [`tools/gitcount.ipynb`](https://github.com/pysal/access/actions/runs/4683952297/jobs/8299566391#step:7:1) notebook. This is [failing](https://github.com/pysal/access/actions/runs/4683952297/jobs/8299566391#step:7:74) because the first line of [`__init__`](https://github.com/pysal/access/blob/main/access/__init__.py) no longer contains the version. The [solution I used previously](https://github.com/pysal/spaghetti/pull/654/files#diff-ab45a5565661ce145449ee7e61410c0e3e745bcf44a7b786802b78fd8b7f786dR153-R170) was to...

I will give it attention over the weekend, if that's OK. Across the ecosystem we have been a bit fluid recently with adopting improved infrastructure. For example, swaping out `setup.py`...

xref #21

@JamesSaxon I might have time tomorrow to do this. Also, I suggest we adopt [`black`](https://github.com/psf/black) format for the repo as we have done in most other PySAL modules. By going...

let's hold off for this. the ecosystem is migrating towards `setuptools_scm` for versioning.

Closing out per #48

@JamesSaxon Do we want to wait for Eli's response before doing this next release?

Anything blocking this merge?

Looks like [`pysal` isn't actually being installed](https://github.com/pysal/pysal/actions/runs/9055028425/job/24875540666?pr=1305#step:6:28) here? ``` _________________ ERROR collecting pysal/tests/test_imports.py _________________ ImportError while importing test module '/home/runner/work/pysal/pysal/pysal/tests/test_imports.py'. Hint: make sure your test modules/packages have valid Python names....