Not really. Python 2 is dead. Jython 2 gets minimal fixes until Jython 3 can replace it, which of course I’d rather be doing.
As discussed on related issues/PRs, we have found treating Jython or Java as a platform, OS or system, on a par with Windows or Linux, to be problematic in practice. Modules ask “is it Windows” and then assume a Unix-like file system. This breaks Jython on Windows.
java_ver alongside win32_ver is part of the same philosophy.
I’m content with the change in Python 3 stdlib because I can see no impact in Jython 2, and I currently think we don’t want it for Jython 3.
platform.implementation and platform.python_version should tell an application it can do Java specific things, then it can ask Java about its version if it needs to.
I have little to say about depreciation speed as I cannot be sure no one is using it. No one running Jython 3 is using it. 