Open martinfleis opened 1 year ago
Can you drop a note if you are planning to work on any of the topics mentioned above so we don't overlap?
I am unlikely to have time until sept 27
I think I’ll go back to ensuring the constructors can consume sparse next
With #577, we're ready for the initial experimental release of Graph.
NotImplementedError
at the moment.Anything else you'd like to get in?
I would target the end of the week at the latest to cut 4.8.0 (need it alive on conda on Tuesday)
Anything blocking the release now that #577 is merged?
@jGaboardi any idea if the current infrastructure works as intended? It has not been updated here.
I am not sure. Let's give it try; perhaps as a 4.7.0.post1
release?
More like 4.8.0rc1
given the status of current main
@jGaboardi Action looking good - https://github.com/pysal/libpysal/actions/runs/6353690175/job/17258825775
PyPI is up - https://pypi.org/project/libpysal/4.8.0rc1/
Changelog is completely broken - https://github.com/pysal/libpysal/releases/tag/v4.8.0rc1
Documentation is okay - https://pysal.org/libpysal/
Changelog is completely broken
Yeah, looks like the action still uses tools/gitcount.ipynb
. This will need to be looked it if we still want to use it.
spaghetti
has been using actions/github-script@v6
with success, if we want to try here.
lets update the root and get rid of versioneer etc before doing a real release
@knaaptime Are you on it or shall I?
i'll take the first pass
Unless anyone does that first, I'm happy to cut 4.8.0 later tonight (Prague time) or tomorrow morning.
Unless anyone does that first, I'm happy to cut 4.8.0 later tonight (Prague time) or tomorrow morning.
Seem to have a strange merge problem with upstream/main
vs. my main
. Both docs build and publish failed. Going to delete the v4.8.0
tag and try to figure it out.
Seems like two key pieces slipped through the cracks:
libpysal/docs/conf.py
I'll put in the necessary PR shortly.
we dont need the sys path hack
i think we're using an old recipe for the docs. It should have an install line before making the docs (so you get the real version without doing the sys/path hack). I think there's a current version in tobler
we dont need the sys path hack
Seems to fail without it. Is there something I am missing? Yes, there was. LOL
@knaaptime @martinfleis
Can confirm docs build locally, but with the following warnings:
libpysal/libpysal/cg/shapes.py:docstring of libpysal.cg.LineSegment.bounding_box:1:<autosummary>:1: WARNING: Inline strong start-string without end-string.
libpysal/libpysal/cg/shapes.py:docstring of libpysal.cg.LineSegment.bounding_box:1:<autosummary>:1: WARNING: Inline strong start-string without end-string.
libpysal/docs/notebooks/fetch.ipynb:4: WARNING: Each notebook should have at least one section title
libpysal/docs/notebooks/io.ipynb:4: WARNING: Each notebook should have at least one section title
libpysal/docs/notebooks/Raster_awareness_API.ipynb: WARNING: document isn't included in any toctree
libpysal/docs/notebooks/fetch.ipynb: WARNING: document isn't included in any toctree
libpysal/docs/notebooks/io.ipynb: WARNING: document isn't included in any toctree
tutorial.rst
on purpose? If so, then nothing to fix. I we are OK with that, I will push up the fixes immediately.
Release failed, I think because there is no README.md
in libpysal
... it's README.rst
.
@knaaptime @martinfleis
v4.8.0rc2
is tagged and up on PyPI with docs built successfully. Please give a once over. If everything looks kosher, I will cut v4.8.0
.
All looking good to me!
Do you or Eli want to do the honors since yall put in that hard work? Or shall I go ahead and cut it?
Go ahead 😉
The decision on ID API has been to allow passing an array of IDs when the input is a sparse or dense precomputed array and raise a ValueError
when it is passed alongside a data frame.
xref #712
I tried to outline what is missing before we could cut a release with the new graph stuff. Open to a discussion.
testing
We have a decent coverage of base but especially constructors are not always tested for correctness. So we test the API but not that the adjacency captures what it should. So missing tests:
implementation/checks
Some bits are still waiting for implementation (I have likely missed stuff here) or a double check that the current implementation works as intended.
discussion
A few things I'd like to discuss (during the dev call in 3 minutes?)
transform
? kernels are essentially transformations. Shall we allow to use them post-creation?~follow-up
Stuff that is not implemented or started but that can likely wait for subsequent release, not the initial one. Below is the list of stuff I'd like to see soon but there's more to be done.
lag()
?)documentation
API reference should be in the docs for the first release. user guide can follow later.
Some of the follow-up could be piped via W for the time being if we want them available.