Bug 1410426 - python-sqlalchemy puts library code in wrong location causing import to fail
Summary: python-sqlalchemy puts library code in wrong location causing import to fail
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Fedora EPEL
Classification: Fedora
Component: python-sqlalchemy0.8
Version: el6
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Fedora Infrastructure SIG
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-01-05 13:17 UTC by patrick.hirt
Modified: 2017-07-04 00:48 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-07-04 00:48:52 UTC
Type: Bug


Attachments (Terms of Use)

Description patrick.hirt 2017-01-05 13:17:05 UTC
Description of problem:

The actual sqlalchemy code is put in site-packages/SQLAlchemy-0.8.2-py2.6-linux-x86_64.egg/sqlalchemy, when it should be in site-packages/sqlalchemy for it to be picked up by Python's site.py at interpreter startup. The jinja2 rpm has the same problem.


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

python-sqlalchemy0.8-0.8.2-4.el6.src.rpm

How reproducible:
Every time

Steps to Reproduce:
1. Install python-sqlalchemy on RHEL6
2. Start a python interpreter
3. Type "import sqlalchemy" and watch it fail

Actual results:
Import does not work


Expected results:
Import works


Additional info:

The workaround for this is obviously 
import sys
sys.path.append('/usr/lib64/python2.6/site-packages/SQLAlchemy-0.8.2-py2.6-linux-x86_64.egg') 
but that really shouldn't be necessary.

Comment 1 Alan Pevec 2017-07-04 00:48:52 UTC
This is intentional in parallel installable packages, otherwise they would conflict with base RHEL provided libraries.
README.Fedora in the package[1] explains how to use it.


[1] http://pkgs.fedoraproject.org/cgit/rpms/python-sqlalchemy0.8.git/tree/README.Fedora?h=el6


Note You need to log in before you can comment on or make changes to this bug.