Here it is !! :-)
http://trac.sagemath.org/sage_trac/ticket/7492
Nathann
On Nov 20, 8:36 am, Nathann Cohen wrote:
> I first thought about your second option, but as Sage has already a
> permutation class, plus a .to_matrix() method to obtain the matrix
> back, I'll go for 1, playing the coward
> But adding just my user name does not result in any updates being
> emailed to me.
Then you need to update your username's e-mail address. IIRC you have to
contact the Trac admin for that (William, Minh, Harald?)
Martin
--
name: Martin Albrecht
_pgp: http://pgp.mit.edu:11371/pks/lookup?op=ge
On Fri, Nov 20, 2009 at 01:29:16AM -0800, Nathann Cohen wrote:
> Here it is !! :-)
>
> http://trac.sagemath.org/sage_trac/ticket/7492
Cool, thanks!
I would return the result as an element of:
CombinatorialFreeModule(Permutations(n), F)
where n is the size of the matrix, and F its ground
Hi Dan!
On Wed, Nov 18, 2009 at 09:10:20AM +0900, Dan Drake wrote:
> On Tue, 17 Nov 2009 at 11:32PM +0100, Nicolas M. Thiery wrote:
> > I have a feature request: an environment where I could use the same
> > syntax as in usual doctests (without the sage results):
> >
> > \begin{sageexam
On Thu, Nov 19, 2009 at 08:42:54PM -0600, Jason Grout wrote:
> Tom Boothby wrote:
> > On Thu, Nov 19, 2009 at 4:14 PM, Florent Hivert
> > wrote:
> >> Hi Jason,
> >>
> I'd like to generate all partially ordered sets of a given cardinality
> upto
> isomorphisms... They are in bi
On Nov 20, 8:04 am, Peter Jeremy wrote:
> My initial comment is that making virtually every question mandatory
> is likely to turn people off or make them pick random answers to
> questions they don't want to answer.
The last year I thought this too, but turns out most of the answers
were not ran
On Fri, Nov 20, 2009 at 3:07 AM, Harald Schilly
wrote:
> On Nov 20, 8:04 am, Peter Jeremy wrote:
>> My initial comment is that making virtually every question mandatory
>> is likely to turn people off or make them pick random answers to
>> questions they don't want to answer.
>
> The last year I
Jason Grout wrote:
> Has anyone applied for a wolfram alpha api id for Sage?
>
> http://www.wolframalpha.com/developers.html
>
> It seems pretty natural to have a Sage interface to Wolfram Alpha.
>
> Thanks,
>
> Jason
>
It would be an interesting request!
Dave.
--
To post to this group, s
Hi,
Me and several people have been putting together a proposal to this NSF program:
http://www.nsf.gov/funding/pgm_summ.jsp?pims_id=5390
I currently have a grant from them for Sage that will expire soon, and
would like another one :-)
This time, we're applying for 4 Sage Days workshops a
On Fri, 20 Nov 2009 at 11:16AM +0100, Nicolas M. Thiery wrote:
> > In Python, I could so something like
> >
> > the_verbatim_line.replace('sage: ', '', 1)
> >
> > but LaTeX does not make string handling easy.
>
> Precisely. So it sounds tempting to have latex write a quoted string
> in the
This is now ticket #7504.
sage: bool(pari(False))
False
sage: bool(gap(False))
False
sage: bool(maxima(False))
False
sage: bool(maple(False))
False
sage: bool(mathematica(False))
False
sage: bool(magma(False))
True
Kiran
--
To post to this group, send an email to sage-devel@googlegroups.com
To
Hello
Can I ignore the SeLinux alert which I obtain from time to time
starting sage 4.2.1 compiled from sources in Fedora 12 on QuadCore
2.4GHz, 4GB RAM
Podsumowanie: (Summary:)
SELinux is preventing /home/andy/Pobrane/sage-4.2.1/local/bin/python
from making the program stack executable.
Szczegó
Hi. I read through and made some comments into
the PDF with Skim on Mac OS X. I'll send it to
you via email.
Henning
On Nov 20, 12:24 pm, William Stein wrote:
> Hi,
>
> Me and several people have been putting together a proposal to this NSF
> program:
>
> http://www.nsf.gov/funding/pgm_sum
> This is my final status report for the category patches:
>
> Yiiippeee!
+1
> Mike just merged them today in Sage 4.3-alpha0, together with one year
> of hard work worth of feature-full patches around root systems, Weyl
> characters, symmetric
"Nicolas M. Thiery" writes:
> Dear category fans, dear Sage-Combinat developers,
>
> This is my final status report for the category patches:
>
> Yiiippeee!
factorial(Congratulations)
I should say to live up to the cliché...
Martin
--
To post t
Thanks for the information ! I just updated my patch ;-)
Nathann
--
To post to this group, send an email to sage-devel@googlegroups.com
To unsubscribe from this group, send an email to
sage-devel-unsubscr...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/s
I've created a couple of scripts which can check what compiler the variables CC
and CXX refer to. They are a bit more complex than the usual things that grep
the output, as these check what the pre-processor defines. As such, they should
be very reliable indicators.
For example, setting CC=tar
I'm teaching numerical analysis next semester, so I'm investigating how
we can use Sage's great support for specifying precision to explain some
topics. I'd like to limit the exponents that a number in a RealField
can have (for example, the exponent must be 0, 1, or -1. I see that
mpfr suppor
achrzesz a écrit :
> Hello
> Can I ignore the SeLinux alert which I obtain from time to time
> starting sage 4.2.1 compiled from sources in Fedora 12 on QuadCore
> 2.4GHz, 4GB RAM
>
>
I do not have an answer to your question. But do you plan to use SELinux
for securing Sage? (a Sage server ?). T
On Sat, Nov 21, 2009 at 1:18 AM, Dr. David Kirkby
wrote:
> I think the scripts need to go to SAGE_LOCAL/bin, but I've no idea where in
> the
> Sage source they should be placed.
There is a repository in $SAGE_LOCAL/bin (the scripts repository) that
they can be checked into.
--Mike
--
To post
achrzesz wrote:
> Hello
> Can I ignore the SeLinux alert which I obtain from time to time
> starting sage 4.2.1 compiled from sources in Fedora 12 on QuadCore
> 2.4GHz, 4GB RAM
>
I always disable SeLinx on my home computers or set it in permissive mode.
Jaap
--
To post to this group, send an
Sage Developers,
trac # 4644 has a patch that I wrote to deal with
several problems with 'sage -sh'. It is listed
as fixed in 4.2.
Yet sage-4.2.1 does not seem to have the patch.
Did I miss a discussion about this issue that caused
my patch to be reverted?
--
Mariah
--
To post to this group
Hi Mariah,
On Sat, Nov 21, 2009 at 7:09 AM, Mariah Lenox wrote:
> Sage Developers,
>
> trac # 4644 has a patch that I wrote to deal with
> several problems with 'sage -sh'. It is listed
> as fixed in 4.2.
>
> Yet sage-4.2.1 does not seem to have the patch.
I just confirmed that ticket #4644 [1]
2009/11/20 Mike Hansen :
> On Sat, Nov 21, 2009 at 1:18 AM, Dr. David Kirkby
> wrote:
>> I think the scripts need to go to SAGE_LOCAL/bin, but I've no idea where in
>> the
>> Sage source they should be placed.
>
> There is a repository in $SAGE_LOCAL/bin (the scripts repository) that
> they can b
""" If the user changes the exponent range, it is her/his
responsibility to check that all current floating-point variables are
in the new allowed range (for example using mpfr_check_range),
otherwise the subsequent behavior will be undefined, in the sense of
the ISO C standard. """
This looks dau
25 matches
Mail list logo
