Hey, On Tue, Jul 17, 2018 at 09:38:13AM +0200, Kay Hayen wrote: > However, for each PyLint release, e.g. 2.0.0, there will be a bunch of > findings that are new, and will to be found, leading to the Travis > builds to fail due to PyLint, all the time now. > > How to approach that. Is there a way I could have enforced using 1.9.2 > on the "master" branch for Travis (and probably "develop" too), and > use the latest greatest PyLint for "factory" only. Anyone know if that > is possible, somehow, anybody doing something like that? Or maybe > install a given version, but make it an error if that version is not > the most recent on only the factory branch, what are people doing in > this regard?
You'd usually use requirements.txt files with exact version pinning - ideally not only for pylint, but for all your dependencies and tools, to ensure deterministic, reproducable results. Then you can use https://requires.io/ or https://pyup.io/ to get notifications (or pull requests) to periodically update the pinned versions. Florian -- https://www.qutebrowser.org | m...@the-compiler.org (Mail/XMPP) GPG: 916E B0C8 FD55 A072 | https://the-compiler.org/pubkey.asc I love long mails! | https://email.is-not-s.ms/
signature.asc
Description: PGP signature
_______________________________________________ code-quality mailing list code-quality@python.org https://mail.python.org/mailman/listinfo/code-quality
