Skip to content

Conversation

@JoachimCoenen
Copy link
Contributor

fixes #275

@BoboTiG
Copy link
Collaborator

BoboTiG commented Mar 16, 2025

Wow! Let me some time to properly review in depth this PR <3

@BoboTiG
Copy link
Collaborator

BoboTiG commented Mar 16, 2025

Given that is a major breaking change, https://pypistats.org/packages/watchdog metrics, and upcoming 3.9 EOL (https://devguide.python.org/versions/), I would be OK to drop Python 3.9 at the same time if it eases your work.

@JoachimCoenen
Copy link
Contributor Author

I don't think we need to drop 3.9 compatibility (yet).

@BoboTiG BoboTiG merged commit ad0d055 into gorakhargosh:master Apr 25, 2025
@BoboTiG
Copy link
Collaborator

BoboTiG commented Apr 25, 2025

Thanks @JoachimCoenen 🥂

TobiasRzepka pushed a commit to TobiasRzepka/watchdog that referenced this pull request Oct 11, 2025
…akhargosh#1099)

* re: gorakhargosh#275 reduced number of created inotify instances - first draft

* re: gorakhargosh#275 fixed race conditions from inotify

* re: gorakhargosh#275 fixed test_inotify_c.py

* re: gorakhargosh#275 fixed test_inotify_buffer.py

* re: gorakhargosh#275 renamed test_inotify_buffer.py to test_inotify_watch.py

* re: gorakhargosh#275 ignore error when removing a watch that doesn't exist anymore

* re: gorakhargosh#275 fixed some docstrings

* re: gorakhargosh#275 renamed InotifyBuffer to InotifyMoveEventGrouper

* re: gorakhargosh#275 renamed InotifyWatch to InotifyWatchGroup

* re: gorakhargosh#275 added clarifying comments

* re: gorakhargosh#275 added test case for independence of InotifyWatchGroups

* re: gorakhargosh#275 renamed test_inotify_watch_grouper.py to test_inotify_watch_group.py

* re: gorakhargosh#275 removed superfluous todos

* re: gorakhargosh#275 fixed too early import in test

* re: gorakhargosh#275 fixed python 3.9 compatibility

* re: gorakhargosh#275 fixed python 3.9 compatibility

* re: gorakhargosh#275 fixed linter issues
TobiasRzepka pushed a commit to TobiasRzepka/watchdog that referenced this pull request Oct 11, 2025
…akhargosh#1099)

* re: gorakhargosh#275 reduced number of created inotify instances - first draft

* re: gorakhargosh#275 fixed race conditions from inotify

* re: gorakhargosh#275 fixed test_inotify_c.py

* re: gorakhargosh#275 fixed test_inotify_buffer.py

* re: gorakhargosh#275 renamed test_inotify_buffer.py to test_inotify_watch.py

* re: gorakhargosh#275 ignore error when removing a watch that doesn't exist anymore

* re: gorakhargosh#275 fixed some docstrings

* re: gorakhargosh#275 renamed InotifyBuffer to InotifyMoveEventGrouper

* re: gorakhargosh#275 renamed InotifyWatch to InotifyWatchGroup

* re: gorakhargosh#275 added clarifying comments

* re: gorakhargosh#275 added test case for independence of InotifyWatchGroups

* re: gorakhargosh#275 renamed test_inotify_watch_grouper.py to test_inotify_watch_group.py

* re: gorakhargosh#275 removed superfluous todos

* re: gorakhargosh#275 fixed too early import in test

* re: gorakhargosh#275 fixed python 3.9 compatibility

* re: gorakhargosh#275 fixed python 3.9 compatibility

* re: gorakhargosh#275 fixed linter issues
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Calling inotify_init() on each watch

2 participants