Questions on the use of a fork of notify

[baldurmen]

Description

Hello!

I maintain this library in Debian.

Since 6e3c2c8, watchfiles has been using a fork of the notify library.

I though this might have been a temporary fix, but now that version 1.0.0 has been released with it, I wanted to ask what are you plans with regards to this situation.

On the Debian side, using forks like that for a particular project makes it pretty hard to keep packaging this library. Depending on a git branch instead of a proper release makes it even harder in fact :(

Cheers,

Example Code

No response

Watchfiles Output

No response

Operating System & Architecture

N/A

Environment

No response

Python & Watchfiles Version

N/A

Rust & Cargo Version

No response

[musicinmybrain]

I’m chiming in because I was looking at updating the python-watchfiles package in Fedora.

We can handle git dependencies like this – we have a policy for them – but it’s something we want to avoid as much as possible, and per our general policy for bundling, we need to specifically ask about a path toward using a system copy of that library. (This comment is intended to satisfy that requirement.)

Is there a path to getting notify-rs/notify@0f87ab1 upstream so you don’t have to fork notify forever?