Bug 1749434

Summary:	enabling devtoolset-6 or devtoolset-8 exports bad PYTHONPATH
Product:	Red Hat Developer Toolset	Reporter:	Piyush Bhoot <pbhoot>
Component:	devtoolset-meta	Assignee:	Marek Polacek <mpolacek>
Status:	CLOSED DUPLICATE	QA Contact:	Martin Cermak <mcermak>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	DTS 8.1 RHEL 7	CC:	jakub, mnewsome, ohudlick, tborcin
Target Milestone:	alpha
Target Release:	9.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2019-09-23 17:21:31 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 Piyush Bhoot 2019-09-05 15:30:37 UTC

Description of problem:

Although the 'devtoolset-x' stuff has nothing to do with python the  enable script exports a PYTHONPATH like this:

/opt/rh/devtoolset-6/root/usr/lib64/python2.7/site-packages:/opt/rh/devtoolset-6/root/usr/lib/python2.7/site-packages


Version-Release number of selected component (if applicable):

devtoolset-6
devtoolset-8

How reproducible:
Always

Steps to Reproduce:
Enable devtoolset scl

Additional info:

PYTHONPATH was introduced in the devtoolset-1.1 and still exists in
devtools-8

The python interpreter takes care of 'its' site directories automatically.
It is common practice to have more than one python version on a machine, very typical a 2.7 and a 3.x version.
So, putting a distinct set of site directories into the static PYTHONPATH is intentional?

Is this intentional?

Comment 3 Marek Polacek 2019-09-23 17:21:31 UTC


*** This bug has been marked as a duplicate of bug 1749445 ***