Am 31.01.26 um 15:39 schrieb Tomas Volf:
The difference is that currently you get a warning during building the profile and (presumably) evaluate its validity and act if necessary. If the conflict will be hidden inside a package(s), the user gets no useful feedback.
I got you: Today, if the packager creates such a conflict, the user gets a warning.
IMHO it's a error if a package includes different versions of the same python modules as this is bound to cause issues.
-- Regards Hartmut Goebel | Hartmut Goebel |[email protected] | |www.crazy-compilers.com | compilers which you thought are impossible |
