-
-
Notifications
You must be signed in to change notification settings - Fork 704
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Events from non-ASCII paths raise UncodeDecodeError #516
Comments
Python 2 is no more supported. Do you reproduce the error on Python 3? |
That's quite disappointing and frustrating to discover, considering the README:
My project is a large Python 2 code base and there's zero chance I will be using Python 3 with it in the next year (maybe slightly higher than zero chance after that). It's 70kloc of messy code with un-ported dependencies. Is there no way the watchdog project can continue to support Python 2 at least until python-dev abandons it? (And note that even after python-dev abandons Python 2, there's still PyPy.) If you're dead set on dropping Python 2 then as a huge favor to your users, I suggest changing the README to stop advertising Python 2.7 support. |
Ooops sorry ! I said bullshit: Python 2.7 is still supported. I dropped support on another project and mixed my brain :/ For the bug, it would be great if you can have a look for a PR (including a simple test). |
Okay, thanks! I'll see about putting together a PR tomorrow. |
results in this exception
Apparently introduced in 0c5e353
The text was updated successfully, but these errors were encountered: