diff options
| author | Todd Gamblin <tgamblin@llnl.gov> | 2021-07-07 02:55:38 -0700 |
|---|---|---|
| committer | Todd Gamblin <tgamblin@llnl.gov> | 2021-07-07 17:27:31 -0700 |
| commit | a22686279c6e45729c0ce6dc4aee0df2d280b513 (patch) | |
| tree | 64be8a5d347bb39de9414fc9c744dc7405eb6f24 /.github/workflows/macos_python.yml | |
| parent | 0dd04ffbfb97bad2dfe0530a23ab5fa8af89a26b (diff) | |
| download | spack-a22686279c6e45729c0ce6dc4aee0df2d280b513.tar.gz spack-a22686279c6e45729c0ce6dc4aee0df2d280b513.tar.bz2 spack-a22686279c6e45729c0ce6dc4aee0df2d280b513.tar.xz spack-a22686279c6e45729c0ce6dc4aee0df2d280b513.zip | |
cvs tests: don't use dateutil at all
`dateutil.parser` was an optional dependency for CVS tests. It was failing on macOS
beacuse the dateutil types were not being installed, and mypy was failing *even when the
CVS tests were skipped*. This seems like it was an oversight on macOS --
`types-dateutil-parser` was not installed there, though it was on Linux unit tests.
It takes 6 lines of YAML and some weird test-skipping logic to get `python-dateutil` and
`types-python-dateutil` installed in all the tests where we need them, but it only takes
4 lines of code to write the date parser we need for CVS, so I just did that instead.
Note that CVS date format can vary from system to system, but it seems like it's always
pretty similar for the parts we care about.
- [x] Replace dateutil.parser with a simpler date regex
- [x] Lose the dependency on `dateutil.parser`
Diffstat (limited to '.github/workflows/macos_python.yml')
0 files changed, 0 insertions, 0 deletions