Re: [matplotlib-devel] git migration this weekend

2011-02-16 Thread Darren Dale 
On Sun, Jan 30, 2011 at 8:10 AM, Darren Dale  wrote:
> On Thu, Jan 27, 2011 at 9:34 PM, Darren Dale  wrote:
>> Hi Folks,
>>
>> I'm planning on freezing the sourceforge svn repository Friday evening
>> at 8:00 (NY time), and moving the git repository to its new home on
>> Saturday morning.
>>
>> If you have concerns, please speak up.
>
> John discovered a problem with some very early project history that
> was lost several years ago during the CVS to Subversion migration. We
> have an opportunity to recover it during the git migration. However,
> do to a recent attack, Sourceforge has taken their CVS service down,
> and based on the latest information at http://sourceforge.net/blog/ ,
> they do not expect it to be back before late this week. I do not think
> I will available to work on the migration this upcoming weekend, Feb
> 4-6. So it will probably be February 7 or 8 before I have a chance to
> try to recover the old history, convert the repos to git, and post
> them to github.

It looks like the history we were looking for does not exist in the
CVS repository either.

John, could you freeze the svn repo around noon on Friday? I'll
convert the repositories and push them up to github on Saturday. Is it
possible to close the sourceforge bugtracker, feature requests, etc to
new issues as well?

Darren

--
The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE:
Pinpoint memory and threading errors before they happen.
Find and fix more than 250 security defects in the development cycle.
Locate bottlenecks in serial and parallel code that limit performance.
http://p.sf.net/sfu/intel-dev2devfeb
___
Matplotlib-devel mailing list
Matplotlib-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/matplotlib-devel

Re: [matplotlib-devel] git migration this weekend

2011-02-16 Thread Fernando Perez 
Hey,

On Wed, Feb 16, 2011 at 5:00 AM, Darren Dale  wrote:
>
> John, could you freeze the svn repo around noon on Friday? I'll
> convert the repositories and push them up to github on Saturday. Is it
> possible to close the sourceforge bugtracker, feature requests, etc to
> new issues as well?

are you guys planning on transfering the old bugs to github?  As I
mentioned, I have code lying around for the upload (and to download
from launchpad, but that's irrelevant here).  I'm going to be mosly
offline til Monday (conference trip), but if someone pings me on my
Berkeley email address, which I monitor even while traveling, I'll be
happy to help out.

Glad to see eveythong moving over to github! (since scipy is also
about to do the same, as soon as 0.9 is out, for which things are
already at the RC stage).

A huge thank you to Darren for putting so much hard work into this, I
admire your attention to detail (and I wish I'd been so thorough when
I transitioned ipython, where we could have recovered from some old
history problems, but I'm too lazy for that :).

Cheers,

f

--
The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE:
Pinpoint memory and threading errors before they happen.
Find and fix more than 250 security defects in the development cycle.
Locate bottlenecks in serial and parallel code that limit performance.
http://p.sf.net/sfu/intel-dev2devfeb
___
Matplotlib-devel mailing list
Matplotlib-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/matplotlib-devel

[matplotlib-devel] Patch for Bug ID: 3176823 plot_date does not respect timezone

2011-02-16 Thread Maximilian Trescher 
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Hi there,

I just created my first patch for matplotlib, it's addressing bug 3176823.

I send the patch with an example (as suggested in the faq).

You can see the effect in the example: before patching it ignores the tz
argument, and marks are set at 23:00. The example dates are at 23:00
o'clock in utc, but should be displayed as 0:00, because the exmaple
"lives" in timezone Europe/Berlin.

Hopefully i got this converter stuff right, i changed in
dates.DateConverter:

 def default_units(x, axis):
 'Return the default unit for *x* or None'
- -return None
+return x

and in axis.py i did


- -def axis_date(self):
+def axis_date(self, tz):
 """
 Sets up x-axis ticks and labels that treat the x data as dates.
+*tz* is the time zone to use in labeling dates.
 """
 import datetime
 # should be enough to inform the unit conversion interface
 # dates are comng in
- -self.update_units(datetime.date(2009,1,1))
+self.update_units(tz.localize(datetime.datetime(2009,1,1)))

so that now DateConverter.axisinfo can now something about timezones:

def axisinfo(unit, axis):
'return the unit AxisInfo'
 # make sure that the axis does not start at 0

- -majloc = AutoDateLocator(tz=unit)
- -majfmt = AutoDateFormatter(majloc, tz=unit)
+tz = None
+if getattr(unit, "tzinfo", None):
+tz = unit.tzinfo
+
+majloc = AutoDateLocator(tz=tz)
+majfmt = AutoDateFormatter(majloc, tz=tz)


cheers,
Maximilian

PS: sry, im not that used to writing mails in english
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iQEcBAEBAgAGBQJNXBWoAAoJEMxyzzlQGYxT/IwH/jyLsd5ldmzFUTjmV0qIaDdu
ct1B0/FbpGf2/F6+IyQxEoltYUXNpWwf4fzg/bdjBAd4CHaS1S0tOv7o6m9JHZDe
J6Eym9h1DmXVPkLJau4gdi1jZwTMpP94ac8wcHDqP39rXSiC/klRdXqpizccD2eP
9DbmgnePd61UQCYJchg9fBwIfSJg1iC7wpGuC51uLkyLT1P1ITDXbvSFH82zWtDU
hBCc8w54X7wlsDuCSejnibocIj251YhyG3cXbWrdw0+wTg+8L9mxglAo+TmCI2Nb
aOIYlQUunhBQkVRIG2qTKXmu6CDv1Sk1u1oxnEGeVXxVsJIbdLWxEPBb1jOjjJI=
=zRMW
-END PGP SIGNATURE-
#coding: utf-8
import matplotlib
matplotlib.use("Qt4Agg")

import matplotlib.pyplot as pyplot
import matplotlib.dates as dates
import datetime
import pytz

utc = pytz.utc
berlin = pytz.timezone("Europe/Berlin")

mydates = [datetime.datetime(2011,1,i, 0, 0) for i in range(1,4)]  #assume these dates are in berlin-timezone
berlindates = [berlin.localize(d) for d in mydates]

pyplot.plot_date(dates.date2num(berlindates), [1,2,3], xdate=True, ydate=False, tz=berlin)
#workaround before patch, to tell the formatter about timezone
#pyplot.gca().get_xaxis().set_major_formatter(dates.DateFormatter("%H",tz=berlin))
pyplot.show()
--
The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE:
Pinpoint memory and threading errors before they happen.
Find and fix more than 250 security defects in the development cycle.
Locate bottlenecks in serial and parallel code that limit performance.
http://p.sf.net/sfu/intel-dev2devfeb___
Matplotlib-devel mailing list
Matplotlib-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/matplotlib-devel

Re: [matplotlib-devel] git migration this weekend

2011-02-16 Thread Darren Dale 
On Wed, Feb 16, 2011 at 12:39 PM, Fernando Perez  wrote:
> are you guys planning on transfering the old bugs to github?

Probably at some point.

> As I
> mentioned, I have code lying around for the upload (and to download
> from launchpad, but that's irrelevant here).  I'm going to be mosly
> offline til Monday (conference trip), but if someone pings me on my
> Berkeley email address, which I monitor even while traveling, I'll be
> happy to help out.

Thanks, that would be very helpful. I'll follow up once I figure out
how to extract the information from sourceforge.

> Glad to see eveythong moving over to github! (since scipy is also
> about to do the same, as soon as 0.9 is out, for which things are
> already at the RC stage).
>
> A huge thank you to

Hang on, don't jinx it.

Darren

--
The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE:
Pinpoint memory and threading errors before they happen.
Find and fix more than 250 security defects in the development cycle.
Locate bottlenecks in serial and parallel code that limit performance.
http://p.sf.net/sfu/intel-dev2devfeb
___
Matplotlib-devel mailing list
Matplotlib-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/matplotlib-devel

Re: [matplotlib-devel] git migration this weekend

2011-02-16 Thread John Hunter 
On Wed, Feb 16, 2011 at 7:00 AM, Darren Dale  wrote:

> John, could you freeze the svn repo around noon on Friday? I'll
> convert the repositories and push them up to github on Saturday. Is it
> possible to close the sourceforge bugtracker, feature requests, etc to
> new issues as well?

I did some poking around and do not see an easy way to freeze the
repo.  I can disable it, but then I think it won't be available for
read access.  One thing I could do is remove commit privs for every
developer, making the repo read only going forward.  This seems like a
reasonable approach.

As for the tracker, similarly, I see how to disable it but not to
freeze it so that no new issues can be added.  Anyone seeing things
differently?

JDH

--
The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE:
Pinpoint memory and threading errors before they happen.
Find and fix more than 250 security defects in the development cycle.
Locate bottlenecks in serial and parallel code that limit performance.
http://p.sf.net/sfu/intel-dev2devfeb
___
Matplotlib-devel mailing list
Matplotlib-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/matplotlib-devel

Re: [matplotlib-devel] git migration this weekend

2011-02-16 Thread Eric Firing 
On 02/16/2011 08:38 AM, Darren Dale wrote:
> On Wed, Feb 16, 2011 at 12:39 PM, Fernando Perez  wrote:
>> are you guys planning on transfering the old bugs to github?
>
> Probably at some point.
>
>> As I
>> mentioned, I have code lying around for the upload (and to download
>> from launchpad, but that's irrelevant here).  I'm going to be mosly
>> offline til Monday (conference trip), but if someone pings me on my
>> Berkeley email address, which I monitor even while traveling, I'll be
>> happy to help out.
>
> Thanks, that would be very helpful. I'll follow up once I figure out
> how to extract the information from sourceforge.

Darren,

Just a heads-up on that: In November the tracker was heavily spammed. 
Recently I marked a few hundred items with the "delete" disposition, but 
I don't think that actually gets rid of them.  If it doesn't, then maybe 
they can be filtered out during the transfer.

Eric

>
>> Glad to see eveythong moving over to github! (since scipy is also
>> about to do the same, as soon as 0.9 is out, for which things are
>> already at the RC stage).
>>
>> A huge thank you to
>
> Hang on, don't jinx it.
>
> Darren
>
> --
> The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE:
> Pinpoint memory and threading errors before they happen.
> Find and fix more than 250 security defects in the development cycle.
> Locate bottlenecks in serial and parallel code that limit performance.
> http://p.sf.net/sfu/intel-dev2devfeb
> ___
> Matplotlib-devel mailing list
> Matplotlib-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/matplotlib-devel


--
The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE:
Pinpoint memory and threading errors before they happen.
Find and fix more than 250 security defects in the development cycle.
Locate bottlenecks in serial and parallel code that limit performance.
http://p.sf.net/sfu/intel-dev2devfeb
___
Matplotlib-devel mailing list
Matplotlib-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/matplotlib-devel

Re: [matplotlib-devel] git migration this weekend

2011-02-16 Thread Sandro Tosi 
On Wed, Feb 16, 2011 at 19:57, John Hunter  wrote:
> On Wed, Feb 16, 2011 at 7:00 AM, Darren Dale  wrote:
>
>> John, could you freeze the svn repo around noon on Friday? I'll
>> convert the repositories and push them up to github on Saturday. Is it
>> possible to close the sourceforge bugtracker, feature requests, etc to
>> new issues as well?
>
> I did some poking around and do not see an easy way to freeze the
> repo.  I can disable it, but then I think it won't be available for
> read access.  One thing I could do is remove commit privs for every
> developer, making the repo read only going forward.  This seems like a
> reasonable approach.

a pre-commit hook that just "exit 1" ? it prevents commits but not checkouts.

Just my 2c,
-- 
Sandro Tosi (aka morph, morpheus, matrixhasu)
My website: http://matrixhasu.altervista.org/
Me at Debian: http://wiki.debian.org/SandroTosi

--
The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE:
Pinpoint memory and threading errors before they happen.
Find and fix more than 250 security defects in the development cycle.
Locate bottlenecks in serial and parallel code that limit performance.
http://p.sf.net/sfu/intel-dev2devfeb
___
Matplotlib-devel mailing list
Matplotlib-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/matplotlib-devel

Re: [matplotlib-devel] git migration this weekend

2011-02-16 Thread Benjamin Root 
On Wed, Feb 16, 2011 at 1:30 PM, Sandro Tosi  wrote:

> On Wed, Feb 16, 2011 at 19:57, John Hunter  wrote:
> > On Wed, Feb 16, 2011 at 7:00 AM, Darren Dale  wrote:
> >
> >> John, could you freeze the svn repo around noon on Friday? I'll
> >> convert the repositories and push them up to github on Saturday. Is it
> >> possible to close the sourceforge bugtracker, feature requests, etc to
> >> new issues as well?
> >
> > I did some poking around and do not see an easy way to freeze the
> > repo.  I can disable it, but then I think it won't be available for
> > read access.  One thing I could do is remove commit privs for every
> > developer, making the repo read only going forward.  This seems like a
> > reasonable approach.
>
> a pre-commit hook that just "exit 1" ? it prevents commits but not
> checkouts.
>
> Just my 2c,
>

Even better, a pre-commit hook that also echos out a message stating where
to go.  And maybe a pre-update/pre-checkout hook that does something
similar?

Ben Root
--
The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE:
Pinpoint memory and threading errors before they happen.
Find and fix more than 250 security defects in the development cycle.
Locate bottlenecks in serial and parallel code that limit performance.
http://p.sf.net/sfu/intel-dev2devfeb___
Matplotlib-devel mailing list
Matplotlib-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/matplotlib-devel

Re: [matplotlib-devel] git migration this weekend

2011-02-16 Thread Michael Droettboom 

Not sure Sourceforge allows custom hooks in SVN.

Mike

On 02/16/2011 02:45 PM, Benjamin Root wrote:
On Wed, Feb 16, 2011 at 1:30 PM, Sandro Tosi > wrote:


On Wed, Feb 16, 2011 at 19:57, John Hunter mailto:jdh2...@gmail.com>> wrote:
> On Wed, Feb 16, 2011 at 7:00 AM, Darren Dale mailto:dsdal...@gmail.com>> wrote:
>
>> John, could you freeze the svn repo around noon on Friday? I'll
>> convert the repositories and push them up to github on
Saturday. Is it
>> possible to close the sourceforge bugtracker, feature requests,
etc to
>> new issues as well?
>
> I did some poking around and do not see an easy way to freeze the
> repo.  I can disable it, but then I think it won't be available for
> read access.  One thing I could do is remove commit privs for every
> developer, making the repo read only going forward.  This seems
like a
> reasonable approach.

a pre-commit hook that just "exit 1" ? it prevents commits but not
checkouts.

Just my 2c,


Even better, a pre-commit hook that also echos out a message stating 
where to go.  And maybe a pre-update/pre-checkout hook that does 
something similar?


Ben Root


--
The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE:
Pinpoint memory and threading errors before they happen.
Find and fix more than 250 security defects in the development cycle.
Locate bottlenecks in serial and parallel code that limit performance.
http://p.sf.net/sfu/intel-dev2devfeb


___
Matplotlib-devel mailing list
Matplotlib-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/matplotlib-devel


--
The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE:
Pinpoint memory and threading errors before they happen.
Find and fix more than 250 security defects in the development cycle.
Locate bottlenecks in serial and parallel code that limit performance.
http://p.sf.net/sfu/intel-dev2devfeb___
Matplotlib-devel mailing list
Matplotlib-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/matplotlib-devel

Re: [matplotlib-devel] git migration this weekend

2011-02-16 Thread John Hunter 
On Wed, Feb 16, 2011 at 2:47 PM, Michael Droettboom  wrote:
> Not sure Sourceforge allows custom hooks in SVN.

We have a couple in place already


https://sourceforge.net/project/admin/svn.php?group_id=80706

--
The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE:
Pinpoint memory and threading errors before they happen.
Find and fix more than 250 security defects in the development cycle.
Locate bottlenecks in serial and parallel code that limit performance.
http://p.sf.net/sfu/intel-dev2devfeb
___
Matplotlib-devel mailing list
Matplotlib-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/matplotlib-devel

Re: [matplotlib-devel] git migration this weekend

2011-02-16 Thread Michael Droettboom 
On 02/16/2011 03:53 PM, John Hunter wrote:
> On Wed, Feb 16, 2011 at 2:47 PM, Michael Droettboom  wrote:
>> Not sure Sourceforge allows custom hooks in SVN.
> We have a couple in place already
>
>
> https://sourceforge.net/project/admin/svn.php?group_id=80706
Yes.  But those aren't custom -- SF only provides a fixed set of scripts 
one can apply.  Notably, I don't think there's one that prevents further 
commits.

Mike

--
The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE:
Pinpoint memory and threading errors before they happen.
Find and fix more than 250 security defects in the development cycle.
Locate bottlenecks in serial and parallel code that limit performance.
http://p.sf.net/sfu/intel-dev2devfeb
___
Matplotlib-devel mailing list
Matplotlib-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/matplotlib-devel