nges back...)
The "official" version of the plot directive should IMO end up either
in Sphinx or matplotlib repository. It's probably OK to require matplotlib
SVN version to build Scipy docs for a while...
What do you think?
--
Pauli Virtanen
d is the output file handling,
and to check that the output is similar as previously for the matplotlib
docs.
--
Pauli Virtanen
--
Open Source Business Conference (OSBC), March 24-25, 2009, San Francisco, CA
-OSBC tackl
dvertisement. We can of course
still do this and revive the idea; it would be good to get a slightly
bigger starting mass, though.
--
Pauli Virtanen
--
Open Source Business Conference (OSBC), March 24-25, 2009, San Fran
if issubclass(axes_class, maxes.Axes):
axes_class_args = {}
else:
axes_class, axes_class_args = axes_class
--
Pauli Virtanen
--
Come build with us! The BlackBerry(R) Develop
Hi!
ti, 2009-10-27 kello 15:36 -0400, Jae-Joon Lee kirjoitti:
> Thanks for your suggestion and the patch.
> However, I'm not very inclined to make such a change any time soon,
> since that custom axes class is one of my primary motivation
> (supporting the cuvelinear grid) behind the axes_grid too
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 stitche
Wed, 26 Jan 2011 13:37:59 +0900, Jae-Joon Lee wrote:
[clip]
> I spend an hour to figure out how we can delete these unreachable
> objects. But it turned out that the answer seems to be simple.
>
> $ git repack -ad
The complete magic stanza is:
git reflog expire --expire=0 --all
git prune
git rep
Wed, 26 Jan 2011 20:35:03 +0900, Jae-Joon Lee wrote:
> On Wed, Jan 26, 2011 at 7:28 PM, Pauli Virtanen
> wrote:
>> The complete magic stanza is:
>>
>> git reflog expire --expire=0 --all
>> git prune
>> git repack -f -a -d
>> git gc --prune=0
>
>
;d also suggest eyeballing the "gitk --all" DAG.
--
Pauli Virtanen
--
Special Offer-- Download ArcSight Logger for FREE (a $49 USD value)!
Finally, a world-class log management solution at an even better price-f
(by definition,
stuff under refs/heads). However, there's also other stuff under refs/:
tags and hidden branches. Especially the postprocess.sh script hides
some branches.
To see all that is there, check the output from
git for-e
ay:
since rewriting changes the hashes of all following commits, you end up
with incompatible histories otherwise.
After that, I get down to 34 MB.
--
Pauli Virtanen
--
Special Offer-- Download ArcSight Logger for FREE
On Fri, 28 Jan 2011 14:00:40 -0600, John Hunter wrote:
[clip]
> The first good svn version is apparently 541; the prior commit 540 had
> the log message "reorganizes py code". This was when we moved
> "matplotlib" to "lib/matplotlib" which I thought svn would handle
> gracefully. Any gurus have an
uot; || echo "Wrong cvsroot..."
mkdir imported
cd imported
git cvsimport matplotlib
This at least shows some files in the first revisions. You can probably
then just graft the two histories together at a suitable point.
Apparently, it also needs some use of "git
not seem to occur often in practice).
--
Pauli Virtanen
--
Free Software Download: Index, Search & Analyze Logs and other IT data in
Real-Time with Splunk. Collect, index and harness all the fast moving IT data
ge
On Tue, 17 May 2011 16:14:53 -0400, Michael Droettboom wrote:
> Darned if I know what I did differently that time. (I'm sure I hit
> git's "misunderstanding" feature again).
>
> It only seems to have affected 2 or 3 of the pull requests -- I suspect
> rebasing those branches off of the current ma
he merge
history...
... and, apparently, the Github UI (but not Git itself) gets confused
in some cases as to what's new in a branch.
--
Pauli Virtanen
--
What Every C/C++ and Fortran developer Should Know!
Read thi
On Fri, 27 May 2011 07:29:15 -1000, Eric Firing wrote:
[clip]
> I wouldn't worry about it. It seems likely that other things from
> master did leak into v1.0.x, but at this point I don't think it matters.
> v1.0.x and master both build and run (or did last time I checked).
> The division between t
On Fri, 27 May 2011 09:51:37 -1000, Eric Firing wrote:
[clip]
> Nice--but what exactly is the meaning of "left" and "right"?
When you write
git checkout this-branch
git merge other-branch
the left parent of the new merge commit is `this-branch` and
the right one is `other-branch`
Thu, 02 Jun 2011 17:48:55 -0400, Darren Dale wrote:
[clip]
> * "git reset --hard 0e6dad5230"
> * redo pull request 103
> * cherry-pick the following commits off of the v1.0.x branch:
> - 069c21d
> - 53f8139e
> - de18d9ab2
> - 91e7d980
> - 0cc213b4fa
> - e7f1e83ace
> - 5c968a0ecdd
>
>
29.09.2011 17:38, Benjamin Root kirjoitti:
[clip]
> but I cannot use "d=np.concatenate(d,np.array(np.nan))" to finish this job.
[clip]
Do
d = np.concatenate([d, np.array([np.nan])])
or
d = np.hstack([d, np.nan])
or
d = np.r_[d, np.nan]
---
20 matches
Mail list logo
