@OceanWolf @fariza Can you take a look at this verify that this does not warn on the supported versions of gtk* backends?

Yay for getting rid of a MacO$ backend that I can't test the backend refactor on! But why don't we deprecate CocoaAgg on the same timeline as the other two rather than immediately removing it now?

I didn't realise that GTK existed as a separate backend from GTKAgg and GTKCairo, I always assumed that GTK aliased to GTKAgg or`GTKCairo``.

P.S. Never heard of FLTK until now ;).

On 2016/06/13 10:33 AM, OceanWolf wrote:

But why don't we deprecate |CocoaAgg| on the same timeline as the other
two rather than immediately removing it now?

It was never a complete backend, and has been deprecated since 1.3 with
removal scheduled in 1.4, but forgotten. It is highly unlikely that
anyone is using it for anything.

Ahh, okay, then we have given users plenty of time to migrate away from it.

In terms of testing, I can't get the GTKAgg/Cairo backends to work on python3... a bug?

ImportError: Gtk* backend requires pygtk to be installed.`` I look in the debian

In debian we don't have a python-gtk2 only python3-gi.

@fariza do you still use python2, if not I will recompile mpl for python2.

As far as I know PyGtk2 never supported python3 so the GTK2 backends are python 2 only

This was the case long time ago, I don't know still the same but I have always thought
Python2 => GTK2
Python3 => GTK3

Not 100% sure about that...

import gi
gi.require_version("Gtk", "2.0")
from gi.repository import Gtk as gtk, Gdk as gdk, GObject as gobject, GLib, Pango as pango

gives

/usr/lib/python3/dist-packages/gi/overrides/Gtk.py:50: RuntimeWarning: You have imported the Gtk 2.0 module.  Because Gtk 2.0 was not designed for use with introspection some of the interfaces and API will fail.  As such this is not supported by the pygobject development team and we encourage you to port your app to Gtk 3 or greater. PyGTK is the recomended python module to use with Gtk 2.0

I can't test further as I don't think _backend_gdk.so builds under python3.

Btw, if you want to make it really clear and extra safe you can write:

if self.__class__ == FigureCanvasGTK:
  warn.deprecated()

I have tested this syntax on both python2.7 and python3.5.1 in __init__ and both do the expected thing, with self.__class__ referring to the actual class of the instance.

class Parent(object):
    def __init__(self):
        print('Setting up Parent', self.__class__)
        if self.__class__ == Parent:
            print('I am me')
        else:
            print('I am someone else')

class Child(Parent):
    def __init__(self):
        print('Setting up Child', self.__class__)
        super(Child, self).__init__()


print('--- Creating Parent ---')
a = Parent()

print('--- Creating Child ---')
b = Child()

Suspect this was broken by the six merge

Closing in favour of #6582