]> git.ipfire.org Git - thirdparty/sqlalchemy/sqlalchemy.git/commit
- Adjusted ``setup.py`` file to support the possible future
authorMike Bayer <mike_mp@zzzcomputing.com>
Sat, 22 Mar 2014 21:31:50 +0000 (17:31 -0400)
committerMike Bayer <mike_mp@zzzcomputing.com>
Sat, 22 Mar 2014 21:31:50 +0000 (17:31 -0400)
commitec97911ed915238b4ea1ce51d6f7a77d49790f2b
treeada9947f79f133b1b526d2ef60c24ca1660945dd
parentc464960fddf0c3d2db3acff9f772b057e32bcf67
- Adjusted ``setup.py`` file to support the possible future
removal of the ``setuptools.Feature`` extension from setuptools.
If this keyword isn't present, the setup will still succeed
with setuptools rather than falling back to distutils.  C extension
building can be disabled now also by setting the
DISABLE_SQLALCHEMY_CEXT environment variable.  This variable works
whether or not setuptools is even available. fixes #2986
- using platform.python_implementation() in setup.py to detect CPython.
I've tested this function on OSX and linux on Python 2.6 through 3.4,
including 3.1, 3.2, 3.3.
Unfortunately, on OSX + 3.2 only, it seems to segfault.  I've tried
installing 3.2.5 from the python.org .dmg, building it from source,
and also blew away the whole 3.2 directory, something seems to be wrong
with the "platform" module on that platform only, and there's also no
issue on bugs.python.org; however, I'm going with
it anyway. If someone is using 3.2 on OSX they really should be upgrading.
doc/build/changelog/changelog_08.rst
doc/build/intro.rst
setup.py