I have submitted python-tornado4 [1], python-tornado5 [2], and python-tornado6 [3] packages. I know python-tornado4 won't work for that much longer, but it is enabled for backwards-compatibility and older openSUSE releases for now. I have also updated the devel:languages:python project config to prefer python-tornado5. [1] https://build.opensuse.org/request/show/719688 [2] https://build.opensuse.org/request/show/719689 [3] https://build.opensuse.org/request/show/719696 On Mon, Jul 29, 2019 at 5:13 AM Tomas Chvatal <TChvatal@suse.com> wrote:
Todd Rme píše v Ne 28. 07. 2019 v 23:06 -0400:
On Tue, Jul 23, 2019 at 3:40 PM Tomas Chvatal <TChvatal@suse.com> wrote:
Todd Rme píše v Út 23. 07. 2019 v 15:22 -0400:
Current we have Tornado 4 in openSUSE, but it has been unmaintained for more than a year and a half, which is worrisome for a web- facing framework like Tornado. Tornado 5 was released March 2018 and Tornado 6, the current version, was released March 2019.
Unforunately some packages have been slow to update, but we are reaching the point where packages are beginning to drop support for Tornado 4. This leads to a situation where certain packages cannot be installed at the same time.
Should we be using versioned releases of Tornado like we started doing for pytest?
Good question. Your assesment bellow this quite spot on, but keeping it out for readability.
The biggest issue is that tornado4 does not work at all with python 3.8 so one I suppose we should start branching it if it is pain (esp. as the pytest is major pain in the butt and upstream does not care that most devs just write pytest==3.whatever and are done with it).
If the attitude is the same for tornado we should 'multiversion' it as well. If we have chance to leverage the upstreams to fix for latest versions tho it is much much better solution (from your list most of them are supporting 5 so we should shoot for it).
Last time the ONLY blocker we had in distro for tornado5 was saltstack and honestly it took a bit to get it rolling with py3.7 and this time I would rather just sack it.
Cheers
Tom
So there seems to be no objections to this. What would be the best way to proceed? I assume we will have 3 versions, python-tornado4, python-tornad5, and python-tornad6? If so, I see a few ways to proceed:
1. Have a "python-tornado" dummy package that pull in the preferred version, probably python-tornado5. Packages that can't use that (or can only use 5) can specify a version number. 2. Have the preferred version (again probably 5) provide python-tornado, and again let packages that need to specify the version 3. Have all three packages provide "python-tornado", let packages specify which version range they can handle, and let zypper's dependency handler work out what to do. 4. Have nothing provide "python-tornado", have all packages specify which combination they support using the new "or" operator, and again let zypper figure out what to install.
Anyone have any thoughts? I would lean towards 1 myself, since it provides a cleaner update path. Even if zypper's dependency solver works perfectly, it could be confusing to people to get a major downgrade (6 to 5, for example) when installing a new package. Anyone have any thoughts?
Well one note is that we can't keep tornado3, we are already prepping the 3.8 that won't work with it anyway so I would absolutely ignore that one.
For the options above option 1 and 3 sound the most pleasing. The difference being that for option 3 you need prjconf adjustment and do not need metapackage.
I try to avoid metapackages and stick with prjconf but both of the solutions achieve the same results for zypper.
Cheers
Tom
-- To unsubscribe, e-mail: opensuse-python+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-python+owner@opensuse.org