[Matplotlib-devel] [Wheel-builders] Manylinux external library test case - matplotlib, tk

Benjamin Root ben.v.root at gmail.com
Sat Apr 30 11:16:46 EDT 2016

Right. Submitting the patch won't address our near-term needs, but it'll
certainly position us better a few years from now. I am thinking that for
the near-term, we could have a fail-over mechanism. First attempt to access
the proposed ik interface (to be forward-compatible), failing that, then
attempt a ctypes interface. Failing that, fall back to our current
implementation. This gives a way forward for those in the restricted
environments to keep doing whatever has been working so far, while giving
everyone else an intermediate solution -- a usable GUI backend that will
almost always be guaranteed to work no matter in what order the packages
were installed.

Ben Root

On Sat, Apr 30, 2016 at 3:43 AM, Nathaniel Smith <njs at pobox.com> wrote:

> On Fri, Apr 29, 2016 at 9:23 PM, Chris Barker <chris.barker at noaa.gov>
> wrote:
> > I'm sure I missed the conversation, but as tkInter is included with
> Python
> > itself, why can't the wheels link against the same version that python
> > ships??
> The problem is that we're trying to make a single build of matplotlib
> that works with multiple different builds of Python, which might come
> with different, incompatible builds of tkInter -- so if we build
> against the version shipped with python A then it will be broken on
> python B and vice-versa.
> Or maybe not -- Matthew's seeing a segfault, and it *might* be due to
> the existence of fundamental ABI incompatibilities between different
> tk builds, but it hasn't really been characterized.
> >> Submitting the buffer hook to tcl/tk and/or tkinter would be nice.
> >
> > That would be the better solution, yes -- presumable to tkinter -- but
> > that's only going to help with Python 3.6 or greater.....
> >
> > (or maybe it could be back-ported)
> It might get backported to 3.5, maybe 3.4 if we're really quick, but
> it won't get backported to 2.7, so yeah, anything involving changing
> python upstream isn't going to be a short-term solution.
> -n
> --
> Nathaniel J. Smith -- https://vorpus.org
> _______________________________________________
> Matplotlib-devel mailing list
> Matplotlib-devel at python.org
> https://mail.python.org/mailman/listinfo/matplotlib-devel
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/matplotlib-devel/attachments/20160430/d61937e9/attachment.html>

More information about the Matplotlib-devel mailing list