# The form data below was edited by perforce # 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. May also provide # additional information such as the earliest release # in which a bug is known to exist. # # Component: Projects may use this optional field to indicate # which component of the project a givenjob is associated # with. # # For the SDP, the list of components is defined in: # //guest/perforce_software/sdp/tools/components.txt # # Type: Type of job [Bug/Feature]. Required. # # Release: Release in which job is intended to be fixed. Job: job000430 Status: open Project: perforce_software-p4python Severity: C ReportedBy: joel_kovisto ReportedDate: 2015/12/29 17:28:07 ModifiedBy: perforce ModifiedDate: 2019/02/19 10:51:28 OwnedBy: joel_kovisto Description: Help P4Python find correct SSL library. Customer obtained P4Python from https://pypi.python.org/pypi/P4Python Got this error when running on Mac/Yosemite. File "/Users/twick/sDev/tableau-tools/pipeline/common_dep/file_utils.py", line 11, in <module> from perforce import P4Conn File "/Users/twick/.tabvenvs/server-dev-b9be31fe483ffffa5a742dfb57832590/tube/lib/python3.4/site-packages/perforce/__init__.py", line 20, in <module> from P4 import P4, P4Exception, Map File "/Users/twick/.tabvenvs/server-dev-b9be31fe483ffffa5a742dfb57832590/tube/lib/python3.4/site-packages/P4.py", line 410, in <module> import P4API ImportError: dlopen(/Users/twick/.tabvenvs/server-dev-b9be31fe483ffffa5a742dfb57832590/tube/lib/python3.4/site-packages/P4API.so, 2): Library not loaded: /opt/local/lib/libssl.1.0.0.dylib Referenced from: /Users/twick/.tabvenvs/server-dev-b9be31fe483ffffa5a742dfb57832590/tube/lib/python3.4/site-packages/P4API.so Reason: image not found Suggest bundling libssl in the wheels (.whl files) they're publishing here, so that this problem can be avoided. DevNotes: Type: Feature