Upgrade notebooks to v0.3.0 of the online lab

[juntyr]

Adapts the notebooks in preparation for v0.3 of the online lab, which updates to Python 3.13, updates all packages, and updates the compression API to use public packages (instead of the in-dev fcbench).

• Reference fsspec store has mismatching asynchron-ity zarr-developers/zarr-python#2946

[SF-N]

I started taking a look and got an error when running the 01-intro.ipynb notebook, when trying to load and run it again, e.g. by calling https://lab.climet.eu/latest/github/climet-eu/compression-lab-notebooks/update-v0-3, only the README.md and the requirements.txt are loading in JupyterLite and an empty compression-lab-notebooks folder.
I had about 5 successful attempts of accessing the online lab until I faced this issue.
I thought the limit of accesses would be much higher than about 5 within half an hour. Does it currently work for you, and do you have any suggestions?

[juntyr]

You need to use the lab main branch (latest is still v0.2.1): https://lab.climet.eu/main/github/climet-eu/compression-lab-notebooks/update-v0-3

I think the rate limit is ~60 files per hour, so given that our repo now has more than 10, this makes sense.

[juntyr]

I've opened jupyterlite/litegitpuller#27

[SF-N]

You need to use the lab main branch (latest is still v0.2.1): https://lab.climet.eu/main/github/climet-eu/compression-lab-notebooks/update-v0-3

This https://lab.climet.eu/latest/github/climet-eu/compression-lab-notebooks/update-v0-3 is what I get from the docs when entering Repository owner: climet-eu, Repository name: compression-lab-notebooks and Git ref: update-v0-3

[SF-N]

With your link the 01-intro.ipynb notebook works fine.
You can go ahead and merge from my point of view.

[juntyr]

You need to use the lab main branch (latest is still v0.2.1): https://lab.climet.eu/main/github/climet-eu/compression-lab-notebooks/update-v0-3

This https://lab.climet.eu/latest/github/climet-eu/compression-lab-notebooks/update-v0-3 is what I get from the docs when entering Repository owner: climet-eu, Repository name: compression-lab-notebooks and Git ref: update-v0-3

It feels like maybe the version names are confusing? Currently, latest refers to the latest published version, while main refers to the main branch (in-development) version. Readthedocs calls the latest published version stable, would that be clearer? We could also give an alias to main (since it's just the branch name), e.g. dev or nightly (which is often used to imply that thinks will break on this version) even latest? I'm open to any change that makes the names less confusing.

Also, do you think the main option should be added to the docs GUI? I didn't for now since I didn't want to drive users to it, but perhaps it might be useful if we choose an alias like nightly that communicates that it's a version that's not meant to work all the time

[SF-N]

It feels like maybe the version names are confusing? Currently, latest refers to the latest published version, while main refers to the main branch (in-development) version. Readthedocs calls the latest published version stable, would that be clearer? We could also give an alias to main (since it's just the branch name), e.g. dev or nightly (which is often used to imply that thinks will break on this version) even latest? I'm open to any change that makes the names less confusing.

Also, do you think the main option should be added to the docs GUI? I didn't for now since I didn't want to drive users to it, but perhaps it might be useful if we choose an alias like nightly that communicates that it's a version that's not meant to work all the time

Thanks for the explanation, now I understand.
I would leave latest as it is now and add main with an alias (I would prefer dev over nightly).