On 2011-10-25 02:33, Dan Drake wrote:
It seems like no one wants to have an epic break-all-patches-in-trac
patch that removes all the trailing whitespace in the Sage library --
and, some people like some trailing whitespace, so perhaps we should
also add just a warning to the sage-merge script
On Tue, 25 Oct 2011 at 08:37AM +0200, Jeroen Demeyer wrote:
The following would be easy for me to do: remove all *newly added*
trailing whitespace from patches (except on lines consisting only of
spaces). Basically, s/^\(+.*[^ ]\) *$/\1/ in the patches.
I think that would be a good idea,
Unfortunately, the original thread expired, so I have to start a new
one. Here is the original:
http://groups.google.com/group/sage-devel/browse_thread/thread/81884a53ab28212/58ad9417b01ed46f?lnk=gstq=units#58ad9417b01ed46f
and some more ideas are here:
Thanks a lot. For some reason I can only open it as root now, but that
is a different story (it seems that the sudo was carried on, I did not
explicitely tell it that I wasn't sudoing anymore). What idiocy
Anyways, if I do that, it works. Thanks a lot.
On 10/24/2011 05:53 PM, leif wrote:
Of course now it works. Thanks a lot. I hope many will find your reply
when trying to install it on Ubuntu 11.10 until the new version is
released. At least my thread title should attract plenty of googling.
Manuel
On Oct 24, 5:53 pm, leif not.rea...@online.de wrote:
On 24 Okt., 16:32, Manuel
On 2011-10-25 09:51, Dan Drake wrote:
I think that would be a good idea, although if you're just running that
through sed, the exact patches applied would be different from the ones
on the trac server, which would cause some confusion.
Very true, but I think that is only a minor annoyance.
On Tue, Oct 25, 2011 at 01:53:31AM -0400, daly wrote:
diff has options to deal with whitespace.
-b --ignore-space-change
-w --ignore-all-space
I'm well aware of that... Mercurial has some extension as well... Or else, I
can rewrite a script to do it... The question is:
- is there a simple
The sage-combinat project is mostly hosted at
http://wiki.sagemath.org/combinat , and parts are constantly merged into
sage. There is also the sage-combinat-devel group.
--
To post to this group, send an email to sage-devel@googlegroups.com
To unsubscribe from this group, send an email to
Hi all,
I am trying to add some Sage examples to my lecture notes for a course
in Commutative Algebra. In particular want to include an example on
how to define the power set ring in sage. I would like to list some
big chunks of sage code with nice colorization and all, so I was
trying to use the
On Monday 24 October 2011, Jason Grout wrote:
Over on the zeromq mailing list, there was a post about running zeromq
through tcpcrypt [1]. This seems like a good idea for our single-cell
server, which uses zeromq to communicate between server and workers. It
also seems like it might be nice
On 10/25/11 10:40 AM, Martin Albrecht wrote:
Jason asked me off list to jump in because I work in crypto. Btw. I am
actually don't work in network security so I am not really an expert on the
matter. But for what it's worth, I have never heard of the protocol.
I took a quick look at the website
On Tuesday 25 October 2011, Jason Grout wrote:
On 10/25/11 10:40 AM, Martin Albrecht wrote:
Jason asked me off list to jump in because I work in crypto. Btw. I am
actually don't work in network security so I am not really an expert on
the matter. But for what it's worth, I have never heard
I managed to build sage-4.7.1 on Ubuntu 11.10 Oneiric Ocelot using the
gcc-4.4 compiler. Maybe its helpful for others, this is what I did:
# install compiler
sudo apt-get install gcc-4.6 gcc-4.4-base gcc-4.4 g++-4.4 cpp-4.4
gfortran-4.4
# set up gcc alternatives
sudo update-alternatives
On 25 Okt., 18:02, Martin Albrecht martinralbre...@googlemail.com
wrote:
On Tuesday 25 October 2011, Jason Grout wrote:
On 10/25/11 10:40 AM, Martin Albrecht wrote:
However, from the website it seems, tcpcrypt doesn't guarantee privacy in
the default setting except against passive
On Oct 24, 2011, at 7:14 PM, Jason Grout wrote:
On 10/24/11 12:07 PM, leif wrote:
On 24 Okt., 17:33, Jason Groutjason-s...@creativetrax.com wrote:
Here is one of the big situations when I like trailing spaces:
def hello():$
print 'hi'$
$
print 'bye'$
To me, it's
On 25 Okt., 12:04, Jeroen Demeyer jdeme...@cage.ugent.be wrote:
On 2011-10-25 09:51, Dan Drake wrote:
I think that would be a good idea, although if you're just running that
through sed, the exact patches applied would be different from the ones
on the trac server, which would cause some
On Tue, Oct 25, 2011 at 11:06 AM, leif not.rea...@online.de wrote:
On 25 Okt., 12:04, Jeroen Demeyer jdeme...@cage.ugent.be wrote:
On 2011-10-25 09:51, Dan Drake wrote:
I think that would be a good idea, although if you're just running that
through sed, the exact patches applied would be
Hi,
[I've tried to post this to sage-release but it failed]
I've tried to build Sage 4.7.2 rc0 on a 64 bits Debian GNU/Linux (wheezy/sig)
[Intel core I5 procesor]
The build failed (compiling Atlas)
Here are the eror messages
Thread model: posix
gcc version 4.6.1 (Debian 4.6.1-15)
gcc -V 21
On 25 Okt., 20:44, William Stein wst...@gmail.com wrote:
On Tue, Oct 25, 2011 at 11:06 AM, leif not.rea...@online.de wrote:
So checking for added trailing whitespace in patches uploaded to trac
would IMHO be a task for the patchbot.
Even better, it could be done by a trac pluging itself (at
Hi!
I had first asked the following question on sage-combinat-devel, but
there was no reply, and so sorry for bothering you here...
It concerns two cached methods of categories, namely
C.all_super_categories() and C.super_categories(proper=False).
The former does not take any argument (except
On 10/25/11 3:30 PM, Simon King wrote:
However, I have heard that methods are considered more pythonic than
attributes.
I think attributes are considered more pythonic for many things than
methods. We insist on methods for many things in Sage because you can
document methods (but it's hard
On 25 Okt., 21:24, Pablo De Napoli pden...@gmail.com wrote:
I've tried to build Sage 4.7.2 rc0 on a 64 bits Debian GNU/Linux (wheezy/sig)
[Intel core I5 procesor]
The build failed (compiling Atlas)
Here are the eror messages
Thread model: posix
gcc version 4.6.1 (Debian 4.6.1-15)
gcc -V
Yes, that was exactly what happend!
a second make worked!
and I don't know why!
On Tue, Oct 25, 2011 at 6:21 PM, leif not.rea...@online.de wrote:
On 25 Okt., 21:24, Pablo De Napoli pden...@gmail.com wrote:
I've tried to build Sage 4.7.2 rc0 on a 64 bits Debian GNU/Linux (wheezy/sig)
[Intel
On Oct 24, 10:33 am, Jason Grout jason-s...@creativetrax.com wrote:
Here is one of the big situations when I like trailing spaces:
def hello():$
print 'hi'$
$
print 'bye'$
+1
Quite a few text editors do this by default. It's enormously
convenient to the programmer; it's
Hi All,
Is there an educated guess as to when/if sage will be ported to lion?
I foolishly upgraded when it came out and have been unable to use sage
since...
Cheers,
Andrew
--
To post to this group, send an email to sage-devel@googlegroups.com
To unsubscribe from this group, send an email to
On Tuesday, October 25, 2011 3:52:24 PM UTC-7, Andrew Mathas wrote:
Hi All,
Is there an educated guess as to when/if sage will be ported to lion?
I foolishly upgraded when it came out and have been unable to use sage
since...
There is a trac ticket about this on which there has been
On 26/10/2011, at 12:56 PM, John H Palmieri wrote:
Meanwhile, I believe that binary versions
of Sage for OS X 10.6 should work on OS X 10.7.
They do. I've been using them since I upgraded.
Michael
--
To post to this group, send an email to sage-devel@googlegroups.com
To unsubscribe from
FWIW, I'm trying to write a ticket listener trac plugin right now, for
other reasons. I could add some functionality to make it check, or even
fix, patch attachments as well. I can't promise it will be done very soon
though, since I just started it the other day :) I'm testing it on trac
0.12
On 26 Okt., 03:17, Keshav Kini keshav.k...@gmail.com wrote:
FWIW, I'm trying to write a ticket listener trac plugin right now, for
other reasons. I could add some functionality to make it check, or even
fix, patch attachments as well. I can't promise it will be done very soon
though, since I
Although I think checking attachments *before* they get attached is
quite different.
No, that's not what I meant. The listener bot would notice that a patch had
been posted, fix it, and then overwrite it by posting to the trac ticket
like a normal user, posting a comment with a diff on the
On 25 Okt., 23:49, john_perry_usm john.pe...@usm.edu wrote:
On Oct 24, 10:33 am, Jason Grout jason-s...@creativetrax.com wrote:
Here is one of the big situations when I like trailing spaces:
def hello():$
print 'hi'$
$
print 'bye'$
+1
Quite a few text editors do
On 26 Okt., 04:30, Keshav Kini keshav.k...@gmail.com wrote:
Although I think checking attachments *before* they get attached is
quite different.
No, that's not what I meant. The listener bot would notice that a patch had
been posted, fix it, and then overwrite it by posting to the trac
Yes, of course there would be some delay. The repo could be disposed of if
the ticket was merged into a full release, so disk usage would not build up
too much. And keep in mind that if we were doing normal commits and
pull-requests etc. instead of developing polished patches on trac and
I think you should put sage: in front of all complete commands and
... in front of continuation lines. I was making multi-line cycles
this way. Triple quotes may conflict with the way how SageTeX produces
its files. Did you try triple single quotes? ( ' + ' + ' instead of
+ + )
Andrey
On Oct
On Tue, 25 Oct 2011 at 08:10AM -0700, javier wrote:
I am trying to add some Sage examples to my lecture notes for a course
in Commutative Algebra. In particular want to include an example on
how to define the power set ring in sage. I would like to list some
big chunks of sage code with nice
35 matches
Mail list logo
