python310Packages.watchdog: 2.3.0 -> 2.3.1

[mweinelt]

https://github.com/gorakhargosh/watchdog/blob/v2.3.1/changelog.rst

less risky than #225406

Description of changes

Things done

• Built on platform(s)
  • x86_64-linux
  • aarch64-linux
  • x86_64-darwin
  • aarch64-darwin
• For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
• Tested, as applicable:
  • NixOS test(s) (look inside nixos/tests)
  • and/or package tests
  • or, for functions and "core" functionality, tests in lib/tests or pkgs/test
  • made sure NixOS tests are linked to the relevant packages
• Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
• Tested basic functionality of all binary files (usually in ./result/bin/)
• 23.05 Release Notes (or backporting 22.11 Release notes)
  • (Package updates) Added a release notes entry if the change is major or breaking
  • (Module updates) Added a release notes entry if the change is significant
  • (Module addition) Added a release notes entry if adding a new NixOS module
• Fits CONTRIBUTING.md.

[dylanmtaylor]

Looking at https://github.com/gorakhargosh/watchdog/blob/master/changelog.rst#300 I don't see too much to be concerned about. Largely just code quality changes and dropping Python 3.6. I would suggest #225406 be merged instead.

[vcunat]

I don't know. Say, the less risky one now for 23.05.

[mweinelt]

Looking at gorakhargosh/watchdog@master/changelog.rst#300 I don't see too much to be concerned about. Largely just code quality changes and dropping Python 3.6. I would suggest #225406 be merged instead.

Yeah, but projects will have pins that say <3, which will ripple through the package set, and I'm not in a position to resolve these right now.

[vcunat]

Oh, the conditional patch doesn't apply:
https://hydra.nixos.org/build/217596281

[vcunat]

Dropping the patch doesn't help, as the original issue seems to still apply, as described in PR #171388

[mweinelt]

Planning to go with #225406 instead. It has the updated patch. Rebase and testing in progress.