Change restricted version of pyflakes

[IDerr]

Change restricted version from 2.0.0 to 2.1.0 to fix #307

[coveralls]

Coverage remained the same at 77.699% when pulling 3970f76 on IDerr:master into 8bb1970 on PyCQA:master.

[Kilo59]

Would it be better (and possible) to loosen the requirements to allow for minor/micro updates to pyflakes while restricting major/minor ones?

Would either of these work?

'pyflakes<2.1,>=0.8.1',

'pyflakes<2,>=0.8.1',

[carlio]

Prospector has the problem that it is using apis of several other packages which were not really meant as libraries but rather as first-class cli tools, with their own release cycles, and some of those apis are not designed to be public but rather internal, so it's very easy for any release of any upstream dependency to break prospector. That's why things have moved to being very restrictive, because broken prospector means broken builds for lots of people and ultimately the bug reports go here first.

A better "notification -> update of prospector -> release" cycle is necessary unfortunately to avoid people spending their morning working out why builds suddenly break and then prospector devs have to work out why and then it turns out that pylint renamed a function or something...

[Kilo59]

I agree, it would be nice if only allowing micro-releases, for example, would guarantee nothing breaks and only ever fix minor bugs. But I don't think that's something you could be sure of.

This is a nice new feature of github.
https://help.github.com/articles/watching-and-unwatching-releases-for-a-repository/

Perhaps it can be a part of that new release cycle. Even better if say a CI job could be kicked off and tested with the new pinned version automatically.

[carlio]

I've been having a similar discussion about another lib I maintain, pylint-django, as it faces the same problems: pylint-dev/pylint-django#206

[Kilo59]

Should give this a try.
I set it up on one of my repos a little while ago and actually found it annoying so I turned it off.
But I think it might actually work very well for this problem.

It will automatically submit PR's with updated requirements files when a dependency gets updated.

https://pyup.io/

[changeling]

What's the status of this?

[chocoelho]

According to their changelog we should be good to go, I just want to give it some more trying in order to check with other repos. Checked against prospector project and it ran fine, but still need to validate this change against a wider range of projects to check if we're not going to trigger broken builds throughout repos.

[IDerr]

Thanks for your work guys

[chocoelho]

Thanks @IDerr I hope to ship this soon, at least in a dev version.