Commit graph

19 commits

Author SHA1 Message Date
Anthony Scopatz
1d3cadb532 let flake8 set the pyflakes version 2019-01-29 11:42:23 -05:00
Anthony Scopatz
10f67def3c more CI test fixes 2019-01-28 18:04:15 -05:00
Anthony Scopatz
b38b433583 change req order for pip 2019-01-28 18:03:59 -05:00
Gil Forsyth
86d9eb65d3 Remove pyflakes pin to fix build error 2018-10-29 10:50:47 -04:00
Morten Enemark Lund
6d6548dc58 Remove support of pygments <2.2 2018-08-01 22:22:08 +02:00
Anthony Scopatz
9640461451 some formatting fixes 2018-07-15 17:00:46 -05:00
Anthony Scopatz
d4d238e0b2 move pyflakes below flake8 2018-07-15 16:23:26 -05:00
Anthony Scopatz
c9828a50ec update reqs and CI 2018-07-15 15:53:46 -05:00
Gil Forsyth
eda7e077bd Pin prompt_toolkit in travis setup
Temporary fix (that we implemented everywhere else) to prevent failures
due to the prompt_toolkit release
2018-06-05 17:05:32 -04:00
Gil Forsyth
5c68df0719 remove numpy and matplotlib from pip test reqs
we miss out on the mpl xontrib tests but the overhead from installing
these on CI is massive
2016-10-11 12:22:59 -04:00
Derek Thomas
75ffd2ab2c add numpy and matplotlib as testing requirements to support mpl 2016-10-03 16:38:30 +09:00
Leonardo Santagada
0f7ccc7539 some weird interaction between timeouts and flake8 3.0.0 in travis 2016-07-27 16:01:28 +02:00
Leonardo Santagada
f8f03e4b2e fix package versions 2016-07-27 15:50:02 +02:00
Leonardo Santagada
5793dc0d92 update flake8 to 3.0.2
during the update we have to ignore some new errors on our current
codebase
2016-07-27 15:34:05 +02:00
Leonardo Santagada
b1616ff170 don't update on install and set package versions 2016-07-26 09:07:59 +02:00
Leonardo Santagada
74de1591c5 run flake8 and coverage inside pytest and on travis 2016-07-15 09:34:01 +02:00
Gil Forsyth
b2981f2169 update travis and appveyor to run pytest (hopefully) 2016-06-22 16:17:04 -04:00
Matthias Bussonnier
c28eafde53 Enable (some) coverage.
Not sure exactly how xonsh is tested completely, so I expect most of the
coverage process to be wrong (for now)

Codecov have [browser
extensions](https://github.com/codecov/browser-extension) that allow you
to see the coverage directly in the pull requests in GitHub.

We might have to give codecov some limited access to the repo (webhook),
and tell the codecov bot to shut its mouth once it's enabled. But it's
super non intrusive, and kind-of useful when you refactor to see that
your code is tested.

Also set some sensible where coverage would fail only if it drops by 10%
in 1 PR.
2016-06-06 20:02:13 -07:00
Randy Syring
1405181f81 fix travis call to pip 2016-04-01 00:26:40 -04:00