Testing to see if switching to a uv build works with GHA #276
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Docassemble >=1.8.0 now installs locally incredibly slow / big enough that it's been breaking GitHub actions when run (https://github.com/SuffolkLITLab/docassemble-EFSPIntegration/actions/runs/16885202477, and https://github.com/SuffolkLITLab/docassemble-EFSPIntegration/actions/runs/16883689579).
Our options:
uvinstead of plain pip to run faster (and maybe use less disk? has to, because it works fine).This PR takes option 2. To do so, it rewrites the
unittest.ymlaction (if this works well, we'll push those changes upstream of ALAction), creating apyproject.toml, and auv.lockfile that saves what versions of things to use (if things go well, we could fix those versions of things to what's present on PROD docassemble).Speedwise, this is a great success! The new tests pass in < 3 minutes, whereas before this changes, successful tests would take 6 to 10 minutes (not even counting the now 28 minutes that DA 1.8 seems to be taking to just install).
Misc
pyproject.tomlhas duplicate information compared to what's insetup.py, but unfortunately, for DA 1.7.7 and below, you can't install a project that just has apyproject.tomland nosetup.py. This seems to be changing, but while we support lower DA versions, we should keep the setup.py file around.pyproject.tomlalso differs from what DA will generate for you, as we're using setuptools-scm to include all of the data files as a part of the package. We'll see what works best: I'm thinking / hoping this will be much simpler for our library projects (i.e. AssemblyLine, ALToolbox, etc.), and we can just stick with DA's default file for interview projects.