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

[Benjamin Root]

What would be better is if we can get rid of the compilation requirement,
but from Michael's comments in the past, it seems that this isn't possible
at the moment. The problem is that the compiled portion provides the image
buffer access, which seems to not be available at the python level. Perhaps
it might make sense to pursue submitting our code to the Tk/Tcl project so
that we might be able to drop this step at some point?

Ben Root


On Mon, Apr 25, 2016 at 3:03 PM, Matthew Brett <matthew.brett at gmail.com>
wrote:

> Hi,
>
> On Mon, Apr 25, 2016 at 11:58 AM, Thomas Caswell <tcaswell at gmail.com>
> wrote:
> > My only thought is to just not build the tk backend, shipping wheels that
> > are known to segfault is no good.
>
> :) - no good at all!
>
> Incidentally, the wheels at http://nipy.bic.berkeley.edu/manylinux/ do
> not have the tk backend, and so, do not (are not known to) segfault.
>
> > Is there any way to (optionally) do a bit of compilation on installation
> of
> > a binary wheel?
>
> No, at least not with the `pip install` step.  The wheel install
> mechanism doesn't have post-install hooks.
>
> Is there an easy way to only do the tkagg build install, if we worked
> out a way to trigger that?
>
> Cheers,
>
> Matthew
> _______________________________________________
> 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/20160425/459ba23c/attachment.html>