On 1/30/13 11:35 PM, William Stein wrote:
It's a normal control at that point -- it sends a message back to the
server and calls the function f.
One thing is that it does*not* try to pass m into f. The interact
object can tell you which variable(s)
triggered a called, and of course you can get
On Wed, Jan 30, 2013 at 9:29 PM, Jason Grout
wrote:
> On 1/30/13 10:53 PM, William Stein wrote:
>>
>> On Wed, Jan 30, 2013 at 7:49 PM, Nicolas M. Thiery
>> wrote:
>>>
>>> Hi William!
>>>
>>> On Wed, Jan 30, 2013 at 05:33:57PM -0800, William Stein wrote:
Can I ask one quick ques
On 1/30/13 10:53 PM, William Stein wrote:
On Wed, Jan 30, 2013 at 7:49 PM, Nicolas M. Thiery
wrote:
Hi William!
On Wed, Jan 30, 2013 at 05:33:57PM -0800, William Stein wrote:
Can I ask one quick question? This is *NOT* meant to be a rhetorical
question (though it could incorrectly b
On Wed, Jan 30, 2013 at 7:49 PM, Nicolas M. Thiery
wrote:
> Hi William!
>
> On Wed, Jan 30, 2013 at 05:33:57PM -0800, William Stein wrote:
>> Can I ask one quick question? This is *NOT* meant to be a rhetorical
>> question (though it could incorrectly be taken that way). Why did you
>> n
Hi William!
On Wed, Jan 30, 2013 at 05:33:57PM -0800, William Stein wrote:
> Can I ask one quick question? This is *NOT* meant to be a rhetorical
> question (though it could incorrectly be taken that way). Why did you
> not write this as an interact?
The main reason is that we are not s
On 2013-01-31, Keshav Kini wrote:
> Dima Pasechnik writes:
>> On 2013-01-23, Robert Bradshaw wrote:
>>> On Tue, Jan 22, 2013 at 9:53 PM, tom d wrote:
Another possible solution would be to change the error message one gets on
a
failed import statement. (I also lost hair on this
Dima Pasechnik writes:
> On 2013-01-23, Robert Bradshaw wrote:
>> On Tue, Jan 22, 2013 at 9:53 PM, tom d wrote:
>>> Another possible solution would be to change the error message one gets on a
>>> failed import statement. (I also lost hair on this issue a couple days
>>> ago.) Right now it say
On Wed, Jan 30, 2013 at 1:04 PM, Nicolas M. Thiery
wrote:
> Dear Sage developers,
>
> At the AIM/ICMS workshop ``Online databases: from L-functions to
> combinatorics'' last week, Jason Bandlow and myself had fun writing a
> prototype for a simple LMFDB-style web application allowing to ex
On 2013-01-30, mmarco wrote:
> Maybe it should be inside public_html?
try this:
http://boxen.math.washington.edu/home/jpuydt/bdist/
>
> On 30 ene, 15:39, Julien Puydt wrote:
>> Le 30/01/2013 12:49, mmarco a crit :
>>
>> > I cannot access to your directory.
>>
>> Hmmm... I don't understand why:
>
William Stein writes:
> I remember adding code that used "with" to Sage back in I think 2008
> when working on generators for the coercion model. We've been using
> with for a long time.
Sure. In general the newer pieces of code in Sage do tend to use more
modern Python than older pieces of code
Dear Sage developers,
At the AIM/ICMS workshop ``Online databases: from L-functions to
combinatorics'' last week, Jason Bandlow and myself had fun writing a
prototype for a simple LMFDB-style web application allowing to explore
Sage. There it is!
Sage Explorer
-
Sage Explorer
On 2013-01-30 21:08, mmarco wrote:
> Should this be reported upstream to pari?
Just did so.
--
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...@
On Wed, Jan 30, 2013 at 11:04 AM, Keshav Kini wrote:
> Travis Scrimshaw writes:
>> Hey everyone,
>>Should we be encouraging (or enforce) new code to be python 3
>> compliant? In particular, not using removed syntax such as exceptions
>> as `raise ExceptionType, args` or `<>` comparisons?
>
>
Hi There,
It's not clear to me from the documentation if the following behavior is a bug
or a known bad use of cached method:
class Bla(object):
@cached_method
def truc(self):
print "Computing truc"
return 1
trac = truc
sage: b = Bla()
sage: b.truc()
Computing t
Thanks, i will try the workaround. Should this be reported upstream to
pari?
On 30 ene, 20:54, Nils Bruin wrote:
> Looks like a known problem:
>
> http://trac.sagemath.org/sage_trac/ticket/13054
>
> The routine in question tries to find a better defining polynomial for
> a given field. With
>
> R
As you may know, Sage prints lists of matrices in a smart way:
sage: m = random_matrix(GF(5),2)
sage: [ m, m^2, m^3 ]
[
[1 4] [4 2] [3 0]
[2 2], [1 2], [0 3]
]
But that currently only works for matrices with a hardcoded is_Matrix().
I'm proposing to add
Looks like a known problem:
http://trac.sagemath.org/sage_trac/ticket/13054
The routine in question tries to find a better defining polynomial for
a given field. With
R.=QQ['y']
poly=y^4 - 4294967296*y^2 + 54265257667816538374400
it executes:
degree = poly.degree()
pari_poly = pari(pol
Travis Scrimshaw writes:
> Hey everyone,
>Should we be encouraging (or enforce) new code to be python 3
> compliant? In particular, not using removed syntax such as exceptions
> as `raise ExceptionType, args` or `<>` comparisons?
Encouraging, yes; enforcing, I'd say no. I don't think a Python
I'd say everybody is encouraged to use py3-compatible syntax. Reading
through the list of whats new is a good start. Lacking py3-versions of all
libraries we can't really enforce anything yet in an automatted way, though
that should soon change.
On Wednesday, January 30, 2013 6:10:46 PM UTC, T
I get a strange error when i try to evaluate a polynomial in QQbar:
sage: R.=QQbar[]
sage: f=x^2+x^3-y^2+y^4*x^4
sage: RX=PolynomialRing(QQbar,'x')
sage: RY=PolynomialRing(QQbar,'y')
sage: x0=3+2^-8
sage: y0=RY(f((x0,y))).roots(multiplicities=False)[0]
sage: f(x+x0,y0)
Hey everyone,
Should we be encouraging (or enforce) new code to be python 3 compliant?
In particular, not using removed syntax such as exceptions as `raise
ExceptionType, args` or `<>` comparisons?
Thanks,
Travis
http://docs.python.org/3.0/whatsnew/3.0.html
--
You received this message bec
On Tuesday, January 29, 2013 9:01:28 AM UTC+1, Dima Pasechnik wrote:
>
>
>
> On Monday, 28 January 2013 19:05:31 UTC+8, Snark wrote:
>>
>> Le 28/01/2013 11:55, Dima Pasechnik a �crit :
>> > On 2013-01-28, Julien Puydt wrote:
>> >> Hi,
>> >>
>> >> here is where we stand:
>> >>
>> >> - bui
On Monday, January 28, 2013 11:55:30 AM UTC+1, Dima Pasechnik wrote:
>
> On 2013-01-28, Julien Puydt > wrote:
> > Hi,
> >
> > here is where we stand:
> >
> > - build: ok, even though libm4rie's conversion.c is a pain ;
> >
> > - ptestlong: three failing tests, related to libc's gamma funct
The problem was in some of the files that we had modified
(authentication.py). we just had to comment the line where it defined
the default user.
The problem with the archiving/unarchiving wrksheets also apperaed in
a previous upgrade.
On 30 ene, 16:31, kcrisman wrote:
> On Jan 30, 10:10 am, mma
On Jan 30, 10:10 am, mmarco wrote:
> Ok, i think i could solve the poblem. The only issue we have now is
> that old worksheets cannot be archived/unarchived
Can you give specifics of your solution? This is very strange.
>
> > On 01/30/2013 09:23 PM, mmarco wrote:
>
> > > I can't recall anyth
Maybe it should be inside public_html?
On 30 ene, 15:39, Julien Puydt wrote:
> Le 30/01/2013 12:49, mmarco a crit :
>
> > I cannot access to your directory.
>
> Hmmm... I don't understand why:
>
> - /home is drwxr-xr-x
>
> - /home/jpuydt is drwxr-xr-x
>
> - /home/jpuydt/bdist is drwxr-xr-x
>
> -
Ok, i think i could solve the poblem. The only issue we have now is
that old worksheets cannot be archived/unarchived
On 30 ene, 15:04, P Purkayastha wrote:
> On 01/30/2013 09:23 PM, mmarco wrote:
>
> > I can't recall anything unusual about the login setup. We have
> > disabled the signing in, an
Le 30/01/2013 12:49, mmarco a écrit :
I cannot access to your directory.
Hmmm... I don't understand why:
- /home is drwxr-xr-x
- /home/jpuydt is drwxr-xr-x
- /home/jpuydt/bdist is drwxr-xr-x
- /home/jpuydt/bdist/sage-5.6-armv7l-Linux.tar.xz is -rw-r--r--
so you should have the right to ent
On 01/30/2013 09:23 PM, mmarco wrote:
I can't recall anything unusual about the login setup. We have
disabled the signing in, and there is no openID option (was it
available in sage 5.2 at all).
I think it might be something specific to your setup. We do have a
server on sage-5.2 using openid.
Hi!
As a preparatory step, I improved the parsing of function definitions in
sage_getargspec. This is needed for putting UniqueRepresentation into a
.pyx file, because currently function definitions in a .pyx file
containing varargs and keywords are not correctly parsed. By
consequence, the @[weak
In Ubuntu, the www-browser is a link:
kaibutsu@sophos:~$ ls -lah /usr/bin/www-browser
lrwxrwxrwx 1 root root 29 Oct 4 12:01 /usr/bin/www-browser ->
/etc/alternatives/www-browser
So you could create that link and make it point to your favorite default
browser. It might also be worth dropping a
I can confirm that this same numerical noise (binomial, gamma functions)
happens on the ARM6 on the Raspberry Pi, running the 'raspian' distro.
(Which isn't Ubuntu, though it is a Debian derivative.)
On Monday, January 28, 2013 1:55:30 PM UTC+3, Dima Pasechnik wrote:
>
> On 2013-01-28, Julien P
I can't recall anything unusual about the login setup. We have
disabled the signing in, and there is no openID option (was it
available in sage 5.2 at all).
Users were created automatically with a script in the command line,
that read the usernames, emails and passwords from a text file and
create
This user has asked this question multiple times, and if there isn't
something strange about the computer, this is a fairly significant and
unexpected regression, presumably due to the new(est) "Flask" notebook
changes. I have to say that we haven't heard much about it, but then
again perhaps not
On Wednesday, January 30, 2013 2:05:56 PM UTC+1, mmarco wrote:
>
> The problem is that i not only have to keep the worksheets, but also
> the users (the server is used by several people), and the information
> about which worksheet is owned by who, and shared with who.
>
I really cannot help th
The problem is that i not only have to keep the worksheets, but also
the users (the server is used by several people), and the information
about which worksheet is owned by who, and shared with who.
On 30 ene, 14:04, Jesus Torrado wrote:
> On Wednesday, January 30, 2013 12:51:55 PM UTC+1, mmarco
On Wednesday, January 30, 2013 12:51:55 PM UTC+1, mmarco wrote:
>
> I don't know if it is the right place to ask this. I have asked in
> sage-notebook list but got no response.
>
BTW, I'd say that sage-support is the appropriate place for this question.
Cheers,
Jesús Torrado
--
You received t
Hi,
This is an unqualified opinion, but it may work, and definitely not harm.
(0) Backup the old and new ".sage" folders.
(1) Erase "~/.sage"
(2) Start 5.6, which will create a fresh ".sage".
(3) Open the notebook and crete a couple of worksheets.
(4) Close sage 5.6.
(5) Look for a folder na
I don't know if it is the right place to ask this. I have asked in
sage-notebook list but got no response.
The problem is that i am running a server with sage 5.2 version. Now i
want to upgrade to sage 5.6, but the notebook directory seems to be
incompatible somehow.
When i try to run it, and acc
I cannot access to your directory.
--
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...@googlegroups.com.
To post to this group, send email to sa
On Tue, Jan 29, 2013 at 8:01 PM, Jonathan wrote:
> For the record as I think about this. The way most scientists do this with
> a mixed number of significant digits (significant figures, SF) in the inputs
> is the following. Please note that for functions like sine, cosine, log and
> so on this
41 matches
Mail list logo
