Fantastic! Thank you! Longer term, I think the metapackage idea has some promise. An alternative might also be for matplotlib to be more dynamic at startup time when selecting a backend. For example, we could have an "Auto" backend setting, that would select from Qt, Gtk, Tk, Cocoa etc. based on the user's DE and what is available and installed. Currently, we do this at build time, but it might be more appropriate at startup time in the context of pre-compiled packages. Anyway, that's OT for this bug, but we'd be happy to discuss this on the matplotlib-devel mailing list. Input from people with experience distributing things or who know how other projects handle this issue would be very helpful to us.
-- [intrepid] No output in ipython because because of wrong default backend https://bugs.launchpad.net/bugs/278764 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
