# The form data below was edited by tom_tyler
# Perforce Workshop Jobs
#
#  Job:           The job name. 'new' generates a sequenced job number.
#
#  Status:        Job status; required field.  There is no enforced or
#                 promoted workflow for transition of jobs from one
#                 status to another, just a set of job status values
#                 for users to apply as they see fit.  Possible values:
#
#                 open - Issue is available to be worked on.
#
#                 inprogress - Active development is in progress.
#
#                 blocked - Issue cannot be implemented for some reason.
#
#                 fixed - Fixed, optional status to use before closed.
#                 
#                 closed - Issue has been dealt with definitively.
#
#                 punted - Decision made not to address the issue,
#                    possibly not ever.
#
#                 suspended - Decision made not to address the issue
#                    in the immediate future, but noting that it may
#                    have some merit and may be revisited later.
#
#                 duplicate - Duplicate of another issue that.
#
#                 obsolete - The need behind the request has become
#                    overcome by events.
#
#  Project:       The project this job is for. Required.
#
#  Severity:      [A/B/C] (A is highest)  Required.
#
#  ReportedBy     The user who created the job. Can be changed.
#
#  ReportedDate:  The date the job was created.  Automatic.
#
#  ModifiedBy:    The user who last modified this job. Automatic.
#
#  ModifiedDate:  The date this job was last modified. Automatic.
#
#  OwnedBy:       The owner, responsible for doing the job. Optional.
#
#  Description:   Description of the job.  Required.
#
#  DevNotes:      Developer's comments.  Optional.  Can be used to
#                 explain a status, e.g. for blocked, punted,
#                 obsolete or duplicate jobs.
#
# Component:      Larger projects may use this optional field to
#                 indicate which component of the project a given
#                 job is associated with.
#
#  Type:	  Type of job [Bug/Feature].  Required.

Job:	SDP-238

Status:	open

Project:	perforce-software-sdp

Severity:	C

ReportedBy:	perforce

ReportedDate:	2017/07/27 11:42:30

ModifiedBy:	tom_tyler

ModifiedDate:	2017/07/27 11:42:30

OwnedBy:	perforce

Description:
	Enhance SDP Python install script so python in PATH is the SDP python3.
	
	After a successful Perl compile, we want to just do:
	
	cd /p4/common/python/bin
	ln -s python3 python
	
	This won't affect the machine-installed Python. It will only affects users
	that have /p4/common/python/bin in their PATH ahead of /bin or /usr/bin,
	typically just the 'perforce' user.  So it's completely safe as far as not
	affecting the root user or non-perforce things.
	
	It would affect any other automation running as the perforce user that has
	a "path deferring" shebang line of "#!/bin/env python".  That includes
	several SDP scripts, which have a path-deffring shebang line.
	
	Any Python automation running as perforce that has an explicit shebang line,
	e.g. "#!/usr/bin/python", won't be affected.
	
	This strikes the right balance between having a strong preference for the
	python/p4python that we have taken the time to install (if we're using
	this script), but without intrusively affecting the existing environment.

Component:	env

Type:	Feature