FIX, CI: Temporarily disable pytest's caching in Pyodide job

[agriyakhetarpal]

Description

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:

1. The Pydantic upper-pin, i.e., pydantic<2 is not needed anymore
2. Skipping this job on forks
3. A more readable condition for the Anaconda index upload step

The workflow is passing on my fork, here: https://github.com/agriyakhetarpal/pywt/actions/runs/9287344567/job/25556120583

What issue does this PR reference?

Closesgh-742. For additional context: this PR fixes an unrelated error which was noted in #742 (comment), 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.

[rgommers]

LGTM, thanks for the quick fix @agriyakhetarpal!

[agriyakhetarpal]

Description

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:

1. The Pydantic upper-pin, i.e., pydantic<2 is not needed anymore
2. Skipping this job on forks
3. A more readable condition for the Anaconda index upload step

The workflow is passing on my fork, here: https://github.com/agriyakhetarpal/pywt/actions/runs/9287344567/job/25556120583

What issue does this PR reference?

Closesgh-742. For additional context: this PR fixes an unrelated error which was noted in #742 (comment), 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.

[rgommers]

LGTM, thanks for the quick fix @agriyakhetarpal!

[agriyakhetarpal]

Description

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:

1. The Pydantic upper-pin, i.e., pydantic<2 is not needed anymore
2. Skipping this job on forks
3. A more readable condition for the Anaconda index upload step

The workflow is passing on my fork, here: https://github.com/agriyakhetarpal/pywt/actions/runs/9287344567/job/25556120583

What issue does this PR reference?

Closesgh-742. For additional context: this PR fixes an unrelated error which was noted in #742 (comment), 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.

[rgommers]

LGTM, thanks for the quick fix @agriyakhetarpal!

[agriyakhetarpal]

Description

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:

1. The Pydantic upper-pin, i.e., pydantic<2 is not needed anymore
2. Skipping this job on forks
3. A more readable condition for the Anaconda index upload step

The workflow is passing on my fork, here: https://github.com/agriyakhetarpal/pywt/actions/runs/9287344567/job/25556120583

What issue does this PR reference?

Closesgh-742. For additional context: this PR fixes an unrelated error which was noted in #742 (comment), 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.

[rgommers]

LGTM, thanks for the quick fix @agriyakhetarpal!

[agriyakhetarpal]

Description

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:

1. The Pydantic upper-pin, i.e., pydantic<2 is not needed anymore
2. Skipping this job on forks
3. A more readable condition for the Anaconda index upload step

The workflow is passing on my fork, here: https://github.com/agriyakhetarpal/pywt/actions/runs/9287344567/job/25556120583

What issue does this PR reference?

Closesgh-742. For additional context: this PR fixes an unrelated error which was noted in #742 (comment), 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.

[rgommers]

LGTM, thanks for the quick fix @agriyakhetarpal!

[agriyakhetarpal]

Description

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:

1. The Pydantic upper-pin, i.e., pydantic<2 is not needed anymore
2. Skipping this job on forks
3. A more readable condition for the Anaconda index upload step

The workflow is passing on my fork, here: https://github.com/agriyakhetarpal/pywt/actions/runs/9287344567/job/25556120583

What issue does this PR reference?

Closesgh-742. For additional context: this PR fixes an unrelated error which was noted in #742 (comment), 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.

[rgommers]

LGTM, thanks for the quick fix @agriyakhetarpal!

[agriyakhetarpal]

Description

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:

1. The Pydantic upper-pin, i.e., pydantic<2 is not needed anymore
2. Skipping this job on forks
3. A more readable condition for the Anaconda index upload step

The workflow is passing on my fork, here: https://github.com/agriyakhetarpal/pywt/actions/runs/9287344567/job/25556120583

What issue does this PR reference?

Closesgh-742. For additional context: this PR fixes an unrelated error which was noted in #742 (comment), 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.

[rgommers]

LGTM, thanks for the quick fix @agriyakhetarpal!

[agriyakhetarpal]

Description

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:

1. The Pydantic upper-pin, i.e., pydantic<2 is not needed anymore
2. Skipping this job on forks
3. A more readable condition for the Anaconda index upload step

The workflow is passing on my fork, here: https://github.com/agriyakhetarpal/pywt/actions/runs/9287344567/job/25556120583

What issue does this PR reference?

Closesgh-742. For additional context: this PR fixes an unrelated error which was noted in #742 (comment), 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.

[rgommers]

LGTM, thanks for the quick fix @agriyakhetarpal!