On 20. 05. 20 21:38, Miroslav Suchý wrote:
Dne 19. 05. 20 v 14:03 Richard Shaw napsal(a):
> Because Qt 5.13.x / PySide2 5.13.x is NOT compatible with Python 3.8. But instead of
asking ourselves, "should we push
> in the VERY latest Python and hope it's ok?", we just patch the build system
to accept it anyway and hope for the best.
>
> Qt (et all) is a pretty organized upstream, so when asked about Python 3.8 support in
5.13.x, they said, "Nope. Wait for
> 5.14.x."
>
BTW this is scholar example of use-case for Modularity.
I disagree: This is a scholar misconception about Modularity.
Modularity doesn't have parallel installability, hence (as Smooge says in this
thread) you have a big problem:
- you either end up in an impossible "choose the stack" situation
- or you need to rebuild every Python package in every Python stream
- that has the maintenance issue
- you have the same problem for PySide in the 3.8 stream as you had before
- or you can workaround Modularity design by packaging each Python stack as a
different module with namespaced PRM packages (and components) -- hence you get
all the usability problems and maintainability problems of Modularity with no
added value
We could have parallel installable multiple Python version stacks w/out
Modularity just fine. The "only little problem" is we hardly have the enough
maintainers to maintain the 3k+ existing Python packages.
--
Miro Hrončok
--
Phone: +420777974800
IRC: mhroncok