0
0
mirror of https://github.com/wagtail/wagtail.git synced 2024-11-25 13:10:14 +01:00
wagtail/tox.ini

71 lines
2.5 KiB
INI
Raw Normal View History

2015-04-03 15:38:08 +02:00
[tox]
skipsdist = True
usedevelop = True
envlist = py{34,35,36}-dj111-{sqlite,postgres,mysql,mssql}-{elasticsearch5,elasticsearch2,elasticsearch,noelasticsearch},
2015-04-03 15:38:08 +02:00
[flake8]
# D100: Missing docstring in public module
# D101: Missing docstring in public class
# D102: Missing docstring in public method
# D103: Missing docstring in public function
# D105: Missing docstring in magic method
# D200: One-line docstring should fit on one line with quotes
# D202: No blank lines allowed after function docstring
# D204: 1 blank line required after docstring
# D205: 1 blank line required between summary line and description
# D209: Multi-line docstring cloasing quotes should be on a separate line
# D400: First line should end with a period
# D401: First line should be in imperative mood
# E303: Too many blank lines
# E501: Line too long
# N805: First argument of a method should be named 'self'
# N806: Variable in function should be lowercase
ignore = D100,D101,D102,D103,D105,D200,D202,D204,D205,D209,D400,D401,E303,E501,N805,N806
2015-04-03 15:38:08 +02:00
[testenv]
install_command = pip install -e ".[testing]" -U {opts} {packages}
commands =
elasticsearch: coverage run runtests.py wagtail.wagtailsearch wagtail.wagtaildocs wagtail.wagtailimages --elasticsearch
Elasticsearch 2 support (#2573) * Created Elasticsearch 2 backend * Added tests for Elasticsearch 2 backend * Split models up into different indices pages, images and documents are now in separate indices * Prefix fields of child models to prevent mapping clashes * Replaced index_analyzer with analyzer/search_analyzer index_analyzer has been removed in Elasticsearch 2.0 https://www.elastic.co/guide/en/elasticsearch/reference/current/breaking_20_mapping_changes.html#_analyzer_mappings There's no indication in Elasticsearch's docs that this wouldn't work on Elasticsearch 1.x. However, we found that the new configuration isn't reliable on Elasticsearch 1.6 and below (causes the test_query_analyzer test to fail randomly). * Implemented new way of representing content types in search index Instead of using a long string of model names that is queried using a "prefix" query, we instead use a multi-value string field and query it using a simple "match" query. The only reason why this isn't implemented in the Elasticsearch 1.x backend yet is backwards compatibility * Added another child model of SearchTest with clashing field mapping This checks that the namespacing of fields on child models is working properly (if it doesn't the update_index tests will fail) * Added tests for get_model_root function * fixup! Added tests for get_model_root function * Docs updates for Elasticsearch 2 support Also tweak examples to use elasticsearch2 backend by default * Test against Elasticsearch 2 on travis
2016-05-06 12:23:31 +02:00
elasticsearch2: coverage run runtests.py wagtail.wagtailsearch wagtail.wagtaildocs wagtail.wagtailimages --elasticsearch2
2016-11-08 12:17:26 +01:00
elasticsearch5: coverage run runtests.py wagtail.wagtailsearch wagtail.wagtaildocs wagtail.wagtailimages --elasticsearch5
noelasticsearch: coverage run runtests.py
2015-04-03 15:38:08 +02:00
basepython =
py34: python3.4
2015-09-16 05:50:12 +02:00
py35: python3.5
2017-02-28 12:38:57 +01:00
py36: python3.6
2015-04-03 15:38:08 +02:00
deps =
2015-04-10 05:44:41 +02:00
django-sendfile==0.3.6
Embedly
dj111: Django>=1.11b1,<2.0
dj111-mssql: django-pyodbc-azure==1.11.0.0
2015-04-03 15:38:08 +02:00
postgres: psycopg2>=2.6
mysql: mysqlclient==1.3.6
elasticsearch: elasticsearch>=1,<2
Elasticsearch 2 support (#2573) * Created Elasticsearch 2 backend * Added tests for Elasticsearch 2 backend * Split models up into different indices pages, images and documents are now in separate indices * Prefix fields of child models to prevent mapping clashes * Replaced index_analyzer with analyzer/search_analyzer index_analyzer has been removed in Elasticsearch 2.0 https://www.elastic.co/guide/en/elasticsearch/reference/current/breaking_20_mapping_changes.html#_analyzer_mappings There's no indication in Elasticsearch's docs that this wouldn't work on Elasticsearch 1.x. However, we found that the new configuration isn't reliable on Elasticsearch 1.6 and below (causes the test_query_analyzer test to fail randomly). * Implemented new way of representing content types in search index Instead of using a long string of model names that is queried using a "prefix" query, we instead use a multi-value string field and query it using a simple "match" query. The only reason why this isn't implemented in the Elasticsearch 1.x backend yet is backwards compatibility * Added another child model of SearchTest with clashing field mapping This checks that the namespacing of fields on child models is working properly (if it doesn't the update_index tests will fail) * Added tests for get_model_root function * fixup! Added tests for get_model_root function * Docs updates for Elasticsearch 2 support Also tweak examples to use elasticsearch2 backend by default * Test against Elasticsearch 2 on travis
2016-05-06 12:23:31 +02:00
elasticsearch2: elasticsearch>=2,<3
2016-11-08 12:17:26 +01:00
elasticsearch5: elasticsearch>=5,<6
elasticsearch5: certifi
setenv =
2015-04-03 15:38:08 +02:00
postgres: DATABASE_ENGINE=django.db.backends.postgresql_psycopg2
2015-04-03 15:38:08 +02:00
mysql: DATABASE_ENGINE=django.db.backends.mysql
mysql: DATABASE_HOST=localhost
mysql: DATABASE_USER=root
# Specific for Appveyor, see:
# https://www.appveyor.com/docs/services-databases/#sql-server-2016
mssql: DATABASE_ENGINE=sql_server.pyodbc
mssql: DATABASE_HOST=(local)\SQL2016
mssql: DATABASE_NAME=master
mssql: DATABASE_USER=sa
mssql: DATABASE_PASS=Password12!
[testenv:flake8]
basepython=python3.4
deps=flake8>=2.2.0
commands=flake8 wagtail