Should siibra cache be versioned?

[AhmetNSimsek]

For example, if there is a change in the data of a certain map but not in its name, potentially the user might not get the updated data if it was previously cached locally.

[xgui3783]

my 2c, in order of preference:

• (most favourable) leave things as they are (i.e. cache are not cleared until user specifically calls siibra.cache.clear() . Simplest solution, and easy to debug
• (distant 2nd) tie cache to siibra version. if siibra version increments, invalidate all cache. CON: on new installation of siibra-python, if there was a version increment, the local cache will need to be populated again.

As a user of siibra-python, I would like to be able to control how/when I clear my cache:

• with python interpreter, I would manually call siibra.cache.clear(), and I do not do this often
• in siibra-api, new directories are used for cache for each siibra-api release, effectively "clearing the cache"

IMO, the last thing we want is to have yet one more place, where stale cache breaks our build, or overly zealous cache invalidation results in new configuration to be fetched everytime a new python session starts