Sorry -- I was too thick to get the reference. Maybe if you had
included a cute picture of a kitten eating a cheeseburger or riding and
invisible bicycle or something... This list needs more of those ;)
Cheers,
Mike
Tom Holroyd wrote:
> Sorry, I just don't like that word. And the "UR ..." was
Sorry, I just don't like that word. And the "UR ..." was a lame
reference to LOL Cats. :-) Sorry, sorry, I'll go away now.
P.S. I love matplotlib.
On Tue, 2008-01-08 at 22:53 +0100, Gael Varoquaux wrote:
> On Tue, Jan 08, 2008 at 04:49:00PM -0500, Michael Droettboom wrote:
> > I don't think "UR DO
On Tue, Jan 08, 2008 at 04:49:00PM -0500, Michael Droettboom wrote:
> I don't think "UR DOIN IT WRONG" is an entirely correct assessment,
> however. Much of this change can be considered refactoring wrt to the
> high-level public API.
Refactoring is often defined (in test driven development) a
On Jan 8, 2008 1:49 PM, Michael Droettboom <[EMAIL PROTECTED]> wrote:
> Thank you for enlightening us. This overloaded and contentious word
> will be replaced.
BTW Michael, ready to go when you are
JDH
-
Check out the new S
Thank you for enlightening us. This overloaded and contentious word
will be replaced.
I don't think "UR DOIN IT WRONG" is an entirely correct assessment,
however. Much of this change can be considered refactoring wrt to the
high-level public API. For instance, I believe basemap only had to
UR DOIN IT WRONG
http://en.wikipedia.org/wiki/Refactoring
On Tue, 2008-01-08 at 10:48 -0800, John Hunter wrote:
> To check out the trunk with the latest transforms refactoring:
The word refactoring applies to cases of code cleanup and so on.
Refactoring implies functional equivalence.
Dr. Tom
On Mon, 07 Jan 2008 19:54:38 -1000
Eric Firing <[EMAIL PROTECTED]> wrote:
> Andrew Straw wrote:
> > Something I haven't seen addressed on the numpy list (or here) is
> > using hg or bzr to mirror an svn repository. What would be the
> > added advantage to the project of using a DVCS if all the
> >
On Jan 8, 2008 8:11 AM, Michael Droettboom <[EMAIL PROTECTED]> wrote:
> Also -- we probably want a news item to say something like this:
I just added MIGRATION.txt to the trunk -- after you do the merge, we
can post this document to provide the migration instructions. I've
tried to add all your t
Also -- we probably want a news item to say something like this:
The experimental transforms refactoring changes have been merged into
SVN trunk. While this version is passing all examples and unit tests,
there may be changes that subtly break things that used to work, raise
nasty except
John Hunter wrote:
> Michael, since you know more about this than anyone, you should
> probably spearhead the svn reorganization and let people know when the
> changes become effective with some advance notice. I will update the
> website with pointers to the relevant docs (your API_CHANGES and
>
John Hunter wrote:
> On Jan 7, 2008 2:37 PM, Eric Firing <[EMAIL PROTECTED]> wrote:
>
>> (At the moment I can't compile the branch--I just sent Mike a message
>> about that off the list, with voluminous output.)
>>
>> It seems like what is needed is not exactly a merge operation but simply
>> a
John Hunter wrote:
[...]
> Michael, how onerous was it for you to do the merges using svn -- this
> seems to be the most significant problem with svn in my reading of
> David's summary.
Here is a new thread related to merging, and the difference between svn
and a DVCS:
http://www.mail-archive.c
Andrew Straw wrote:
> Something I haven't seen addressed on the numpy list (or here) is using
> hg or bzr to mirror an svn repository. What would be the added advantage
> to the project of using a DVCS if all the DVCS-ophiles would simply sync
> the svn tree?
There has been numpy discussion of
Something I haven't seen addressed on the numpy list (or here) is using
hg or bzr to mirror an svn repository. What would be the added advantage
to the project of using a DVCS if all the DVCS-ophiles would simply sync
the svn tree?
Eric Firing wrote:
> John Hunter wrote:
>> On Jan 7, 2008 2:37
John Hunter wrote:
> On Jan 7, 2008 2:37 PM, Eric Firing <[EMAIL PROTECTED]> wrote:
[...]
>> All this brings to mind the discussion taking place over the last week
>> on the numpy list regarding switching from svn to bzr or hg.
>> http://thread.gmane.org/gmane.comp.python.numeric.general/18130
>>
On Jan 7, 2008 2:37 PM, Eric Firing <[EMAIL PROTECTED]> wrote:
> (At the moment I can't compile the branch--I just sent Mike a message
> about that off the list, with voluminous output.)
>
> It seems like what is needed is not exactly a merge operation but simply
> a renaming of the trunk and the
John et al.,
(At the moment I can't compile the branch--I just sent Mike a message
about that off the list, with voluminous output.)
It seems like what is needed is not exactly a merge operation but simply
a renaming of the trunk and the branch. Maybe some doc files need to be
merged, but tha
Now that the 0.91.2 release is out, I am inclined to merge Michael's
transforms branch into the trunk. Since many people rely on svn, we
probably need to advertise this move broadly, with a news item on the
web page and announcements on the mailing lists, with instructions on
how to checkout the
18 matches
Mail list logo
