]> 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:47:07 +0000 (17:47 -0400)
commit0dddcf924eada6cb090da0f11ddb53b8a9487bab
treeb0a0ace966f174205ab61b522454a5e77cc5510e
parentcb51fe3ef894f279537f6de91af23034da226f62
- 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.
- adjusted the logic for platform_implementation(), apparently "platform"
is there in python 2.5, so we are doing a version check.
Conflicts:
doc/build/intro.rst
setup.py
doc/build/changelog/changelog_08.rst
doc/build/intro.rst
setup.py