[sage-devel] Re: [sage-cloud] Re: network access from projects

2014-06-22 Thread Андрей Ширшов
William, It seems for me white list should be placed on SMC site. For example in help page. воскресенье, 22 июня 2014 г., 22:19:54 UTC+4 пользователь William Stein написал: > > On Sun, Jun 22, 2014 at 1:26 AM, Craig E Larson > wrote: > > hi, > > > > can you add washington.edu to the whitelis

Re: [sage-devel] A digital non-deterministic random bit generator

2014-06-22 Thread David Joyner
On Sun, Jun 22, 2014 at 9:22 PM, wrote: > is available here > > www.tag.md/public/ > While this looks spammy, it seems to be an implementation of Nash's algorithm from 1955 (recently declassified, http://www.nsa.gov/public_info/press_room/2012/nash_exhibit.shtml). I thought Nash's algorithm was

[sage-devel] A digital non-deterministic random bit generator

2014-06-22 Thread mknight . tag
is available here www.tag.md/public/ -- 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

[sage-devel] Re: make download includes optional packages

2014-06-22 Thread Andrey Novoseltsev
I missed once again a "proper" make download target - with a very fast network (part of Seattle cluster, so in fact local) downloading standard packages is easy, yet there still can be some hiccups that interrupt compilation. And of course I was not watching what's going on for a bit since comp

[sage-devel] Re: curl 404 on cygwin64 branch

2014-06-22 Thread Jason Wu
It worked! I initially tried this, but it didn't work because the tarball from mpir.org was named "mpir-2.7.0[DASH]alpha4.tar.bz2" where the one it was trying to download was "mpir-2.7.0[DOT]alpha4.tar.bz2". Thanks again! On Sunday, June 22, 2014 7:20:25 PM UTC-4, Dima Pasechnik wrote: > > On 2

[sage-devel] Re: curl 404 on cygwin64 branch

2014-06-22 Thread Dima Pasechnik
On 2014-06-22, Jason Wu wrote: > Hello, > I'm fairly new to sage and I was trying to build sage on cygwin64. I cloned > the git repo and checked out u/jpflori/cygwin64 but it gets stuck when it > tries to download mpir 2.7.0.alpha4. mpir2.6.0 (used in master branch) > won't build on cygwin64. a

[sage-devel] curl 404 on cygwin64 branch

2014-06-22 Thread Jason Wu
Hello, I'm fairly new to sage and I was trying to build sage on cygwin64. I cloned the git repo and checked out u/jpflori/cygwin64 but it gets stuck when it tries to download mpir 2.7.0.alpha4. mpir2.6.0 (used in master branch) won't build on cygwin64. anyways, sage-spkg uses curl to try and dow

Re: [sage-devel] Re: network access from projects

2014-06-22 Thread William Stein
On Sun, Jun 22, 2014 at 2:17 PM, Benjamin Peterson wrote: > William Stein gmail.com> writes: > >> >> >> Is there a way to create a local mirror of all of pypi? > > One can use the bandersnatch package for this: > https://pypi.python.org/pypi/bandersnatch Thanks! > > -- > You received this messa

Re: [sage-devel] Re: cube roots in Sage

2014-06-22 Thread Vincent Delecroix
As Niles already said it would be better to have it as a symbolic function sage: f(x) = real_nth_root(x, 5) sage: f x |--> real_nth_root(x,5) 2014-06-22 22:36 UTC+02:00, Gregory Bard : > Yes, that is reasonable. Let us call it "real_nth_root" instead, as > suggested by Nicolas Thiery. Any other r

[sage-devel] Re: cube roots in Sage

2014-06-22 Thread Dima Pasechnik
On 2014-06-22, Gregory Bard wrote: > Yes, that is reasonable. Let us call it "real_nth_root" instead, as > suggested by Nicolas Thiery. Any other requests/comments? it's better talk about "n-ic" root rather than "n-th" root, IMHO. > > It would be superb if this could be resolved by June 30th, w

[sage-devel] Re: network access from projects

2014-06-22 Thread Benjamin Peterson
William Stein gmail.com> writes: > > > Is there a way to create a local mirror of all of pypi? One can use the bandersnatch package for this: https://pypi.python.org/pypi/bandersnatch -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubsc

Re: [sage-devel] Re: cube roots in Sage

2014-06-22 Thread Gregory Bard
Yes, that is reasonable. Let us call it "real_nth_root" instead, as suggested by Nicolas Thiery. Any other requests/comments? It would be superb if this could be resolved by June 30th, when my book goes to the American Mathematical Society for publication... ---Greg On Sun, Jun 22, 2014 at 9:02 A

[sage-devel] Re: [sage-cloud] Re: network access from projects

2014-06-22 Thread William Stein
On Sun, Jun 22, 2014 at 1:26 AM, Craig E Larson wrote: > hi, > > can you add washington.edu to the whitelist? No. > i use local copies of sage in my projects so i can add my own packages. i > download them from: > > http://boxen.math.washington.edu/home/sagemath/sage-mirror/linux/64bit/ However

Re: [sage-devel] Re: cube roots in Sage

2014-06-22 Thread William Stein
On Sun, Jun 22, 2014 at 8:27 AM, Nicolas M. Thiery wrote: > On Fri, Jun 20, 2014 at 06:33:52PM -0700, Gregory Bard wrote: >> It seems that the consensus on both Sage-devel and Sage-edu is to go >> with some sort of nth_real_root function. I propose the following, >> which I have tested for evaluat

[sage-devel] Re: Coercion model not allowing coercions to be registered

2014-06-22 Thread Simon King
Hi Travis, On 2014-06-22, Travis Scrimshaw wrote: > Now startup a new session: > > sage: SGA4 = SymmetricGroupAlgebra(QQ, 4) > sage: SGA3 = SymmetricGroupAlgebra(QQ, 3) > sage: SGA3.has_coerce_map_from(SGA4) > False > sage: lift = SGA4.module_morphism(lambda x: SGA3.zero(), codomain=SGA3) > sage:

Re: [sage-devel] Re: cube roots in Sage

2014-06-22 Thread Nicolas M. Thiery
On Fri, Jun 20, 2014 at 06:33:52PM -0700, Gregory Bard wrote: > It seems that the consensus on both Sage-devel and Sage-edu is to go > with some sort of nth_real_root function. I propose the following, > which I have tested for evaluation, plotting, differentiation, and > integration. Sadly, the de

[sage-devel] Coercion model not allowing coercions to be registered

2014-06-22 Thread Travis Scrimshaw
Hey everyone, Currently we have the following behavior in Sage. This is okay: sage: SGA4 = SymmetricGroupAlgebra(QQ, 4) sage: SGA3 = SymmetricGroupAlgebra(QQ, 3) sage: lift = SGA4.module_morphism(lambda x: SGA3.zero(), codomain=SGA3) sage: SGA3.register_coercion(lift) Now startup a new sessio