James Gaboardi

@sjsrey I can get started on this if you like, though I will need admin permissions. Following the actual renaming we should... * add a (temporary) note to `README.md` for...

@martinfleis nice find

More strangeness. After calling `libpysal.examples.available()` the New Haven data is found in a buried directory. ```python In [1]: import libpysal In [2]: libpysal.examples.get_path("newhaven_nework.shp") newhaven_nework.shp is not a file in any...

See also Joris' [blog post](https://jorisvandenbossche.github.io/blog/2020/02/11/geopandas-pyproj-crs/).

And we could swap in native `pysal` geometries is that kind of check, correct?

> one small complication is that if we wanted this in libpysal, there's not really anywhere in the current namespace that's super appropriate What about [`common.py`](https://github.com/pysal/libpysal/blob/master/libpysal/common.py)?

hmmm. Not able to see the diagnostic from [the last time this was run](https://github.com/pysal/libpysal/runs/2926315274?check_suite_focus=true), but both the latest [GitHub (`v4.5.1.post2`)](https://github.com/pysal/libpysal/releases/tag/v4.5.1.post2) and PyPI [`v4.5.1`](https://pypi.org/project/libpysal/4.5.1/) releases were done on 2021/06/27. So it...

Somewhat related to pysal/momepy#307.

So does this mean the appropriate tag is not being pushed by the GHA? Or that `v4.5.1.post{1,2}` are being evaluated as older versions than `v4.5.1`?

Maybe we should release a `v4.5.2`?