ci update

[sjsrey]

Addressing #1299

[sjsrey]

This was modeled after spopt ci, for reference.

[jGaboardi]

Shall we move spopt into the dependencies section (in all environments)?

[jGaboardi]

Gentle ping to remind to remove the pip: spopt and move spopt directly up beneath splot in an CI environments for this PR.

[jGaboardi]

For the -oldest tag we should ideally have minimum pins. We could probably simply follow SPEC000 for this.

[martinfleis]

That is a bit tricky to do in here as you would need to pin 2nd order dependencies, given the pysal depends only on subpackages, where we always want to pull the latest, never the oldest. I would probably leave this env out.

[jGaboardi]

@sjsrey If we follow @martinfleis's idea here, we can simply rename 310-oldest.yaml --> 310-latest.yaml (and in the workflow file) and have done with it.

[jGaboardi]

Looks like pysal isn't actually being installed 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.
Traceback:
../../../micromamba/envs/test/lib/python3.12/importlib/__init__.py:90: in import_module
    return _bootstrap._gcd_import(name[level:], package, level)
pysal/tests/test_imports.py:2: in <module>
    from pysal import federation_hierarchy
E   ModuleNotFoundError: No module named 'pysal'

[jGaboardi]

re: pacakage install

For some packages (e.g. spopt and spaghetti), merely checking out the repo is enough. However, this is not the case most of time (e.g. tobler and momepy). I have never been able to figure the difference and why it is not needed sometimes. Seems like it is needed here.

[jGaboardi]

Is this file still even needed? I opened #1306 because I thought it could be pruned entirely.