mirror of
https://github.com/dashpay/dash.git
synced 2024-12-25 03:52:49 +01:00
313d79e319
f4beb4996d27f2cdaf4f0a63e7dc044bf17decce test: Remove python dead code linter (Wladimir J. van der Laan)
Pull request description:
Primarily I'd like to remove this because it is very imprecise, due to Python's dynamic nature, giving it a large list of false positives that need to be listed as exceptions. See for example #16906.
It's also a frequent source of complaints. I'm doubtful of the usefulness of checking for dead code in a linter in the first place.
Having some dead code in the test framework for a while is not a
disaster.
ACKs for top commit:
sdaftuar:
utACK f4beb4996d27f2cdaf4f0a63e7dc044bf17decce
practicalswift:
ACK f4beb4996d27f2cdaf4f0a63e7dc044bf17decce -- diff looks correct
jamesob:
ACK
|
||
---|---|---|
.. | ||
lint_04_install.sh | ||
lint_05_before_script.sh | ||
lint_06_script.sh | ||
README.md | ||
test_03_before_install.sh | ||
test_04_install.sh | ||
test_05_before_script.sh |
travis build scripts
The .travis
directory contains scripts for each build step in each build stage.
Currently the travis build defines two stages lint
and test
. Each stage has
it's own lifecycle.
Every script in here is named and numbered according to which stage and lifecycle
step it belongs to.