Re: [Sqlalchemy-tickets] [sqlalchemy] #2806: setup.py misbehaves with respect to the location of sh
Brought to you by:
zzzeek
|
From: sqlalchemy <mi...@zz...> - 2013-08-19 19:26:35
|
#2806: setup.py misbehaves with respect to the location of shared objects
-----------------------------------+------------------------------------
Reporter: assarbad | Owner: zzzeek
Type: defect | Status: closed
Priority: medium | Milestone:
Component: cextensions | Severity: no triage selected yet
Resolution: wontfix | Keywords:
Progress State: completed/closed |
-----------------------------------+------------------------------------
Comment (by zzzeek):
The only function we call setup.py is setup(). There are no options to
control where .so files go or how to respond to $PYTHONHOME, chroot
environments or anything else like that (See
http://docs.python.org/2/distutils/apiref.html#distutils.core.setup for
core setup() and http://pythonhosted.org/distribute/setuptools.html#new-
and-changed-setup-keywords for those added by setuptools). We are
calling it in the identical form as other more widely used packages such
as psycopg2, giving it a list of ext_modules, that's all it accepts.
If setup() is doing the wrong thing based on your environment, I'd assume
the issue is with setuptools. I have no knowledge of what $PYTHONHOME
even does in terms of setuptools, and based on my experience I'd guess it
does not what you expect - $PYTHONHOME is not a variable that is commonly
used these days, standard practice is to use virtualenv for local Python
installations. So from all indications this certainly seems like a usage
issue with setuptools overall and the folks on disutils-sig should have
definitive information on how setuptools works - I'm only a user of it.
If people with knowledge of setuptools can point to an actual bug in
SQLAlchemy's code, reopen this ticket and we will fix it.
--
Ticket URL: <http://www.sqlalchemy.org/trac/ticket/2806#comment:3>
sqlalchemy <http://www.sqlalchemy.org/>
The Database Toolkit for Python
|