SourceForge logo
SourceForge logo
Menu

matplotlib-devel — matplotlib developers

You can subscribe to this list here.

2003 Jan
Feb
Mar
Apr
May
Jun
Jul
Aug
Sep
Oct
(1)
Nov
(33)
Dec
(20)
2004 Jan
(7)
Feb
(44)
Mar
(51)
Apr
(43)
May
(43)
Jun
(36)
Jul
(61)
Aug
(44)
Sep
(25)
Oct
(82)
Nov
(97)
Dec
(47)
2005 Jan
(77)
Feb
(143)
Mar
(42)
Apr
(31)
May
(93)
Jun
(93)
Jul
(35)
Aug
(78)
Sep
(56)
Oct
(44)
Nov
(72)
Dec
(75)
2006 Jan
(116)
Feb
(99)
Mar
(181)
Apr
(171)
May
(112)
Jun
(86)
Jul
(91)
Aug
(111)
Sep
(77)
Oct
(72)
Nov
(57)
Dec
(51)
2007 Jan
(64)
Feb
(116)
Mar
(70)
Apr
(74)
May
(53)
Jun
(40)
Jul
(519)
Aug
(151)
Sep
(132)
Oct
(74)
Nov
(282)
Dec
(190)
2008 Jan
(141)
Feb
(67)
Mar
(69)
Apr
(96)
May
(227)
Jun
(404)
Jul
(399)
Aug
(96)
Sep
(120)
Oct
(205)
Nov
(126)
Dec
(261)
2009 Jan
(136)
Feb
(136)
Mar
(119)
Apr
(124)
May
(155)
Jun
(98)
Jul
(136)
Aug
(292)
Sep
(174)
Oct
(126)
Nov
(126)
Dec
(79)
2010 Jan
(109)
Feb
(83)
Mar
(139)
Apr
(91)
May
(79)
Jun
(164)
Jul
(184)
Aug
(146)
Sep
(163)
Oct
(128)
Nov
(70)
Dec
(73)
2011 Jan
(235)
Feb
(165)
Mar
(147)
Apr
(86)
May
(74)
Jun
(118)
Jul
(65)
Aug
(75)
Sep
(162)
Oct
(94)
Nov
(48)
Dec
(44)
2012 Jan
(49)
Feb
(40)
Mar
(88)
Apr
(35)
May
(52)
Jun
(69)
Jul
(90)
Aug
(123)
Sep
(112)
Oct
(120)
Nov
(105)
Dec
(116)
2013 Jan
(76)
Feb
(26)
Mar
(78)
Apr
(43)
May
(61)
Jun
(53)
Jul
(147)
Aug
(85)
Sep
(83)
Oct
(122)
Nov
(18)
Dec
(27)
2014 Jan
(58)
Feb
(25)
Mar
(49)
Apr
(17)
May
(29)
Jun
(39)
Jul
(53)
Aug
(52)
Sep
(35)
Oct
(47)
Nov
(110)
Dec
(27)
2015 Jan
(50)
Feb
(93)
Mar
(96)
Apr
(30)
May
(55)
Jun
(83)
Jul
(44)
Aug
(8)
Sep
(5)
Oct
Nov
(1)
Dec
(1)
2016 Jan
Feb
Mar
(1)
Apr
May
Jun
(2)
Jul
Aug
(3)
Sep
(1)
Oct
(3)
Nov
Dec
2017 Jan
Feb
(5)
Mar
Apr
May
Jun
Jul
(3)
Aug
Sep
(7)
Oct
Nov
Dec
2018 Jan
Feb
Mar
Apr
May
Jun
Jul
(2)
Aug
Sep
Oct
Nov
Dec
S M T W T F S






1
2
(9)
3
(16)
4
(8)
5
(41)
6
(13)
7
(1)
8
(2)
9
(1)
10
(3)
11
(4)
12
(6)
13
(9)
14
(3)
15
(1)
16
17
(8)
18
(11)
19
(3)
20
(9)
21
(6)
22
(13)
23
(9)
24
(10)
25
(6)
26
(9)
27
(9)
28
(11)
29
(4)
30
(3)
31
(7)





Showing 6 results of 6

From: Darren D. <dsd...@gm...> - 2011年01月25日 23:39:04
On Tue, Jan 25, 2011 at 6:12 PM, Darren Dale <dsd...@gm...> wrote:
> There is still an outstanding issue that must be taken care of before
> we migrate. The conversion routines create a basemap repository out of
> trunk/toolkits/basemap, and matplotlib repository out of
> trunk/matplotlib. Still, the matplotlib repo (at
> github.com/darrendale/matplotlib) is over 200 MB. One can search the
> objects in the large packfile, and find that there are still
> references to basemap data in the matplotlib repo. I don't know how it
> got in there, nor how to remove it.
I went through the exercise of identifying the largest blob, as
described near the end of http://progit.org/book/ch9-7.html :
$ git verify-pack -v
objects/pack/pack-fa44ca56d7ec3964e562494f2fe08203143074bd.idx | sort
-k 3 -n | tail -3
3b8b6c010f8ce59afac1e811b1bbc3efc21b770a blob 9154481 9089827 62749144
6328b70e665b58ed7f5aa1e110418cbb3facc07a blob 9331200 94297 156884507
f784efc1518b10dff33673ad9a7a1ac3a7d107d5 blob 51399604 14333430 162328624
$ git rev-list --objects --all | grep f784efc1518b10dff
f784efc1518b10dff33673ad9a7a1ac3a7d107d5 toolkits/basemap/data/gshhs_h.txt
This shell script is supposed to identify which commits have that blob
in their tree (http://stackoverflow.com/questions/223678/git-which-commit-has-this-blob):
---
#!/bin/sh
obj_name="1ドル"
shift
git log "$@" --pretty=format:'%T %h %s' \
| while read tree commit subject ; do
 if git ls-tree -r $tree | grep -q "$obj_name" ; then
 echo $commit "$subject"
 fi
done
---
but it comes up empty, so now I'm stuck. Any ideas would be greatly appreciated.
From: Darren D. <dsd...@gm...> - 2011年01月25日 23:12:43
On Tue, Jan 25, 2011 at 3:06 PM, Darren Dale <dsd...@gm...> wrote:
> On Tue, Jan 25, 2011 at 1:31 PM, Pauli Virtanen <pa...@ik...> wrote:
>> 2011年1月25日 12:19:37 -0500, Darren Dale wrote:
>>> There is a potential problem converting the entire basemap history to
>>> git. In svn commit 4418, trunk/toolkits had basemap and basemap-testing
>>> directories. In commit 4419, basemap was renamed basemap-0.9.6.1, so
>>> there was only basemap-0.9.6.1 and basemap-testing. In commit 4420,
>>> basemap-testing is renamed basemap. The git history only goes back as
>>> far as svn4420, it looks like the conversion routines get confused by
>>> the temporary absence of the basemap directory.
>>>
>>> I'm trying to find a workaround, but if I can't... ?
>>
>> You can maybe do it like this:
>>
>> 1) Write matplotlib.rules so that all of the directories where basemap
>> stuff has been ends in the basemap repository. (I'm assuming this does
>> not error out...)
>
> Aha! I thought I had tried that. Thanks.
>
>> 2) This will create a number of separate heads in the basemap repo that
>> do not share common history.
>>
>> 3) Add graft rules in matplotlib.grafts to stitch the disconnected
>> history graphs together.
>
> Mercifully, the latest checkout of svn2git seems to take care of that.
> I've developed a wicked headache.
>
> Jeff, the repository is temporarily available at
> https://github.com/darrendale/basemap . It would be really helpful if
> you would have a look at the network graph at
> https://github.com/darrendale/basemap/network to make sure there are
> no surprises, maybe clone the repository and check that the working
> directory is identical to your svn checkout.
There is still an outstanding issue that must be taken care of before
we migrate. The conversion routines create a basemap repository out of
trunk/toolkits/basemap, and matplotlib repository out of
trunk/matplotlib. Still, the matplotlib repo (at
github.com/darrendale/matplotlib) is over 200 MB. One can search the
objects in the large packfile, and find that there are still
references to basemap data in the matplotlib repo. I don't know how it
got in there, nor how to remove it.
Jeff: was there ever any basemap data committed directly to trunk/matplotlib?
Pauli: could I trouble you to have a look at my rules file, maybe you
will notice something I overlooked?
(https://github.com/darrendale/mpl2git/blob/master/matplotlib.rules)
Any other ideas?
Thanks
Darren
From: Darren D. <dsd...@gm...> - 2011年01月25日 20:06:29
On Tue, Jan 25, 2011 at 1:31 PM, Pauli Virtanen <pa...@ik...> wrote:
> 2011年1月25日 12:19:37 -0500, Darren Dale wrote:
>> There is a potential problem converting the entire basemap history to
>> git. In svn commit 4418, trunk/toolkits had basemap and basemap-testing
>> directories. In commit 4419, basemap was renamed basemap-0.9.6.1, so
>> there was only basemap-0.9.6.1 and basemap-testing. In commit 4420,
>> basemap-testing is renamed basemap. The git history only goes back as
>> far as svn4420, it looks like the conversion routines get confused by
>> the temporary absence of the basemap directory.
>>
>> I'm trying to find a workaround, but if I can't... ?
>
> You can maybe do it like this:
>
> 1) Write matplotlib.rules so that all of the directories where basemap
> stuff has been ends in the basemap repository. (I'm assuming this does
> not error out...)
Aha! I thought I had tried that. Thanks.
> 2) This will create a number of separate heads in the basemap repo that
> do not share common history.
>
> 3) Add graft rules in matplotlib.grafts to stitch the disconnected
> history graphs together.
Mercifully, the latest checkout of svn2git seems to take care of that.
I've developed a wicked headache.
Jeff, the repository is temporarily available at
https://github.com/darrendale/basemap . It would be really helpful if
you would have a look at the network graph at
https://github.com/darrendale/basemap/network to make sure there are
no surprises, maybe clone the repository and check that the working
directory is identical to your svn checkout.
Darren
From: Pauli V. <pa...@ik...> - 2011年01月25日 18:31:34
2011年1月25日 12:19:37 -0500, Darren Dale wrote:
> There is a potential problem converting the entire basemap history to
> git. In svn commit 4418, trunk/toolkits had basemap and basemap-testing
> directories. In commit 4419, basemap was renamed basemap-0.9.6.1, so
> there was only basemap-0.9.6.1 and basemap-testing. In commit 4420,
> basemap-testing is renamed basemap. The git history only goes back as
> far as svn4420, it looks like the conversion routines get confused by
> the temporary absence of the basemap directory.
> 
> I'm trying to find a workaround, but if I can't... ?
You can maybe do it like this:
1) Write matplotlib.rules so that all of the directories where basemap 
stuff has been ends in the basemap repository. (I'm assuming this does 
not error out...)
2) This will create a number of separate heads in the basemap repo that 
do not share common history.
3) Add graft rules in matplotlib.grafts to stitch the disconnected 
history graphs together.
This happened also with Numpy: part of the old history had a this sort of 
a rename and so part of the history was not connected to the main graph. 
So I just stitched the graphs together manually.
-- 
Pauli Virtanen
From: Darren D. <dsd...@gm...> - 2011年01月25日 17:19:52
There is a potential problem converting the entire basemap history to
git. In svn commit 4418, trunk/toolkits had basemap and
basemap-testing directories. In commit 4419, basemap was renamed
basemap-0.9.6.1, so there was only basemap-0.9.6.1 and
basemap-testing. In commit 4420, basemap-testing is renamed basemap.
The git history only goes back as far as svn4420, it looks like the
conversion routines get confused by the temporary absence of the
basemap directory.
I'm trying to find a workaround, but if I can't... ?
From: Sandro T. <mo...@de...> - 2011年01月25日 17:03:30
Sorry it was my fault: /dev/shm was not mounted in the chroot where I
built the package so multiprocessing wasn't able to create semaphores.
It's building fine now.
On Thu, Jan 20, 2011 at 22:58, Sandro Tosi <mo...@de...> wrote:
> Hi all,
> I'm fighting against this weirdness since some days: if I build mpl
> debian package on my system, it builds normally, but if I build the
> package in a clean chroot it fails, and I only noticed because I want
> to create a link in doc/build/html/_static dir, that's missing. and
> I'm wondering why! I can't seem to find a clear answer to that, so I'm
> asking for any advice yo might have.
>
> The full log of the package build in the chroot is at [1] (it's quite
> large expanded); at the end of the file there are some ls -lR to try
> to identify what's going wrong.
>
> [1] http://people.debian.org/~morph/matplotlib_1.0.1-1_amd64.build.bz2
>
> Thanks in advance,
> --
> Sandro Tosi (aka morph, morpheus, matrixhasu)
> My website: http://matrixhasu.altervista.org/
> Me at Debian: http://wiki.debian.org/SandroTosi
>
-- 
Sandro Tosi (aka morph, morpheus, matrixhasu)
My website: http://matrixhasu.altervista.org/
Me at Debian: http://wiki.debian.org/SandroTosi

Showing 6 results of 6

Want the latest updates on software, tech news, and AI?
Get latest updates about software, tech news, and AI from SourceForge directly in your inbox once a month.
Thanks for helping keep SourceForge clean.
X





Briefly describe the problem (required):
Upload screenshot of ad (required):
Select a file, or drag & drop file here.
Screenshot instructions:

Click URL instructions:
Right-click on the ad, choose "Copy Link", then paste here →
(This may not be possible with some types of ads)

More information about our ad policies

Ad destination/click URL:

AltStyle によって変換されたページ (->オリジナル) /