Open gzm55 opened 7 years ago
Bump, @posborne ?
@gzm55 @stuaxo I haven't touched anything related to this for some time and could use independent verification if you are actively working with dbus-python. Based on the notes in the issue, I would say that it appears that things appear to be working upstream.
With confirmation I will gladly make a note that people should not be using this and should depend on upstream if possible (that's always really been preferable but at the time the maintainers left us in a difficult spot which is why this was first created).
I got as far as seeing that setup.py existed in upstream, but I'm more a very very casual user ... never used dbus until I wanted to try experimenting with it on windows last night (and I'm usually not a windows user).
Hi,
in the issue: https://bugs.freedesktop.org/show_bug.cgi?id=55439 and dbus-python 1.2.4, it seems the upstream does have the correct setup.py. Does this mean that this fork can be deprecated and preferred the upstream pip package?