On Thu, Jun 29, 2017 at 7:44 AM, jan matejek <jmatejek@suse.com> wrote:
fellow pythonistas,
i'd like to propose a new review rule: do not accept new python modules into Factory that are not either singlespec or explicitly versioned.
So "python2-foo" is fine, "python3-foo" is fine, "python-foo" which is not singlespec is rejected.
For apps that have python as a requirement, do not accept anything that requires "python", and look hard on apps that require "python2". (they should require python3 unless the app actually doesn't work with it)
This would apply to *new* packages. Anyone opposed?
I'd like to apply to existing packages too... as in, if you touch a thing that requires python, also make sure that it is versioned. But perhaps this is not a reason for rejection, more like, leave a comment "can you please also do this"?
Thoughts?
m.
Jan, I'm not a pythonista, but I maintain a large python based package - python-plaso. Upstream is working on python 3 compatibility, but it isn't there yet. It is dependant on a couple dozen (or more) python modules: https://build.opensuse.org/package/binary/security:forensics/python-plaso?arch=x86_64&filename=python-plaso-1.5.1-26.3.noarch.rpm&repository=openSUSE_Tumbleweed Note none of the modules are exclusively available as python3. What happens when the first of those dependencies goes python 3 only? Thanks Greg -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org