On Tue, Jul 20, 2010 at 7:43 PM, John Hunter wrote:
>
> The major issues I am aware of are:
>
> * what do to about all the various subdirs of the mpl trunk
> (trunk/toolkits/basemap, trunk/sample_data, etc..). An svn commit to
> one tags all with a unique revision number. In git, how do we
> syn
> Yes, but there is a *lot* more involved in making the transition than
> just creating a git replica of the svn trunk.
Granted, and I'm probably forgetting many of them. So it is probably
a good idea for us to enumerate them here as a checklist when we do
migrate.
The major issues I am aware of
Howdy,
On Tue, Jul 20, 2010 at 11:48 AM, Eric Firing wrote:
>
> Although I would like the transition to occur soon, it might make sense
> to let the numpy people do it first so that we can take maximum
> advantage of their systematic approach. I don't know how much of a
> delay that would entail
On 07/20/2010 08:59 AM, Ryan May wrote:
> On Tue, Jul 20, 2010 at 1:48 PM, Eric Firing wrote:
>> On 07/20/2010 08:30 AM, Darren Dale wrote:
>>> On Tue, Jul 20, 2010 at 12:33 PM, Michael Droettboom
>>> wrote:
We've seen this before. It seems to have to do with files that were
created
On Tue, Jul 20, 2010 at 1:48 PM, Eric Firing wrote:
> On 07/20/2010 08:30 AM, Darren Dale wrote:
>> On Tue, Jul 20, 2010 at 12:33 PM, Michael Droettboom wrote:
>>> We've seen this before. It seems to have to do with files that were
>>> created after the branching. While I haven't found a soluti
On 07/20/2010 08:30 AM, Darren Dale wrote:
> On Tue, Jul 20, 2010 at 12:33 PM, Michael Droettboom wrote:
>> We've seen this before. It seems to have to do with files that were
>> created after the branching. While I haven't found a solution, it's
>> been going on a long time and seems to be beni
On Tue, Jul 20, 2010 at 12:33 PM, Michael Droettboom wrote:
> We've seen this before. It seems to have to do with files that were
> created after the branching. While I haven't found a solution, it's
> been going on a long time and seems to be benign.
Ok, thanks.
> (And, yeah, making the leap
We've seen this before. It seems to have to do with files that were
created after the branching. While I haven't found a solution, it's
been going on a long time and seems to be benign.
(And, yeah, making the leap to a DVCS would probably not be a bad
"solution" to this problem.)
Mike
On 07
Hello,
The documentation for hist seems to indicate that you should be able
to send a list of values through the 'weights' parameter in axes.hist,
and this worked in previous versions. In 1.0, however, this produces
an error. I've attached a diff (also pasted below) that I believe
produces the e
I am following the instructions in the coding guide to commit a change
on the maintenance branch, and merge that change into the trunk. I am
getting a bunch of unexpected property changes, so I interrupted the
commit. Is it ok to go ahead and let this finish?:
[~/Projects/matplotlib]
dar...@waterh
10 matches
Mail list logo
