Tracking how to get this thing as a single binary available on Linux/MacOS/Windoze. Maybe we actually don't give a fook about MacOS/Windoze but definitely multiple Linux distros would be ideal as a first step.
Tracking how to get this thing as a single binary available on Linux/MacOS/Windoze. Maybe we actually don't give a fook about MacOS/Windoze but definitely multiple Linux distros would be ideal as a first step.
A piece of this relates to having pygobject and pycairo versions setup correctly. For example, when you install latest pycairo, you have a dependency on a system package, cairo which may or may not be available via your system package manager. Hence, we need to get these bounds right and to be relaxed enough to handle different distributions and to be at least 1 version back (e.g. Debian Stretch + Buster). See https://gitlab.gnome.org/GNOME/pygobject/-/issues/395#note_929707.
A piece of this relates to having `pygobject` and `pycairo` versions setup correctly. For example, when you install latest `pycairo`, you have a dependency on a system package, `cairo` which may or may not be available via your system package manager. Hence, we need to get these bounds right and to be relaxed enough to handle different distributions and to be at least 1 version back (e.g. Debian Stretch + Buster). See https://gitlab.gnome.org/GNOME/pygobject/-/issues/395#note_929707.
Tracking how to get this thing as a single binary available on Linux/MacOS/Windoze. Maybe we actually don't give a fook about MacOS/Windoze but definitely multiple Linux distros would be ideal as a first step.
A piece of this relates to having
pygobjectandpycairoversions setup correctly. For example, when you install latestpycairo, you have a dependency on a system package,cairowhich may or may not be available via your system package manager. Hence, we need to get these bounds right and to be relaxed enough to handle different distributions and to be at least 1 version back (e.g. Debian Stretch + Buster). See https://gitlab.gnome.org/GNOME/pygobject/-/issues/395#note_929707.Oh, more digging and I think I have some workable bounds now: