Last commit is about 1years old.
136 open issues...
141 issues in August 28, 2018. No active forks?
I've just became a new collaborator. I'm going to release today a new 0.9.0 version with the master tip as is (actually, I'll change some few stuff like adding me to AUTHORS and adding a 3.7 classifier).
I'm thinking on dropping the Python 2.6 and 3.2 compatibility (and perhaps 3.3 as well), as I'm having some bad time to get Travis CI working with them. Running locally, it's passing in the tests even on these Python versions. Nevertheless, the burden of maintaining the code for these old Python versions seem to not worth the trouble.
I think it would be good idea to end Support for Python 2.
Python 3.4, 3.5, 3.6 and 3.7 would be enough
I managed to make it pass on every Python version (Python 2.6+, Python 3.2+, PyPy, PyPy3) on Travis CI!
https://travis-ci.org/gorakhargosh/watchdog/builds/421748950
"I think it would be good idea to end Support for Python 2."
Very bad idea... for a question of using certain libs, you need to be compatible with Python 2.7
The new v0.9.0 had just been released and it's already available in PyPI! I'll close this issue =)
Most helpful comment
I'm thinking on dropping the Python 2.6 and 3.2 compatibility (and perhaps 3.3 as well), as I'm having some bad time to get Travis CI working with them. Running locally, it's passing in the tests even on these Python versions. Nevertheless, the burden of maintaining the code for these old Python versions seem to not worth the trouble.