Bug 1749434 - enabling devtoolset-6 or devtoolset-8 exports bad PYTHONPATH
Summary: enabling devtoolset-6 or devtoolset-8 exports bad PYTHONPATH
Keywords:
Status: CLOSED DUPLICATE of bug 1749445
Alias: None
Product: Red Hat Developer Toolset
Classification: Red Hat
Component: devtoolset-meta
Version: DTS 8.1 RHEL 7
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: alpha
: 9.0
Assignee: Marek Polacek
QA Contact: Martin Cermak
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-09-05 15:30 UTC by Piyush Bhoot
Modified: 2019-09-23 17:21 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-09-23 17:21:31 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

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 ***
Note You need to log in before you can comment on or make changes to this bug.