Thanks to visit codestin.com
Credit goes to github.com

Skip to content

COMPAT: use tkagg backend on PyPy #9356

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 12 commits into from
Jan 12, 2018
Merged

COMPAT: use tkagg backend on PyPy #9356

merged 12 commits into from
Jan 12, 2018

Conversation

mattip
Copy link
Contributor

@mattip mattip commented Oct 11, 2017

PR Summary

the tkagg::blitfunction uses the id built-in to obtain memory adresses. This is not compatible with PyPy. I have written a proof-of-concept alternative blit function that uses a pure-python _tkagg backend via CFFI. Since CPython prefers a c-extension (_tkagg.so) over a python file (_tkagg.py) and PyPy reverses this, the two implementations can live side by side.

It is working but not yet complete:

  • on the matplotlib side I should probably only conditionally build the _tkagg c-extension on CPython
  • on the PyPy side the serialization/deserialization of a numpy ndarray should not make a copy of the data
  • updating only a bbox of data not supported yet
  • documentation

but I wanted to see if this approach is acceptable before continuing. Any thoughts?

Edit: now point three (bbox handling) is complete
Edit: (5.Nov.17) now points one and two are done, and documentation does not change

@anntzer
Copy link
Contributor

anntzer commented Oct 11, 2017

Looks like the only problematic use of id() is to get the underlying address of the ndarray object (the PyObject, not the memory buffer), right? I would suggest instead just passing a memoryview object, which contains all the relevant information even in Py2 (https://docs.python.org/2/library/stdtypes.html#memoryview), and adapting the extension code to accept such an input (it's all private anyways).

Actually now that I look at it it's not clear whether tk.call can pass memoryviews, but you can also just pass in the address of the underlying buffer and the size and strides of the array (and fix the extension code accordingly). The address of the underlying buffer is accessible at t.__array_interface__["data"] (https://docs.scipy.org/doc/numpy-1.13.0/reference/arrays.interface.html#__array_interface__).

If possible, I'd prefer avoid too much pypy specific code, because I fear it's quite likely to bitrot...

@tacaswell tacaswell added this to the 2.2 (next feature release) milestone Oct 11, 2017
@mattip
Copy link
Contributor Author

mattip commented Oct 16, 2017

@anntzer thanks for picking this up.

I tried to modify the id() calls as you said, but have not been able to get load_tkinter_funcs fron the _tkagg.cpp c-extension working on PyPy, so in the mean time I fleshed out this approach to see if it is functional.

@mattip
Copy link
Contributor Author

mattip commented Nov 5, 2017

I actually needed to change very little to get this working, in the end I:

  • modified the private calls to pass "ptr height width" instead of id(array)
  • added another case to the code on non-win32 that searches for the shared object that works with PyPy's cffi module tk._tkinter.tklib_cffi.__file__

On PyPy unfortunately there seems to be an issue with opening the "configure subplot" subfigure on a basic plot, the mouse events are not reliably reaching the event handlers in lib/matplotlib/widgets.py, maybe a threading issue or competing event loops?

_tkagg.tkinit(tk.interpaddr(), 1)
else:
# very old python?
_tkagg.tkinit(tk, 0)
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

interpaddr was added in 1998(! python/cpython@9d1b7ae) so I cannot actually imagine a case where this is triggered today (but that can go to another PR of course)

@mattip
Copy link
Contributor Author

mattip commented Nov 7, 2017

@tacaswell I got a mail reviewing the changes to setupext.py but cannot see it here, I removed the reference to py_converters.cpp since it is no longer needed. It was used to convert the python-level id(ndarray) to a C-level ndarray. Now I changed the code to pass in ptr height width instead, so the conversion does not require any knowlege about ndarrays

@mattip
Copy link
Contributor Author

mattip commented Nov 7, 2017

How do I fix the codecov/patch check failure?

@dopplershift
Copy link
Contributor

Don't worry about the codecov check there. The Tk GUI code, unfortunately, has no automated tests for CI to run.

@anntzer
Copy link
Contributor

anntzer commented Nov 7, 2017

We tend to ignore that check to be honest...

@mattip
Copy link
Contributor Author

mattip commented Nov 23, 2017

ping

src/_tkagg.cpp Outdated
#endif
# define BBOX_FORMAT "%f %f %f %f"
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

extra space?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

fixed in cc7b73e

src/_tkagg.cpp Outdated
deststride = 4 * destwidth;

destbuffer = new agg::int8u[deststride * destheight];
destbuffer = new uint8_t[deststride * destheight];
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

any reason for the change?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

now it no longer uses #include py_converters.h which supplied the agg:int8u

src/_tkagg.cpp Outdated
return TCL_ERROR;
}

if (sscanf(argv[4], BBOX_FORMAT, &x1, &x2, &y1, &y2) == 4) {
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

should probably error out cleanly if an invalid string is passed?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

yesish, these are basically "private" functions parsing a call from python, but I will add more checking code

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

updated in cc7b73e

src/_tkagg.cpp Outdated
has_bbox = true;
}
else {
else if (bbox_parse == 1 && x1 == 0){
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

parens

@anntzer
Copy link
Contributor

anntzer commented Nov 24, 2017

Can you rebase on master (to try to make appveyor pass... perhaps)?

src/_tkagg.cpp Outdated
desty = hdata - y2;
destwidth = x2 - x1;
destheight = y2 - y1;
destx = (int)x1;
Copy link
Contributor

@anntzer anntzer Nov 24, 2017

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Shouldn't BBOX_FORMAT just be 4 integers and just use integers all along? (not sure if tk would have the bad idea to always cast things to float)

Edit: Actually I guess not, what should really happen is that we should explicitly cast on the caller's side but this can just go as it is for now...

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The call sequence is backend.blit(image, bbox) -> tkagg.py:blit(image, bbox) -> PyAggImagePhoto(as_string(image, bbox)) so we cannot change the root backend.blit call. AFAICT the choice is:

  • convert early in tkagg.py:blit
  • convert later in PyAggImagePhoto

I usually prefer converting as late as possible to postpone rounding and allow future refactoring with floats to be as painless as possible, but will flow with whatever is matplotlib best practices

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think we can leave it as it is for now, we were using floats to start with and we can change that later.

Copy link
Contributor

@anntzer anntzer left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

assuming appveyor passes

Tested locally on cpython, not actually tested myself on pypy...

@mattip
Copy link
Contributor Author

mattip commented Nov 24, 2017

thanks, I tested on pypy HEAD and tkagg now works. However the way matplotlib uses weakref.ref in callbacks exposes a bug in the JIT, am working on distilling it so I can report and get it fixes

@mattip
Copy link
Contributor Author

mattip commented Nov 28, 2017

just to be clear, the weakref issue is not a matplotlib issue, rather a PyPy issue that matplotlib exposes

@mattip
Copy link
Contributor Author

mattip commented Dec 2, 2017

after #9899 was merged, this is all that is needed for the next release of PyPy to work with the TkAgg backend

embedding_in_tk2_sgskip is essentially a slightly simplified duplicate
of embedding_in_tk_sgskip.
src/_tkagg.cpp Outdated
deststride = 4 * destwidth;

destbuffer = new agg::int8u[deststride * destheight];
destbuffer = new uint8_t[deststride * destheight];
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why change away from the agg types here?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Previously there was a conversion from a PyArrayObject * (in other words ndarray) to a data pointer, width, height, etc via py_converters. Now I pass that information directly from python. I no longer need the "py_converters.cpp" and ""py_converters.h" since there is no use of ndarray in the c++ code. Should I leave the include for this one type definition?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I am concerned about the corner case where unint8_t and agg:int8u are different underlying types. Not sure how likely that actually is, hence leaning towards being conservative about changing it.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I wonder what different types you think these can be.
I would also bet that there must be parts of the code where we assume that this is interconvertible with np.uint8, or that this fits in a single byte... doesn't leave you a lot of options!

@mattip
Copy link
Contributor Author

mattip commented Dec 11, 2017

I never mentioned that what I thought was a PyPy weakref or JIT issue was actually solved by PR #9899 so this PR is all that is needed for TkAgg and PyPy

@mattip
Copy link
Contributor Author

mattip commented Dec 13, 2017

what's up with docs build? It seems to have timed out with no connection to my pull request

@tacaswell converted back to agg::int8u

@mattip
Copy link
Contributor Author

mattip commented Dec 19, 2017

what's up with docs build? It seems to have timed out with no connection to my pull request

@tacaswell converted back to agg::int8u

edit: docs build seems to have passed

@jklymak
Copy link
Member

jklymak commented Dec 19, 2017

Sometimes the builds need to be restarted manually because the host has a problem...

@mattip
Copy link
Contributor Author

mattip commented Jan 11, 2018

can I get this marked 2.2-critical?

@anntzer anntzer added the Release critical For bugs that make the library unusable (segfaults, incorrect plots, etc) and major regressions. label Jan 11, 2018
@anntzer
Copy link
Contributor

anntzer commented Jan 11, 2018

"Making PyPy work" sounds like a good thing to have...

@anntzer
Copy link
Contributor

anntzer commented Jan 12, 2018

By the way would be nice to add a whatsnew entry (including info about what versions of PyPy are supposed to work).

@mattip
Copy link
Contributor Author

mattip commented Jan 12, 2018

Not sure 270f05d is the proper way to do it, let me know if I should have done it differently

@tacaswell
Copy link
Member

Perfect @mattip

@tacaswell tacaswell merged commit 3bb328f into matplotlib:master Jan 12, 2018
@tacaswell
Copy link
Member

Thanks @mattip !

@QuLogic QuLogic modified the milestones: needs sorting, v2.2.0 Feb 12, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
GUI: tk Release critical For bugs that make the library unusable (segfaults, incorrect plots, etc) and major regressions.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants