On 2019-07-09, 12:35 GMT, you wrote:
I believe there might be a misunderstanding, and I think Tom wasn't actually that difficult to understand.
Yes, there is, we are crossing two streams (OH NO!) of communication. You are replying to my discussion with Thomas Bechtold, and arguing about something else.
The discussion is about getting rid of singlespec because (as you rightly pointed out that python 2.x is nearing EOL).
That’s the discussion I have with you.
This was countered with the point that you want to have singlspec so that pypy works, and this raised the eyebrows because the current singlespec approach won't work for pypy.
That is not correct. The current singlespec works with pypy (or at least we have no reasons to believe it doesn’t work), but pypy and pypy3 themselves are broken. When somebody fixes pypy3, we could use all thousands manhours of fixing our current python SPEC files with that as well, and not pour them down the drain as you seem to like to do.
Neither Tom nor I want python 2.x only stack. we want a python 3.x only stack without the insane baggage that singlespec carries behind it (where everything needs to be enabled for all enabled python interpreters).
That is a different discussion I have with Thomas (not Tomáš Chvátal … too many Toms in one discussion!), and what I understood python2-only stack is exactly what he wants, doesn’t it? To have python2-programs in %{_bindir}? Best, Matěj -- https://matej.ceplovi.cz/blog/, Jabber: mcepl@ceplovi.cz GPG Finger: 3C76 A027 CA45 AD70 98B5 BC1D 7920 5802 880B C9D8 When you're happy that cut and paste actually works I think it's a sign you've been using X-Windows for too long. -- from /. discussion on poor integration between KDE and GNOME -- To unsubscribe, e-mail: opensuse-python+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-python+owner@opensuse.org