param Deprecate version.py

Closes https://github.com/holoviz/param/issues/999

There are probably fancier ways to implement that but I think that will do the job.

Jan 03 '25 10:01 maximlt

Looks good to me!

I think the main thing we need to check is that nothing in holoviz is using param.Version before the next version of param is released. That way, this warning should only be seen by non-holoviz users of Version of which I suspect there aren't that many (if any).

Jan 14 '25 12:01 jlstevens

I think the main thing we need to check is that nothing in holoviz is using param.Version before the next version of param is released. That way, this warning should only be seen by non-holoviz users of Version of which I suspect there aren't that many (if any).

True! https://github.com/holoviz/param/issues/999 lists some projects that depend on param/version.py. param/version.py is usually used at both the build and run times, which means that ideally, projects should migrate before we release Param with this deprecation warning. Let's merge it when it's done for the most important ones.

[x] Migrate the main projects (list TBD) using param/version.py to alternative solutions

Jan 14 '25 13:01 maximlt

All the projects that used the version module have been either archived or updated to use another tool. Test failures are unrelated.

Oct 23 '25 12:10 maximlt