summaryrefslogtreecommitdiff
path: root/setup.py
Commit message (Collapse)AuthorAgeFilesLines
* - bump minimum python version to 2.7Mike Bayer2017-03-101-3/+2
| | | | | | - add placeholder 1.2 release documentation, update intro numbers Change-Id: I9f9969cbb9e95c2f750a5c16798e92c35a5ef6cf
* - further changes to avoid pytest warningsMike Bayer2017-01-171-2/+2
| | | | Change-Id: Ia83a996ff97a6ba54a0666a32241e570f3852ab4
* update pytest good practices link in PyTest classMark Sandan2016-06-161-2/+4
| | | | | Change-Id: Ie96edd05e962663e9ddeeda85b24858caabd3bfd Pull-request: https://github.com/zzzeek/sqlalchemy/pull/262
* - add a new qualifier "native" vs. "dbapi" unicode to avoidMike Bayer2016-01-241-0/+10
| | | | | | profiling problems here - add extras_require to setup.py for the most common DBAPIs - rework tox.ini to use extras, specify a test matrix built in
* Tell Wheel to generate platform and interpreter specific wheelspr/194Donald Stufft2015-08-131-1/+16
| | | | | | | By telling wheel that we have extension modules, even though we have none, wheel will create a Wheel which is platform and interpreter specific. This will ensure that the pure Python wheels on PyPy do not trigger installs on CPython without the C speedups.
* - we can again use setuptools.find_packages since we require setuptoolsMike Bayer2015-08-131-25/+13
| | | | - clean up other things we aren't using anymore
* - remove "distutils-only" mode, use setuptools onlyMike Bayer2015-07-241-60/+62
| | | | | | - add first-class "pytest" runner to setup.py, fixes #3489 - remove references to setuptools Feature and mark that "--without-cextensions" is removed, fixes #3500
* - have python setup.py test use xdist with -qMike Bayer2014-08-081-1/+1
|
* fixed style to conform to PEP8Brian Jarrett2014-07-101-37/+42
|
* - Fixed bug where "python setup.py test" wasn't calling intoMike Bayer2014-07-091-1/+1
| | | | | distutils appropriately, and errors would be emitted at the end of the test suite.
* - we aren't supporting py2.5 so just simplify this import for platform, re: ↵Mike Bayer2014-03-221-9/+3
| | | | #2986
* - Adjusted ``setup.py`` file to support the possible futureMike Bayer2014-03-221-9/+31
| | | | | | | | | | | | | | | | | | 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.
* - Support has been added for pytest to run tests. This runnerMike Bayer2014-03-031-2/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | is currently being supported in addition to nose, and will likely be preferred to nose going forward. The nose plugin system used by SQLAlchemy has been split out so that it works under pytest as well. There are no plans to drop support for nose at the moment and we hope that the test suite itself can continue to remain as agnostic of testing platform as possible. See the file README.unittests.rst for updated information on running tests with pytest. The test plugin system has also been enhanced to support running tests against mutiple database URLs at once, by specifying the ``--db`` and/or ``--dburi`` flags multiple times. This does not run the entire test suite for each database, but instead allows test cases that are specific to certain backends make use of that backend as the test is run. When using pytest as the test runner, the system will also run specific test suites multiple times, once for each database, particularly those tests within the "dialect suite". The plan is that the enhanced system will also be used by Alembic, and allow Alembic to run migration operation tests against multiple backends in one run, including third-party backends not included within Alembic itself. Third party dialects and extensions are also encouraged to standardize on SQLAlchemy's test suite as a basis; see the file README.dialects.rst for background on building out from SQLAlchemy's test platform.
* - The C extensions are ported to Python 3 and will build underMike Bayer2013-07-261-1/+1
| | | | any supported CPython 2 or 3 environment. [ticket:2161]
* - replace most explicitly-named test objects called "Mock..." withMike Bayer2013-06-301-2/+1
| | | | | | | | | | | | actual mock objects from the mock library. I'd like to use mock for new tests so we might as well use it in obvious places. - use unittest.mock in py3.3 - changelog - add a note to README.unittests - add tests_require in setup.py - have tests import from sqlalchemy.testing.mock - apply usage of mock to one of the event tests. we can be using this approach all over the place.
* don't need 2to3Mike Bayer2013-04-281-52/+20
|
* - revert mistaken checkinMike Bayer2013-02-061-1/+1
|
* - need autoincrement hereMike Bayer2013-02-061-1/+1
|
* - revert the "basedir" thing - running setup.py from the currdir is ↵Mike Bayer2012-09-291-10/+4
| | | | | | unfortunately part of the distutils docs (http://docs.python.org/install/index.html#platform-variations)
* - enhance setup.py to support being run from outside the current directory. ↵Mike Bayer2012-09-291-14/+20
| | | | | | hopefully there's no gotchas with this on other platforms.
* - add new C extension "utils", so far includes distill_paramsMike Bayer2012-08-071-1/+3
| | | | | - repair test_processors which wasn't hitting the python functions - add another suite to test_processors that does distill_params
* trailing whitespace bonanzaMike Bayer2012-07-281-3/+3
|
* unmonkeypatch the 2to3 preprocessor so we don't disturb subsequent runsPhilip Jenvey2012-03-021-7/+21
| | | | | patch from mcdonc fixes #2421
* modernize the READMEMike Bayer2012-01-261-126/+9
|
* add supported implementationsMike Bayer2011-12-031-0/+3
|
* - Added a workaround for Python bug 7511 whereMike Bayer2011-06-051-5/+7
| | | | | | failure of C extension build does not raise an appropriate exception on Windows 64 bit + VC express [ticket:2184]
* this will also move back to prod/stableMike Bayer2011-05-201-1/+1
|
* might as well explicitly disable the cext on Jython tooPhilip Jenvey2011-04-221-1/+2
|
* - rework setup.py script to work with:Mike Bayer2011-04-171-32/+61
| | | | | | | | | | - Python 3 - Python 3 builds if Distribute isn't installed - rework install documentation again - raise if doc build with mako < 0.4.1 - Python 3.1 builds force doctest parse but then fails due to distribute bug, so remove usage of backslash \\ in hybrid.py docstring - put in the latest ez_setup.py
* explicitly disable the cextension on Python 3 until it's updated for itPhilip Jenvey2011-04-131-2/+4
|
* enable the cextension by default, falling back to pure python when thePhilip Jenvey2011-04-131-162/+211
| | | | | extension fails to compile fixes #2129
* minor cleanupPhilip Jenvey2011-04-131-40/+33
|
* 0.7 will be beta classifier to startMike Bayer2011-02-121-1/+1
|
* - whitespace removal bonanzaMike Bayer2011-01-021-2/+2
|
* - set sqla_nose as the setup.py test runner - works !Mike Bayer2010-11-161-5/+1
|
* first step of [ticket:1949], remove the setuptools aspectMike Bayer2010-11-151-6/+1
| | | | of the plugin, move it to test/bootstrap
* - the NoseSQLAlchemyPlugin has been moved to aMike Bayer2010-10-171-6/+6
| | | | | | | | | | new package "sqlalchemy_nose" which installs along with "sqlalchemy". This so that the "nosetests" script works as always but also allows the --with-coverage option to turn on coverage before SQLAlchemy modules are imported, allowing coverage to work correctly. - added some new ignores
* hey lets pep-8 the setup.py file.Mike Bayer2010-09-151-19/+117
|
* mergeMike Bayer2010-04-231-3/+0
|\
| * yikes, no more svn version here...Mike Bayer2010-04-201-3/+0
| |
* | prod/stableMike Bayer2010-04-231-1/+1
|/
* the mercurial extension seems to not work in py3k and also I don'tMike Bayer2010-03-071-1/+5
| | | | | like its usage during build/install. going with the manual approach for the moment.
* use setuptools_hg to auto-discover the same way we did with SVN.Mike Bayer2010-03-071-0/+1
| | | | Thanks *much* to Jannis Leidel for the suggestion/creation !
* use a flag to build cextensions (thanks again to Genshi for the tip)Mike Bayer2010-03-051-10/+27
|
* require nose .11 to support first_package_wins flagMike Bayer2010-03-011-1/+1
|
* add a noteMike Bayer2010-02-141-1/+10
|
* - Added an optional C extension to speed up the sql layer byGaëtan de Menten2010-02-131-2/+10
| | | | | | | | | | | | | | | reimplementing the highest impact functions. The actual speedups will depend heavily on your DBAPI and the mix of datatypes used in your tables, and can vary from a 50% improvement to more than 200%. It also provides a modest (~20%) indirect improvement to ORM speed for large queries. Note that it is *not* built/installed by default. See README for installation instructions. - The most common result processors conversion function were moved to the new "processors" module. Dialect authors are encouraged to use those functions whenever they correspond to their needs instead of implementing custom ones.
* - Improved the installation/test setup regarding Python 3,Mike Bayer2010-02-131-2/+16
| | | | | | now that Distribute runs on Py3k. distribute_setup.py is now included. See README.py3k for Python 3 installation/ testing instructions.
* - added py3k and "OS Independent" classifiersMike Bayer2009-11-011-0/+2
|
* merge 0.6 series to trunk.Mike Bayer2009-08-061-2/+3
|
View Lorry Controller Status