Gallery versioning

[mberz]

We've now already had a couple of issues and PRs regarding updated due to pyfar version updates (#98, #100)
It's probably a good idea to start introducing versioning the gallery and tracking the respective working pyfar version numbers in the requirements file.

[f-brinkmann]

+1

What we could maybe also do is to add a test of running the notebooks where warnings are raised as errors to more quikly notice such things

[mberz]

Catching deprecation warnings probably is a good idea in that case. Failing tests on every warning is probably a bit too verbose and restrictive.

[ahms5]

I have tried this yesterday

pytest --nbmake docs/gallery/interactive/*.ipynb  -W error::DeprecationWarning

but it not working, I did not go deeper into is

[mberz]

It probably would need to be configured in nbmake to parse the notebook output

[ahms5]

we could also use the cookiecutter template for fixing this issue. Introducing a pyproject.toml would also be possible in this case

[mberz]

we could also use the cookiecutter template for fixing this issue. Introducing a pyproject.toml would also be possible in this case

I'm not sure I'm getting this. How would the cookiecutter help with this?
The original suggestion was to assign version numbers to the gallery and track the version numbers of the dependencies.

[ahms5]

and the cookiecutter provides everthing what is required for it.

[mberz]

Ah, now I got it 🙂