On Tue, Nov 19, 2019 at 10:49 AM Carlos Soriano via desktop-devel-list
wrote:
>
> Hi everyone,
>
> Good news! Thanks to OpenAtMicrosoft and our staff we have set up a Windows
> runner for the GNOME/ group. Right now it's a single runner with the
> "windows" tag attached, feel free to use it as
On Sat, Aug 11, 2018 at 12:28 PM, Lanoxx wrote:
> Hi All,
>
> It would be nice if I could get some response about my question from the
> community. I spend several days of work on this and I would like to know if
> there is a change that my patch gets merged into Gtk-Doc. I am restating my
>
Thanks everyone for chiming in!
I think we have all distros/OSes covered now and can make an informed
decision based on that.
I've opened a proposal MR for glib to drop Python 2 support
https://gitlab.gnome.org/GNOME/glib/merge_requests/196
___
On Sun, Jul 15, 2018 at 3:25 PM, Nicolas Dufresne wrote:
> Stable distribution shouldn't block software from going forward with
> Python 3. Simply because stable OS won't update to whatever we release
> next, unless it's bug/security fixes.
I agree in general, but as I noted at the end of my
> Slow-releasing/stable/"enterprise" distributions like RHEL, Debian,
> Ubuntu LTS and SLED are the usual sticking point for dependency versions.
>
> My understanding is that the main blocker for using Python 3 is
> that RHEL/CentOS 7 doesn't have it built-in, only as part of a secondary
>
Hey everyone,
we currently do support Python 2 and 3 for things like gobject-introspection
and glib scripts etc. and while I don't see any problem with continuing that
support I'd like to know why we still need to support Python 2 there. i.e.
What needs to happen so that Python 3 support is
