You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
use('module://') directive doesn't work as expected #2309
doesn't work as expected if my_backend's name clashes with one of the modules in matplotlib.backends. In that case the result is confusing (in my case my_backend is called backend_webagg since I was experimenting on it).
get_backend() still says module://my_backend
pylab_setup() returns the module with the same name from matplotlib.backends
I would expect pylab_setup() to return the same module as import my_backend.
Technically, it is. It is importing backend_webagg from where it is. It is
a completely different place than where your code that called
use('module://backend_webagg'). Now, one thing I haven't thought about is
differences in behavior between py2.x and py3k for this feature. This
particular feature probably doesn't get exercise in our test suite, so I am
not sure how it should behave.
Activity
WeatherGod commentedon Aug 22, 2013
Technically, it is. It is importing backend_webagg from where it is. It is
a completely different place than where your code that called
use('module://backend_webagg'). Now, one thing I haven't thought about is
differences in behavior between py2.x and py3k for this feature. This
particular feature probably doesn't get exercise in our test suite, so I am
not sure how it should behave.
andreabedini commentedon Aug 23, 2013
I understand what's happening and why the module in
matplotlib.backendsgets picked. Perhaps we should make sure the import is always absolute.make sure we only perform absolute imports on loading a backend