On Fri, Jul 8, 2016 at 10:14 AM, Jason Newton
I guess I missed something or d:l:p:Factory now has LEAP on the repo list - too much time between replies for me to remember. But still towards the original point, I think d:l:p:Factory packages should be linked into python3's project so we have a single stable repo for this topic. Further, rather than python3 it should be d:l:p:latest, or stable. The point is latest stable python distribution but actually stable (and self contained) as a repository too. If this is disagreeable, then at least rename/re-purpose d:l:p:Factory to be something more stable sounding.
d:l:p:Factory is not necessarily stable. Well, the Python version is, but Python 3 updates often break existing Python packages. Python 3.5.2, for example, is apparently incompatible with python3-qt5, and will be for some time. So if you install d:l:p:Factory there is a very good chance you will end up with broken packages. And that is only for "patch" level updates, minor version update (3.x) are larger still. Also, KDE and Python 3 are very different things. KDE is a set of libraries and applications built on those libraries. As long as you recompile those applications, it is not that big a deal. Python, on the other hand, is a programming language, and a lot of packages outside of d:l:p3 provide interfaces in that language. For example rpm provides python 3 bindings. If you update from python 3.4 to 3.5 all those packages will break, because they depend on a particular python minor version (so python 3.4 or 3.5). So that would imply update really low-level components like rpm, in which case you might as well be using Tumbleweed, or recompiling these packages for every supported openSUSE version in d:l:p3, which would be a huge maintenance burden especially since they could break on patch-level Python release. Further, this burden would be pushed on to any project that build any python3 package of any sort for LEAP, since if every project doesn't do it then we will end up with a mix of incompatible python packages. So this is simply infeasible in practice. The whole point of differentiating stable release distros from rolling release one is that it is infeasible to make large changes to low-level components in a stable release distro. If you really need updated versions of low-level components like core programming languages, you should either use a rolling release distro or a stand-alone distribution of that language like Anaconda. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org