Re: Some PyGObject related news/updates




On Apr 28, 2017, at 3:21 AM, Christoph Reiter <reiter christoph gmail com> wrote:

Hey everyone,

* There now exists a "pygobject" [0] github organization containing repos
 related to everything Python + GObject related. My hope here is to make them
 look a bit more "official", give an overview of all the work happening, and
 to reduce the bus factor.

* The organization also contains a fork of pycairo which current pygobject
 master depends on. This means distros shipping GNOME 3.26 will likely be
 forced to upgrade to it (msys2 already does). If you had any problems with
 pycairo before please file a bug report, but there is a good chance that the
 last release [1] already contains a fix. There is ongoing work to adjust
 www.cairographics.org and pypi to reflect the upstream change and make this
 a bit more official.

* The PyGObject test suite now runs on Windows and macOS. Especially on
 Windows, using msys2, development is as simple as under Linux: clone, make,
 hack, make check, done. For 64bit Windows some changes from glib master are
 still required.

* The PyGObject test suite now runs with GTK+4: "make check
 TEST_GTK_VERSION=4.0". This should guarantee that at least the basics work
 and I encourage everyone brave enough to try GTK+4 to report any bugs you
 find.

* The PyGObject wiki.gnome.org page [2] is now gone and things have been moved
 to https://pygobject.readthedocs.io. I encourage everyone to contribute, be
 it through issues pointing out missing information or by improving the page.
 The page is also part of the afore-mentioned github orga.

[0] https://github.com/pygobject
[1] https://pycairo.readthedocs.io/en/latest/changelog.html
[2] https://wiki.gnome.org/Projects/PyGObject/


This doesn't make sense. How is creating a Github repo and moving the wiki to readthedocs.io supposed to make 
things seem "more official" and why would that be the sole motivation for all of the work?

At this moment the Github repo contains the fork of PyCairo and some projects that seem to be about 
automatically generating API docs for PyGobject. That's very far indeed from "everything Python + GObject 
related". Are you planning also to fork PyGobject?

Regards,
John Ralls



[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]