>>> 2^6
> 4
>
>
I didn't know sage-combinat had switched back to pure Python...
--
You received this message because you are subscribed to the Google Groups
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to sage-devel+unsubscr...@googlegro
Dear Anne,
>>> 2^6
4
Sincerely,
Paul
Paul-Olivier Dehaye
SNF Assistant Professor of Mathematics
University of Zurich
http://user.math.uzh.ch/dehaye/contact_info.txt
On Wed, Sep 10, 2014 at 2:42 AM, Anne Schilling
wrote:
> Dear All!
>
> Dan Bump, Travis Scrimshaw and I are going to organize S
Dear All!
Dan Bump, Travis Scrimshaw and I are going to organize Sage Days 64 (=2^6 !!)
at UC Davis March 17-20, 2015. A preliminary website can be found here
http://wiki.sagemath.org/days64
If you are interested in participating, please sign up on the wiki or
drop us a line!
Hope to see yo
I was dabbling in arithmetic when I noticed that the following leaks memory
at about a megabyte per second:
F. = GF(11^2, 'a')
R. = F[]
while True:
_ = x(a, a)
Now I would have thought that evaluating polynomials is a fairly common
operation, so I'm sure somebody noticed thi
For the record, I'd rather have both 0 and 1-based permutations act on
matrices in the the natural way (as permutations on an ordered set,
regardless of how that set is written). So there is no need to get rid of
1-based permutations. However, we need to be able to tell 0- and 1-based
permutati
Hello sage-devel,
could somebody please review the small patch
http://trac.sagemath.org/ticket/16827
It fixes the sage-preparse script, which is called when running a
foo.sage file through the command line, to use atomic_write. This avoids
race conditions when multiple Sage sessions are run in
On Tue, Sep 09, 2014 at 10:18:29AM -0700, 'Martin R' via sage-devel wrote:
>But why shouldn't the current behaviour be deprecated?
With this ticket I was aiming for a minimal change. If there is a
consensus that we eventually want to get rid of using 1-based
permutations for row/column matrix
On Tuesday, September 9, 2014 8:55:04 AM UTC-7, Volker Braun wrote:
>
> On Tuesday, September 9, 2014 4:44:33 PM UTC+1, Nils Bruin wrote:
>>
>> In python, looking up a global flag is going to be relatively slow,
>> because, if addressed by its proper name, it involves checking several
>> __dict__
On Tuesday, September 9, 2014 6:07:49 PM UTC+1, Nicolas M. Thiéry wrote:
>
> I agree it's not great. But do you have a better proposal?
How about being explicit, aka the principle of least astonishment?
M.permute_columns(sigma, base=0) with base=1 being the default. In either
case an error is
The "git trac log " only inspects the log of the current branch
(just like "git log", except that it understands trac ticket numbers). So
you need to be on a sufficiently recent branch if you want the log of these
tickets.
On Tuesday, September 9, 2014 5:56:28 PM UTC+1, Clemens Heuberger wrote
>
> The ticket only adds a new feature allowing for the natural 0-based
> permutations. Otherwise it does not change the current behavior.
But why shouldn't the current behaviour be deprecated? I think requiring
that the domain is 0..n-1 (is possible, with a check) would be much better.
Mart
Bonjour Bernard,
On Wed, Sep 03, 2014 at 12:42:51PM -0700, parisse wrote:
>I'm reading the european grant project description on
>https://github.com/sagemath/grant-europe/ and I have no idea whether
>the software would be free or not. In fact since the project in its
>curre
On Fri, Sep 05, 2014 at 07:58:30AM -0700, Dima Pasechnik wrote:
>I just had a quick look at it, and the following looks downright scary:
>+For backward compatibility, if a permutation group element
>+acts on the integers `\{1,\ldots,n\}` or a subset thereof,
>
I get (git-trac-command at 7e8fb34)
$ git trac log 16538
Error: release manager has not merged Trac #16538
$ git trac log 16943
Error: release manager has not merged Trac #16943
$ git trac log 16786
Error: release manager has not merged Trac #16786
Actually, #16538 has been merged in 6.4.beta0,
#
On Fri, Sep 05, 2014 at 05:00:29PM +0200, Nathann Cohen wrote:
>> I just had a quick look at it, and the following looks downright
>scary:
>It is one of this code's many wonders. Also, note that :
>sage: Permutation([1,2,3])
>[1, 2, 3]
>sage: Permutation((1,2,3))
>[2, 3,
On Tuesday, September 9, 2014 4:44:33 PM UTC+1, Nils Bruin wrote:
>
> In python, looking up a global flag is going to be relatively slow,
> because, if addressed by its proper name, it involves checking several
> __dict__s
>
Which is why it needs to be a cdef bool as I wrote earlier.
sage: sag
On Tuesday, September 9, 2014 5:48:59 AM UTC-7, Volker Braun wrote:
>
> But that doesn't work at the C level, you either compile something in or
> not. So you can't apply it to the (presumably) speed-critical c(p)def
> functions, only to plain Python functions
>
True
> where overhead wasn't muc
Hi
Then perhaps this message should be changed?
$sage -i pyopenssl
...
...
Successfully installed pyopenssl-0.13.p0
Deleting temporary build directory
/home/jan/src/sage-6.3/local/var/tmp/sage/build/pyopenssl-0.13.p0
Finished installing pyopenssl-0.13.p0.spkg
Warning: it might be needed to updat
On Monday, September 8, 2014 6:32:33 PM UTC+1, Nils Bruin wrote:
>
> There is an advantage to a decorator on python-level: If you're happy to
> configure sage_citation_enabled at start-up (which means it would have to
> be a command line option or an environment variable), you can make it
> comp
On Tuesday, September 9, 2014 3:02:08 AM UTC-4, Jan Groenewald wrote:
>
> Hi
>
> I'm running Ubuntu 14.04 and the PPA which is the downloaded binary.
>
> I wanted to enable notebook(secure=True), which prompted me to install
> pyopenssl.
>
> sage -i pyopenssl successfully installed but prompted
Hi
I can change the permissions on the PPA folder, these are imaged desktops
for labs, and I can always test and reimage on any computer.
I have in the past often installed optional packages with the PPA.
I will try from source, and see if it persists.
Regards,
Jan
On 9 September 2014 11:39, V
If you used the PPA shouldn't "sage -i" have failed with a permission
error, how come you can write into the Sage install? In any case, IMHO you
are best off compiling all of Sage if you want to install (compile)
optional packages as well.
On Tuesday, September 9, 2014 8:02:08 AM UTC+1, Jan G
[paul.mercat@octopus ~]$ rpm -ql glpk-dev
package glpk-dev is not installed
Le mardi 9 septembre 2014 11:03:50 UTC+2, François a écrit :
>
> No obvious things in this log. But a careful reading shows that both
> glpk.h and glpk/glpk.h where found. glpk in sage only ships glpk.h
> so the other on
No obvious things in this log. But a careful reading shows that both
glpk.h and glpk/glpk.h where found. glpk in sage only ships glpk.h
so the other one must come from the system.
The output of "rpm -ql glpk-dev" or would it be glpk-devel would
show us what has been detected from the system.
But l
Hi
I'm running Ubuntu 14.04 and the PPA which is the downloaded binary.
I wanted to enable notebook(secure=True), which prompted me to install
pyopenssl.
sage -i pyopenssl successfully installed but prompted me to make.
make finished without error.
sage now does not start:
0 jan@muizenberg:/va
25 matches
Mail list logo
