view setup.cfg @ 3625:260a7a01b054 beta

follow Python conventions for boolean values True and False might be singletons and the "default" values for "boolean" expressions, but "all" values in Python has a boolean value and should be evaluated as such. Checking with 'is True' and 'is False' is thus confusing, error prone and unnessarily complex. If we anywhere rely and nullable boolean fields from the database layer and don't want the null value to be treated as False then we should check explicitly for null with 'is None'.
author Mads Kiilerich <madski@unity3d.com>
date Thu, 28 Mar 2013 01:10:45 +0100
parents 55ff0b9ef89e
children cd50d1b5f35b 3483de9d11e5
line wrap: on
line source

[egg_info]
tag_build =
tag_svn_revision = true

[easy_install]
find_links = http://www.pylonshq.com/download/

[nosetests]
verbose=True
verbosity=2
with-pylons=test.ini
detailed-errors=1
nologcapture=1
#pdb=1
#pdb-failures=1

# Babel configuration
[compile_catalog]
domain = rhodecode
directory = rhodecode/i18n
statistics = true

[extract_messages]
add_comments = TRANSLATORS:
output_file = rhodecode/i18n/rhodecode.pot
width = 80

[init_catalog]
domain = rhodecode
input_file = rhodecode/i18n/rhodecode.pot
output_dir = rhodecode/i18n

[update_catalog]
domain = rhodecode
input_file = rhodecode/i18n/rhodecode.pot
output_dir = rhodecode/i18n
previous = true

[build_sphinx]
source-dir = docs/
build-dir  = docs/_build
all_files  = 1

[upload_sphinx]
upload-dir = docs/_build/html