Mercurial > kallithea

view MANIFEST.in @ 8262:66670aff96c5

Find changesets by keywords (author, files, the commit message), revision number or hash, or revset expression.
celery: set default config values in code and remove them from the generated .ini It is hard to imagine any reason the user should change celery.imports . And if it ever should change, we want it controlled in code - not left stale in user controlled config files. Everybody sould just use .json and there is no reason anybody should specify that in the .ini ... and it will be the default in Celery 4.
author Mads Kiilerich <mads@kiilerich.com>
date Tue, 18 Feb 2020 17:03:09 +0100
parents ddfecf9fe7f2
children 97c5e6ac5c75
line wrap: on
line source

include           .coveragerc
include           Apache-License-2.0.txt
include           CONTRIBUTORS
include           COPYING
include           Jenkinsfile
include           LICENSE-MERGELY.html
include           LICENSE.md
include           MIT-Permissive-License.txt
include           README.rst
include           conftest.py
include           dev_requirements.txt
include           development.ini
include           pytest.ini
include           requirements.txt
include           tox.ini
recursive-include docs *
recursive-include init.d *
recursive-include kallithea/alembic *
include           kallithea/bin/ldap_sync.conf
include           kallithea/lib/paster_commands/template.ini.mako
recursive-include kallithea/front-end *
recursive-include kallithea/i18n *
recursive-include kallithea/public *
recursive-include kallithea/templates *
recursive-include kallithea/tests/fixtures *
recursive-include kallithea/tests/scripts *
include           kallithea/tests/models/test_dump_html_mails.ref.html
include           kallithea/tests/performance/test_vcs.py
include           kallithea/tests/vcs/aconfig
recursive-include scripts *