Hello Florian,
> > That sounds very nice. But you wouldn't normally put pylint into
> > the standard requirements, would you, so you would have a dedicated,
> > separate requirement file for it, to use with these services?
>
> I often see a requirements.txt (with runtime dependencies) and a
> requ
On Wed, Jul 18, 2018 at 09:01:39AM +0200, Kay Hayen wrote:
> Hello Florian,
>
> thanks for your reply.
>
> > > 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
Hello Florian,
thanks for your reply.
> > 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 doi
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
