csv-metadata-quality/.travis.yml

dist: bionic
language: python
python:
  - "3.6"
  - "3.7"
  - "3.8"
  - "3.9"
  - "nightly"
jobs:
  allow_failures:
    - python: "nightly"
install:
  - "pip install -r requirements.txt"
  - "pip install -r requirements-dev.txt"
script: pytest

# vim: ts=2 sw=2 et
.travis.yml: Use Ubuntu 18.04 "Bionic" 2019-11-14 22:22:19 +01:00			`dist: bionic`
Add Travis CI support I'm happy with SourceHut's build support, but Travis allows us to tests other Python versions. 2019-07-29 10:45:58 +02:00			`language: python`
			`python:`
Support Python 3.6 and 3.7 again 2020-01-15 11:19:17 +01:00			`- "3.6"`
			`- "3.7"`
.travis.yml: Test Python 3.8 2019-11-14 22:22:37 +01:00			`- "3.8"`
.travis.yml: Bump Python versions Test Python 3.9 now that it was released, and allow tests to fail on nightly builds. 2020-10-28 22:14:36 +01:00			`- "3.9"`
			`- "nightly"`
.travis.yml: Try to build with Python 3.8-dev But allow failures. 2020-03-29 15:40:11 +02:00			`jobs:`
			`allow_failures:`
.travis.yml: Bump Python versions Test Python 3.9 now that it was released, and allow tests to fail on nightly builds. 2020-10-28 22:14:36 +01:00			`- python: "nightly"`
Add Travis CI support I'm happy with SourceHut's build support, but Travis allows us to tests other Python versions. 2019-07-29 10:45:58 +02:00			`install:`
.travis.yml: Install packages from requirements.txt too 2019-11-14 22:42:28 +01:00			`- "pip install -r requirements.txt"`
.travis.yml: Try using pip instead of pipenv The Pipfile knows it was created with Python 3.8, yet we're running with multiple Python versions on Travis. I'm curious if would work better to use pip to install dependencies instead of pipenv in this case. 2019-11-14 22:37:25 +01:00			`- "pip install -r requirements-dev.txt"`
Add Travis CI support I'm happy with SourceHut's build support, but Travis allows us to tests other Python versions. 2019-07-29 10:45:58 +02:00			`script: pytest`

			`# vim: ts=2 sw=2 et`