Worth having any special-cases for Google CoLab?

[patcon]

Google CoLab has a directory at /content/sample_data, and everywhere else is very non-obvious or hidden.

How to detect: https://stackoverflow.com/a/53586419

[gaborbernat]

Colab runs a standard Linux VM, so the Unix/XDG backend already returns correct paths (~/.local/share, ~/.config, ~/.cache, etc.). These directories work normally in a Colab session.

The /content/sample_data path mentioned is where Colab places sample notebooks — it's not an application data directory convention. Unlike Android, which has a genuinely different filesystem layout (/data/data/<pkg>/ namespacing) requiring its own backend, Colab follows standard Linux conventions with no platform-specific directory guidance.

Without a concrete use case where the current Unix paths break or behave unexpectedly in Colab, there's nothing to special-case here. Closing as not planned.

[patcon]

K thanks for considering 🙏🏻