django/tests/requirements/base.txt

bcrypt
docutils
jinja2 >= 2.7
# move to py2.txt when dropping Python 3.2
mock
numpy
Pillow
PyYAML
pytz > dev
selenium
sqlparse
Fixed #19196 -- Added test/requirements 2013-07-01 13:58:04 -04:00			`bcrypt`
			`docutils`
[1.8.x] Fixed #25056 -- Documented minimum version of jinja2 for testing. Backport of ca58181bac5366d3a1fb44e1b49fe9e365095138 from master 2015-07-03 08:20:53 -04:00			`jinja2 >= 2.7`
Fixed #23289 -- Added mock as a test dependency. 2014-11-29 11:45:06 -05:00			`# move to py2.txt when dropping Python 3.2`
			`mock`
Fixed #21538 -- Added numpy to test/requirements/base.txt Thanks Tim Graham for the report 2013-12-02 17:21:48 +00:00			`numpy`
Fixed #19196 -- Added test/requirements 2013-07-01 13:58:04 -04:00			`Pillow`
			`PyYAML`
Fixed #21032 -- pip 1.4 can't install pytz. 2013-09-06 22:11:55 -05:00			`pytz > dev`
Fixed #19196 -- Added test/requirements 2013-07-01 13:58:04 -04:00			`selenium`
Fixed #3214 -- Stopped parsing SQL with regex. Avoided introducing a new regex-based SQL splitter in the migrations framework, before we're bound by backwards compatibility. Adapted this change to the legacy "initial SQL data" feature, even though it's already deprecated, in order to facilitate the transition to migrations. sqlparse becomes mandatory for RunSQL on some databases (all but PostgreSQL). There's no API to provide a single statement and tell Django not to attempt splitting. Since we have a more robust splitting implementation, that seems like a good tradeoff. It's easier to add a new keyword argument later if necessary than to remove one. Many people contributed to both tickets, thank you all, and especially Claude for the review. Refs #22401. 2014-04-26 10:22:48 +02:00			`sqlparse`