[sage-support] Re: sxrange / xsrange possible bug

2009-09-22 Thread Minh Nguyen
Hi Mariah, On Tue, Sep 22, 2009 at 11:08 PM, Mariah wrote: > I respectfully suggest that this section be split out to a "How to > make > a Sage patch (for newbies)" ... or at the very least moved to the > beginning > of the Developers' Guide. This is now ticket #6987 http://trac.sagemath.or

[sage-support] Re: sxrange / xsrange possible bug

2009-09-22 Thread Mariah
Minh, > Tutorials, tips and techniques on making and managing patches should > go in the Developers' Guide at > > http://www.sagemath.org/doc/developer/ Aha! This already has the stuff I was going to write up. The reason that I never looked at this is that I do not consider myself a "developer

[sage-support] Re: sxrange / xsrange possible bug

2009-09-21 Thread Minh Nguyen
Hi Mariah, On Tue, Sep 22, 2009 at 12:26 AM, Mariah wrote: > Is there a "How to make a Sage patch (for newbies)" page anywhere? > If not, there should be. The sage-combinat team has a wiki page on using Mercurial for making patches: http://wiki.sagemath.org/combinat/MercurialStepByStep The

[sage-support] Re: sxrange / xsrange possible bug

2009-09-21 Thread Mariah
Dan, As you suggested, I took a look at the Mercurial website and quickly found that putting the following in my .hgrc file would make hg use my email address rather than 'mar...@localhost.localdomain' [ui] username = Mariah Lenox > You sound like you're pretty comfortable with the basic diff

[sage-support] Re: sxrange / xsrange possible bug

2009-09-16 Thread Dan Drake
On Wed, 16 Sep 2009 at 07:22AM -0700, Mariah wrote: > Note that the first time I did "$ hg ci" I had to edit the file > that my editor threw up to remove leading "HG" in some > lines. When I repeat the command, I now get > > No username found, using 'mar...@localhost.localdomain' instead > > I a

[sage-support] Re: sxrange / xsrange possible bug

2009-09-16 Thread Simon King
Hi Mariah, On 16 Sep., 15:29, Minh Nguyen wrote: [...] > Do you mean producing a proper patch file using Mercurial? If yes, > then you can use the Mercurial that's shipped with Sage like so. From > SAGE_ROOT, you can do something along the lines of the following > terminal session: > > [mv...@sa

[sage-support] Re: sxrange / xsrange possible bug

2009-09-16 Thread Robert Bradshaw
On Sep 16, 2009, at 7:22 AM, Mariah wrote: > Minh, > > Ok, how does the following look? Like what you want? > The date looks funny. > > > # HG changeset patch > # User mariah.le...@gmail.com > # Date 1253110290 14400 > # Node ID 299c98

[sage-support] Re: sxrange / xsrange possible bug

2009-09-16 Thread Mariah
Minh, Ok, how does the following look? Like what you want? The date looks funny. # HG changeset patch # User mariah.le...@gmail.com # Date 1253110290 14400 # Node ID 299c98688ef9ab55662e33f9b9e074de803de4c4 # Parent 684eea91ff224e5bc

[sage-support] Re: sxrange / xsrange possible bug

2009-09-16 Thread Minh Nguyen
Hi Mariah, On Wed, Sep 16, 2009 at 11:10 PM, Mariah wrote: > What I do not know how to do is to indicate that this is for the file > > sage-4.1.1/sage/misc/misc.py > > in > > spkg/standard/sage-4.1.1.spkg > > Is there a convention as to how to indicate this? Do you mean producing a proper

[sage-support] Re: sxrange / xsrange possible bug

2009-09-16 Thread Mariah
Second attempt. Embarrassing typo in my first attempt. - --- misc.py.orig        2009-09-15 16:25:22.983553000 -0400 +++ misc.py     2009-09-15 16:28:47.335875000 -0400 @@ -1001,8 +1001,8 @@      .. note

[sage-support] Re: sxrange / xsrange possible bug

2009-09-16 Thread Mariah
William, > The file misc.py has this line: > > sxrange = xsrange Ah, yes. I should have looked at the source code. Apologies. > Any chance you could post a patch with a statement that they are > aliases added to the docs? How about: --

[sage-support] Re: sxrange / xsrange possible bug

2009-09-15 Thread William Stein
On Tue, Sep 15, 2009 at 11:38 AM, Robert Bradshaw wrote: > On Sep 15, 2009, at 11:28 AM, William Stein wrote: > >> You might have some thought about this... at least I think it might be >> caused by your optimizations to [a..b].  This is really a question from ccr, >> by the way... >> >> Forwarde

[sage-support] Re: sxrange / xsrange possible bug

2009-09-15 Thread William Stein
On Tue, Sep 15, 2009 at 10:53 AM, Mariah Lenox wrote: > > Perhaps I do not understand sxrange / xsrange correctly.  The > reference manual entries for them seem to be similar.  Is > there a difference?  (If one is just an alias for the other, > it would be best to say so. If they are different, t