Re: [matplotlib-devel] Planning for 1.3.0

[Derek H. <de...@as...>]

Hi Michiel,

On 15.04.2013, at 6:03AM, Michiel de Hoon <mjl...@ya...> wrote:

> --- On Sun, 4/14/13, Derek Homeier <de...@as...> wrote:
>> Of course if there are any other possible negative effects
>> besides the window handling, I'd take your point.
> 
> Several bugs have been reported in the past that turned out to be due to Python not being installed as a framework. For example, the file selection window when saving a figure doesn't respond. This has been a major hassle, since each of those bug reports take time to investigate before realizing that it is due to the Python installation.

OK, that is a valid reason! I vaguely remember some problems with that in the past,
though haven't experienced any of that in a long time (just tested 'Save File', and I've
been regularly using 'Configure Subplots'). But this is probably a case where a
Warning might not keep all users from filing a bug. :-(
The QT4Agg backend has its ups as well, though there still seem to be some quirks,
too (e.g. the zoom rectangle only shows up with the left and lower border); I will probably
become a fan of the line configuration tool that allows you to switch back to linear from a
log axis scale (in the command line there seems to be no return from plt.semilogy() or
plt.loglog())!

Cheers,
						Derek