Mercurial > kallithea
view .travis.yml @ 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 | 925c77b9d3f1 |
children | 69377d1d7604 |
line wrap: on
line source
language: python python: - "2.5" - "2.6" - "2.7" env: - TEST_DB=sqlite:////tmp/rhodecode_test.sqlite - TEST_DB=mysql://root@127.0.0.1/rhodecode_test - TEST_DB=postgresql://postgres@127.0.0.1/rhodecode_test services: - mysql - postgresql # command to install dependencies before_script: - mysql -e 'create database rhodecode_test;' - psql -c 'create database rhodecode_test;' -U postgres - git --version before_install: - sudo apt-get remove git - sudo add-apt-repository ppa:pdoes/ppa -y - sudo apt-get update -y - sudo apt-get install git -y install: - pip install mysql-python psycopg2 mock unittest2 - pip install . --use-mirrors # command to run tests script: nosetests notifications: email: - marcinkuz@gmail.com irc: "irc.freenode.org#rhodecode" branches: only: - dev