matplotlib-devel Mailing List for matplotlib

James Evans wrote:
>When using the Qt backend, resize events were not
>getting passed along properly so the window was created
>based off of some other criteria. The attatched patch
>file will fix the problem and make the window be
>resized appropriatly on construction.
>
> 
>
Admittedly I'm no Qt person (this was my opportunity to install Qt on my
system), but I couldn't find any problems with the current
implementation. Could you give a specific, reproducible problem case
that your patch fixes?
Cheers!
Andrew

James Evans wrote:
>I am uploading a newer patch that is against the SVN
>repository as of "MAR 10, 2006 13:55". This also
>contains a few minor cosmetic fixes/tweaks.
>
> 
>
Committed into svn 2142.
Watch those indents! For some reason, your patch had 3 space indents
(instead of 4) in some places. I also took the liberty of running
lib/matplotlib/dates.py through pylint and fixing some long lines.
Cheers!
Andrew

Andrew Straw wrote:
>After testing this patch, I tried checking it in, but I'm getting an error:
>
>$ svn commit src
>Authentication realm: <https://svn.sourceforge.net:443> SourceForge
>Subversion area
>Password for 'astraw':
>svn: Commit failed (details follow):
>svn: MKACTIVITY of
>'/svnroot/matplotlib/!svn/act/451cc94f-c20e-0410-914b-b8458948145c': 403
>Forbidden (https://svn.sourceforge.net)
>svn: Your commit message was left in a temporary file:
>svn: 
>'/home/astraw/other-peoples-src/matplotlib/matplotlib.svn/svn-commit.2.tmp'
>
>I tried a couple of times to make sure I got the password right, but it
>still didn't go. Does anyone know what's going on? This would have been
>my first commit since we switched to subversion.
> 
>
Weird, SF disables write access by default to the subversion repository:
http://sourceforge.net/tracker/?group_id=1&atid=200001&func=detail&aid=1443846
What's more bizarre is that apparently all the MPL devs aside from me
apparently had no problem committing despite this fact!
Anyhow, I found our permissions page and am in the process of adding
write access to all MPL devs.
https://sourceforge.net/project/admin/userperms.php?group_id=80706
James, your first patch (strict C/C++ conformance) is svn 2141 and I'll
work on your others in short order.

After testing this patch, I tried checking it in, but I'm getting an error:
$ svn commit src
Authentication realm: <https://svn.sourceforge.net:443> SourceForge
Subversion area
Password for 'astraw':
svn: Commit failed (details follow):
svn: MKACTIVITY of
'/svnroot/matplotlib/!svn/act/451cc94f-c20e-0410-914b-b8458948145c': 403
Forbidden (https://svn.sourceforge.net)
svn: Your commit message was left in a temporary file:
svn: 
'/home/astraw/other-peoples-src/matplotlib/matplotlib.svn/svn-commit.2.tmp'
I tried a couple of times to make sure I got the password right, but it
still didn't go. Does anyone know what's going on? This would have been
my first commit since we switched to subversion.
Anyhow, it looks like I can't apply the other patches right now, so I'm
giving up for the time being.
James Evans wrote:
>When compiling with less forgiving compilers 
>('MSVC', 'g++ --pedantic') there are a few sections of
>code that will fail. The attatched SVN diff file will
>patch the code to remedy this.
>
>The patch is as follows:
>-- In several places arrays are initialized with a
>variable for the length. As per Stroustrup arrays can
>only be specified with constants or using 'new' .
>
>-- in strict forms of C all variable declarations in a
>function must be finished before any actual code is run
>(cntr.c) 
> 
>

I just made some changes to svn that I want to mention. Sometimes, usetex's 
external dependencies could fail silently. Andrew suggested that the 
subprocess module included in python-2.4 could be used to catch the exit 
status and therefore report such problems. I added this module to mpl; tests 
on both linux systems with python-2.3 and python-2.4 were successful. Now if 
you pass give latex bad syntax, an exception is raised and you will see the 
report from latex. 
I also added a papertype kwarg for postscript. You can do something like
savefig('test.eps', papertype='letter')
or if you want the pagesize to scale automatically:
savefig('test.eps', papertype='auto')
Adding the papertype kwarg actually required a small change to every backend. 
I tested my work with backend_driver, and no problems turned up. Please let 
me know if you experience problems.
Finally, I got landscape orientation working properly with the usetex option. 
This wasnt an easy task, and I'll leave out the gory details, but I will say 
I've been pulling my hair out all weekend and my eyes are crossed.
Darren