-
-
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
Fixes for native fs-events #716
Conversation
Thank you for the fix 🍾 FTR I disabled tests for Python 3.6-3.10 as they will be done on master. |
Oups, I forgot to tell that the clean-up is already active on the branch. Could you rebase? |
Sure, no problem. |
Addresses one possible source of memory corruption, and simplifies the code.
11ef299
to
5142713
Compare
I am OK to merge! |
I'd first like to figure out the reason for the broken test. It appears to be a regression, and is pretty weird overall. |
Python 2.7 didn't like the double string conversion. Also improve some of the error handling code to behave better, as well as add error handling to th PyCapsule creation.
Inspired by issue gorakhargosh#706
Should be OK to merge now, travis is just slow to get around to all environments. |
You are a killer :) |
Some fixes and code simplifications for the native fsevents module:
PyBytes_
C API, so we can remove a bunch of the#if PY_MAJOR_VERSION
conditionals.NativeEvent
(and provides additional ones that weren't exposed so far). This fixes [macOS] Events without "renamed" or "modified" flags are dropped #702 .Alas, the Python 2.7 tests currently fail with an interesting error in
tests/test_fsevents.py::test_unschedule_removed_folder
that I still need to investigate. So this draft PR is primarily to see what the CI says for everything that I cannot test locally.