Hey,
I don't want to support end of life versions.
Just knew about Suse using it and wanted to make it transparent.
The last days I investigated dependency handling and I would even propose requiring Python 3.9 for 5.0, as we have
matplotlib as dependency and its current version requires it:
https://pypi.org/project/matplotlib/
Besides Python 3.8 will reach end of life before scheduled 5.0 release as well (release January 2025, end of life
October 2024):
https://devguide.python.org/versions/
Best
Gerald
On 3/23/24 11:42, Mathias Behrle wrote:
* Gerald Wiese: " Re: [Health-dev] Improve SYSINFO command" (Sat, 23 Mar 2024
11:24:48 +0100):
About Suse: My point was rather that importing a library introduced in 3.8
would break it if still using 3.6 - no matter if you know the version already.
But if it's only used for 5.0 and we have openSUSE with Python3.11 by then,
seems fine :)
I think it is not enough to narrow the view on OpenSUSE. If you want to
support Python3.6, it shouldn't break with 3.6.
Best
Mathias
On 3/23/24 10:27, Axel Braun wrote:
Hi Gerald,
Am 22. März 2024 18:43:41 GMT+00:00 schrieb Gerald Wiese
<wi...@gnuhealth.org>:
Hi,
I was investigating how to properly set the desired environment variables
GNUHEALTH_VERSION & TRYTON_VERSION for the SYSINFO command.
.....
Not sure what that would mean for openSUSE.
During the build/Packaging process on OBS we determine the GH and trytond
Version. As every change in dependency triggers a rebuild, the information
is always accurate.
does that explain?
Kind regards
Axel
