Bug 560622

Summary: pypar incompatible with openmpi, not using environment modules.
Product: [Fedora] Fedora Reporter: Cong Ma <frigoris.ma>
Component: pyparAssignee: Susi Lehtola <susi.lehtola>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: low    
Version: 12CC: susi.lehtola
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2010-02-01 13:13:14 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Cong Ma 2010-02-01 12:18:28 UTC
Description of problem:
The version of pypar shipped by Fedora is unusable without manually tweaking the PYTHONPATH shell variable or sys.path. In Python, the statement "import pypar" will raise ImportError.

Version-Release number of selected component (if applicable):
2.1.4_94-1.fc12

How reproducible:
Always

Steps to Reproduce:
1. Load OpenMPI modules in the current shell: module load openmpi-`uname -i`
2. Try to import pypar in Python.
3. Watch things fail.
  
Actual results:
Python can't find module pypar.

Expected results:
Python should have been able to import pypar.

Additional info:
I think this should be easily fixed by adding a module file in /etc/modulefiles/ that loads the module OpenMPI module for the current architecture then prepend PYTHONPATH with /usr/lib/python2.6/site-packages/openmpi

Comment 1 Cong Ma 2010-02-01 12:22:57 UTC
Just another note, please update the package URL to refer to pypar's new website at Google Code: http://code.google.com/p/pypar/

Comment 2 Susi Lehtola 2010-02-01 13:13:14 UTC
This is caused by the environment module of Open MPI not following the MPI guidelines fully, the PYTHONPATH prepend should exist in the openmpi module.

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