ENH: Disable check for framework Python in OSX backend. #92
Conversation
Without this check, the osx backend can be used with just `python` rather than requiring `pythonw`. `pythonw` still works better (window comes to the front and gives a taskbar icon), but not requiring `pythonw` is much less surprising to users. Since we now work with just python, simplify the tests.
|
Hi! This is the friendly automated conda-forge-linting service. I wanted to let you know that I linted all conda-recipes in your PR ( Here's what I've got... For recipe:
|
|
Thanks @dopplershift! |
|
This check went in via matplotlib/matplotlib@46f2d53 / matplotlib/matplotlib#4452 by @mdehoon . While this may fix the behavior, but I am very concerned about going against Michiel in matters of how to deal with the OSX backend. |
|
For matplotlib proper, we may just want to consider adjusting our checks (or something); without the check we can still get a plot, it just doesn't have a taskbar icon nor does the window come to the front initially. For conda-forge I think it's more important to be compatible with the defaults channel than having to explain to everyone that they need to use this weird "pythonw" thing--and I don't even know what to do about IPython. An alternative would be to fallback to a different back end rather than ending anything and everything with an exception--at least in the case of trying to use the "default" backend. |
Without this check, the osx backend can be used with just
pythonrather than requiring
pythonw.pythonwstill works better (windowcomes to the front and gives a taskbar icon), but not requiring
pythonwis much less surprising to users.Since we now work with just python, simplify the tests.