@jameskrach I think it makes sense to factor this out into a new issue :)

A few ideas off the top of my head:

• Replacing thepoetry-specific specification of development dependencies with theformat standardized in PEP-621. This would allow contributors to use whatever dependency manager they prefer to contribute (maintainers would still of course be free to use poetry for building and releasing the package).
• Committing a known-good set of dependencies to help resolve confusion about why code may not be working on two different individuals' machines (example from numpy).
• Setting up aGitHub Action to run tests to remove any ambiguity around whether a contribution works. There is a reasonably generousfree tier that should be sufficient for this project.

Related to the last two points, were either of you able to see if the tests passed on your machine(s) when run from the branch I opened?

Originally posted by@jameskrach in#581

• CfUpdate pyproject.toml to use PEP-621 dependency specification #584.

I think we have the last point somewhat covered already, though I'm sure this can always be improved. If you have suggestions, feel free to let me know.

The first point is really good, I personally useuv and it's a bit of a pain point to set up the environment with the non-standardpyproject.toml.