Working through the checklist, I am wary of cutting an RC at this particular
moment. Why is just about a quarter of all the tests coming back as known
There are only two legit known fails, one in test_basic and one in
test_dates and these are the only two I am seeing. You are likely
seeing known fails on the pdf or svg tests because either you don't
have gs or inkscape installed to do the image conversion. Take a look
at ib/matplotlib/testing/compare.py to see the conversion commands
fails? Also, running unit/memleak_hawaii3.py is showing what seems to be a
memory leak (GTKAgg, Python 2.7, Ubuntu, 32-bit) on my system. The step ups
are about 40-50 KB at about once every 10 seconds.
I can't test this now because I am leaving for a roadtrip now until
tomorrow night; usually this steps up a bit on initial figures and
then stabilizes after a large number of figures. I don't have a
problem waiting til Monday to sort out a few lingering issues. I also
don't have a problem branching and cutting the rc now because we can
always fix things in the branch, but this increases the workload
because of the additional merge. So why don't we keep hammering on
the few remaining issues and shoot for Monday afternoon?
···
On Sat, Sep 24, 2011 at 12:37 AM, Benjamin Root <ben.root@...553...> wrote:
I trust Michael to get this right ahead of the release. It's a known
issue he's fixed before. I can test on a python 2.4 and 2.7 so if it
works on both of those I am comfortable. If we break something, we
can fix it.
···
On Fri, Sep 23, 2011 at 5:04 PM, Benjamin Root <ben.root@...553...> wrote:
Personally, my vote is to live with the deprecation warnings. They only
happen if you turn warnings on in python 2.7 (by default, they are off). I
am not that comfortable with such a change this close to release for a minor
issue (unless I am missing something..?)
I have made you a project admin on the sf site. That means you have
full permission to do anything (except commit to the svn repo).
However, to enable access to the html directory, you will need to add
your public key to the list of authorized keys (don't have the link
handy at the moment). You might potentially encounter some unix file
permission issues on the server as well, if we don't have the group
bits set up right. You'll just have to experiment with it.
Alternatively, I'm happy to pick up the ball on Monday
JDH
···
On Fri, Sep 23, 2011 at 11:54 PM, Benjamin Root <ben.root@...553...> wrote:
I will see about cutting the release, but I won't be able to upload any
files to SF, unless somebody can give me that permission for my account.
On Fri, Sep 23, 2011 at 5:04 PM, Benjamin Root<ben.root@...553...> wrote:
Personally, my vote is to live with the deprecation warnings. They only
happen if you turn warnings on in python 2.7 (by default, they are off). I
am not that comfortable with such a change this close to release for a minor
issue (unless I am missing something..?)
I trust Michael to get this right ahead of the release. It's a known
issue he's fixed before. I can test on a python 2.4 and 2.7 so if it
works on both of those I am comfortable. If we break something, we
can fix it.
You haven't announced or posted an rc tarball for testing yet have
you? Would you like me to do this? Are we holding on anything before
putting out something for general testing?
···
On Sat, Sep 24, 2011 at 12:37 AM, Benjamin Root <ben.root@...553...> wrote:
Working through the checklist, I am wary of cutting an RC at this particular
moment. Why is just about a quarter of all the tests coming back as known
fails? Also, running unit/memleak_hawaii3.py is showing what seems to be a
memory leak (GTKAgg, Python 2.7, Ubuntu, 32-bit) on my system. The step ups
are about 40-50 KB at about once every 10 seconds.
Thanks, missed that. Christoph and Russell, will you have a chance to
build some binaries we can upload for testing? Once this is done, we
should announce to the user list.
···
On Tue, Sep 27, 2011 at 11:30 AM, Sandro Tosi <morph@...12...> wrote:
On Tue, Sep 27, 2011 at 18:23, John Hunter <jdh2358@...149...> wrote:
On Sat, Sep 24, 2011 at 12:37 AM, Benjamin Root <ben.root@...553...> wrote:
Working through the checklist, I am wary of cutting an RC at this particular
moment.
I'm testing the debian package and I'll follow up with my thoughts on
it when done.
Thanks, missed that. Christoph and Russell, will you have a chance to
build some binaries we can upload for testing? Once this is done, we
should announce to the user list.
- what's the difference between examples/ and lib/mpl_examples/ dirs?
diff says they are identical, but maybe there's a reason there are 2
copies of them. If not, maybe you can remove one, so to reduce
confusion
- the tarball has grown a lot in size, ~3 times, but in the changelog
there's no mention of the reason of this growth (baseline images for
testing)
- the doc generation stops at thumbnails regen, it seems 'thumbnails'
dict is empty and so it stucks there.
If you want me to do any tests, just ask me.
Cheers,
···
On Tue, Sep 27, 2011 at 18:30, Sandro Tosi <morph@...12...> wrote:
On Tue, Sep 27, 2011 at 18:23, John Hunter <jdh2358@...149...> wrote:
On Sat, Sep 24, 2011 at 12:37 AM, Benjamin Root <ben.root@...553...> wrote:
Working through the checklist, I am wary of cutting an RC at this particular
moment.
I'm testing the debian package and I'll follow up with my thoughts on
it when done.
Thanks, missed that. Christoph and Russell, will you have a chance to
build some binaries we can upload for testing? Once this is done, we
should announce to the user list.
OK, I'm working on this and will send out the ANN when it is done.
Thanks everyone for their help, and Ben especially for herding the
cats and pushing us forward.
JDH
···
On Tue, Sep 27, 2011 at 4:00 PM, Benjamin Root <ben.root@...553...> wrote:
No, I couldn't figure out how to do that on sourceforge.
