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'.

include rhodecode/config/deployment.ini_tmpl
include rhodecode/lib/dbmigrate/migrate.cfg

include README.rst
recursive-include rhodecode/i18n *

#docs
recursive-include docs *

#init.d
recursive-include init.d *

#images
recursive-include rhodecode/public/css *
recursive-include rhodecode/public/images *
#js
recursive-include rhodecode/public/js *
#templates
recursive-include rhodecode/templates *