The pytest test suite tries to generate additional bytecode files after its completion, and it then tries to save them to a filesystem that is read-only for unexplored reasons. Since this workflow runs only in a temporary CI job, the .pyc file generation can be disabled with the internal pytest plugin using -p no:cacheprovider.
Some other fixes are included as well:
The Pydantic upper-pin, i.e., pydantic<2 is not needed anymore
Skipping this job on forks
A more readable condition for the Anaconda index upload step
Closes gh-742. For additional context: this PR fixes an unrelated error which was noted in https://github.com/PyWavelets/pywt/issues/742#issuecomment-2136963106, and the CI job is already picking up the latest Emscripten version that is coupled with pyodide-build using the value retrieved by the $(pyodide config get emscripten_version) command.
Description
The
pytesttest suite tries to generate additional bytecode files after its completion, and it then tries to save them to a filesystem that is read-only for unexplored reasons. Since this workflow runs only in a temporary CI job, the.pycfile generation can be disabled with the internalpytestplugin using-p no:cacheprovider.Some other fixes are included as well:
pydantic<2is not needed anymoreThe workflow is passing on my fork, here: https://github.com/agriyakhetarpal/pywt/actions/runs/9287344567/job/25556120583
What issue does this PR reference?
Closes gh-742. For additional context: this PR fixes an unrelated error which was noted in https://github.com/PyWavelets/pywt/issues/742#issuecomment-2136963106, and the CI job is already picking up the latest Emscripten version that is coupled with
pyodide-buildusing the value retrieved by the$(pyodide config get emscripten_version)command.