Mailinglist Archive: opensuse-bugs (4790 mails)

< Previous Next >
[Bug 1046990] New: python3-devel should also require python3
  • From: bugzilla_noreply@xxxxxxxxxx
  • Date: Mon, 03 Jul 2017 06:58:19 +0000
  • Message-id: <bug-1046990-21960@http.bugzilla.opensuse.org/>
http://bugzilla.opensuse.org/show_bug.cgi?id=1046990


Bug ID: 1046990
Summary: python3-devel should also require python3
Classification: openSUSE
Product: openSUSE Tumbleweed
Version: Current
Hardware: Other
OS: Other
Status: NEW
Severity: Normal
Priority: P5 - None
Component: Development
Assignee: bnc-team-screening@xxxxxxxxxxxxxxxxxxxxxx
Reporter: markos.chandras@xxxxxxxx
QA Contact: qa-bugs@xxxxxxx
Found By: ---
Blocker: ---

Hi,

We are facing an annoying issue with python3 packages. There are several
openstack projects requiring python3-devel. However, this package only requires
the 'python3-base' in TW and Leap. This package though doesn't have the XML
module which project expect to find when they pull python3-devel. The XML
module is located in the python3 package.

We have a very strange situation in openSUSE where the python3 interpreter is
present in the python3-base package whilst the python3 package contains other
modules. As such, we need to do all sorts of things in order to have a
reasonably python3 core stack in openSUSE. Can this situation be improved
somehow?

The python3 package is also described as 'Python3 interpreter' which is
misleading.

I suggest to modify python3-devel to require the python3 package as well. Then
I would suggest to possibly merge python3 and python3-base since the former has
some core modules in it which seems like 95% of the python3 installations would
want them. Plus, I would expect the python3 interpreter to be in python3 not
python3-base so perhaps that's another reason to merge them

The situation is also similar in python2 with the xml module being in its own
package but I guess it's too late to deal with it now.

Thank you

--
You are receiving this mail because:
You are on the CC list for the bug.
< Previous Next >
Follow Ups