Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Bug 1317532

Summary: [RFE] add dependency of python-devel on python-setuptools
Product: Red Hat Enterprise Linux 7 Reporter: Irina Gulina <igulina>
Component: pythonAssignee: Python Maintainers <python-maint>
Status: CLOSED NOTABUG QA Contact: BaseOS QE - Apps <qe-baseos-apps>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 7.2CC: cstratak, mkovacik, pviktori
Target Milestone: rcKeywords: FutureFeature
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-03-14 14:42:36 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Irina Gulina 2016-03-14 13:31:44 UTC
Description of problem:
python-setuptools is not installed together with python-devel

Version-Release number of selected component (if applicable):
>> rpm -qa '*setuptools*'
python-setuptools-0.9.8-4.el7.noarch
>>rpm -qa '*python-devel*'
python-devel-2.7.5-34.el7.x86_64
>> rpm -q --whatrequires python-setuptools
no package requires python-setuptools


How reproducible:
always

Steps to Reproduce:
1. yum install python-devel

Actual results:
python-setuptools is not installed

Expected results:
python-setuptools is installed

Additional info:

Comment 2 Charalampos Stratakis 2016-03-14 14:03:56 UTC
What is the actual problem? Why would python-devel need python-setuptools?

Comment 3 mkovacik 2016-03-14 14:31:36 UTC
(In reply to Charalampos Stratakis from comment #2)
> What is the actual problem? Why would python-devel need python-setuptools?

To create a python extension one installs python-devel to pull-in headers and sources of python.
However, to actually install and package the extension one still needs python-setuptools.
This BZ was suggested by me actually to enhance that workflow.
Maybe there could be a python development group that would require both the packages as dependencies instead?

Comment 4 Petr Viktorin (pviktori) 2016-03-14 14:42:36 UTC
Setuptools are quite useful, and I'd recommend them in most cases, but they're not the only way to build Python extensions. For example the "distutils" module can be used as well, as can alternative buildsystems like waf.
Also, python-devel is useful for other things than extensions, for example to embed Python in C programs.

The right thing to do for your package is to BuildRequire both python-devel and python-setuptools.

Thanks for trying to enhance the workflow, however!