Re: [Sqlalchemy-tickets] [sqlalchemy] #2806: setup.py misbehaves with respect to the location of shared objects

[sqlalchemy <mi...@zz...>]

#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  |
-----------------------------------+------------------------------------
Changes (by zzzeek):

 * status:  new => closed
 * resolution:   => wontfix
 * status_field:  awaiting triage => completed/closed


Comment:

 SQLAlchemy's setup.py uses a system called "setuptools" to build its
 software, which itself builds upon Python's standard build system
 "distutils".  "setuptools" itself is a de-facto standard in Python as well
 and is used by a large portion of Python projects.

 All of the behaviors you're observing here are not specific to SQLAlchemy
 and are instead part of the behaviors of distutils and setuptools, there's
 nothing in SQLAlchemy itself that impacts the behavior of where .so files
 go or anything like that.   SQLAlchemy does have some C extensions, which
 might not be the case for other packages you are comparing to, but for
 comparison, try installing a package like psycopg2 or lxml which also
 generates .so files and compare the behavior there.

 This is a pretty fundamental Python install issue so I'd suggest asking on
 a general group such as comp.lang.python, or if you want to talk to
 distutils developers you can ask on
 http://www.python.org/community/sigs/current/distutils-sig/, they might be
 able to shed light on the mechanics of your issue here.

--
Ticket URL: <http://www.sqlalchemy.org/trac/ticket/2806#comment:1>
sqlalchemy <http://www.sqlalchemy.org/>
The Database Toolkit for Python