Clean up install

[eliotwrobson]

Found by @nwalters512 (context omitted)

@caleb531 we should remove the tests directory from the published version of the package. Might it be a good idea to use a more modern build tool like uv for publishing / dependency management? I used it for another project, and it was very straightforward to set up automated testing / publishing.

[caleb531]

@eliotwrobson Could you please provide some more context for the original issue here? We already have an __init__.py in the tests functionality, so would that not already be the "immediate fix"?

I always thought build was the official Python means of building packages for publishing, but even the build documentation mentions uv. So, if you really feel uv would be a good choice for automata, then I'd gladly review a PR!

[eliotwrobson]

Could you please provide some more context for the original issue here? We already have an __init__.py in the tests functionality, so would that not already be the "immediate fix"?

Sorry, the screenshot on its own is a little confusing. The issue he is referring to is that in a Python file someone had locally, they were trying to import from another file in a local tests folder, and Python was not recognizing this and instead trying to import from the tests directory included on the path from this library. This issue is happening because the tests directory is being included in this package during publishing.

I always thought build was the official Python means of building packages for publishing, but even the build documentation mentions uv. So, if you really feel uv would be a good choice for automata, then I'd gladly review a PR!

Sounds good, I'll give it a shot! It should simplify the extra files in this package a good bit (we can put all of our dev requirements into pyproject.toml). Will tag you for a review when it's ready.

[caleb531]

@eliotwrobson Since #254 was merged a month ago, is there anything more within the scope of this issue that hasn't been implemented yet? Or are we ready to close this issue?

[eliotwrobson]

@caleb531 I think we're good! I think I meant to close but just forgot earlier, so I'll go ahead and do that now.