Re: [matplotlib-devel] git migration

Hi, On Tue, Mar 2, 2010 at 10:17 PM, william ratcliff wrote: > I think there's a legal reason for the embargo--sourceforge apparently also > has such a policy: > http://sourceforge.net/blog/clarifying-sourceforgenets-denial-of-site-access-for-certain-persons-in-accordance-with-us-law/ > So, as a

Re: [matplotlib-devel] git migration

I think there's a legal reason for the embargo--sourceforge apparently also has such a policy: http://sourceforge.net/blog/clarifying-sourceforgenets-denial-of-site-access-for-certain-persons-in-accordance-with-us-law/

Re: [matplotlib-devel] git migration

Eric Firing wrote: > All, > > I think the git migration deserves its own thread on the devel list, so > here is a start. Explanation: the last bit of discussion was actually off-list, but because it was tacked onto a matplotlib-users list thread, and appeared there in my mailer, I failed to no

Re: [matplotlib-devel] git migration

Andrew Straw wrote: [...] > This is a good point. My preferred option is that we jettison all the > stuff that is not going to be shipped with MPL 1.0 from the git repo. > (More correctly - we build a git repo without that stuff ever going in.) > We can keep the old svn tree around and migrate the

Re: [matplotlib-devel] git migration

On Tue, Mar 2, 2010 at 11:03 PM, Matthew Brett wrote: > Hi, > > > Apart from being inflammatory, has anyone considered code.google.com(GC) as > > a solution? > > ;) - speaking as someone with no right to offer an opinion - please, > no. Google blocks Cuba from google code completely, for no obv

Re: [matplotlib-devel] git migration

Hi, > Apart from being inflammatory, has anyone considered code.google.com (GC) as > a solution? ;) - speaking as someone with no right to offer an opinion - please, no. Google blocks Cuba from google code completely, for no obvious reason, and a) that seems to me quite wrong and outside the s

Re: [matplotlib-devel] git migration

On Tue, Mar 2, 2010 at 9:17 PM, Andrew Straw wrote: > Eric Firing wrote: > > All, > > > > I think the git migration deserves its own thread on the devel list, so > > here is a start. > > > To the uninitiated - a decision is being made that MPL is moving to git > and github. We hope that this move

Re: [matplotlib-devel] git migration

Eric Firing wrote: > All, > > I think the git migration deserves its own thread on the devel list, so > here is a start. > To the uninitiated - a decision is being made that MPL is moving to git and github. We hope that this move will foster greater contributions from the community and a blurri

[matplotlib-devel] git migration

All, I think the git migration deserves its own thread on the devel list, so here is a start. The full svn repo includes much more than just matplotlib: also course, htdocs, py4science, sample_data, sampledoc_tut, scipy06, toolkits, and users_guide. Before moving matplotlib, I think we should

Re: [matplotlib-devel] Cannot import ft2font on Mac OSX

I followed your instructions and re-built, and I get the same error. I also ran "nm ft2font.so" and I get results that look like this: U _FT_Attach_File U _FT_Done_Face U _FT_Done_FreeType U _FT_Done_Glyph U _FT_G

[matplotlib-devel] Cannot import ft2font on Mac OSX

Using the svn build from 2-25: matplotlib.__version__ = 1.0.svn Python from Enthought: Python 2.6.4 -- EPD 6.0.0 (64-bit) I get the following errors when I try to import ft2font: Traceback (most recent call last): File "./testme.py", line 3, in from matplotlib import ft2font ImportError: dlopen(/

Re: [matplotlib-devel] Current svn version bug in get_xydata function in line.py

On Tue, Mar 2, 2010 at 7:07 AM, David Trem wrote: > Hi, > >  There is a typo in the matplotlib line.py file in function get_xydata > line 662 > it should be self._invalidx instead of self.invalidx > (missing leading underscore) > Fixed in svn r8170. Thanks for the report. JDH -

[matplotlib-devel] Current svn version bug in get_xydata function in line.py

Hi, There is a typo in the matplotlib line.py file in function get_xydata line 662 it should be self._invalidx instead of self.invalidx (missing leading underscore) Regards, David -- Download Intel® Parallel Studio Eva