Hi,
After trying "make distclean" to start the build from scratch, the build
finally succeed.
Thanks.
On Sun, Jun 23, 2013 at 7:13 AM, Volker Braun wrote:
> You have some half-built gfortran in the path, try "make distclean" to
> start the build from scratch.
>
>
>
>
> On Saturday, June 22,
Congratulations! This is very deserved. We *really* appreciate all the
work you've done! I think it's been critical to the success of Sage.
Jason
On 6/22/13 12:48 PM, William Stein wrote:
Jeroen Demeyer has provided excellent service to the Sage community as
release manager, starting with
Excellent choice, congratulations Jeroen!
-Marshall
--
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
You have some half-built gfortran in the path, try "make distclean" to
start the build from scratch.
On Saturday, June 22, 2013 2:49:07 AM UTC-7, Wai Man Chung wrote:
>
> I have taken advice of Volker Braun and run "sudo yum install gcc-c++
> gcc-gfortran", then I run "make" again, it runs for
On Friday, 21 June 2013 12:56:10 UTC+2, John Cremona wrote:
>
> Perhaps the best way forward would be to split this up into sections,
> rather than doing it all at once. For example we could deal with the
> elliptic curve cases in one ticket.
>
Right, having separate tickets and patches for se
Le 22/06/2013 21:55, leif a écrit :
William Stein wrote:
For his conscientious and technically excellent work as Sage release
manager, and his significant contributions to the Sage library,
Jeroen Demeyer is awarded the 2013 Spies Prize.
Just wonder whether he's already on vacation (i.e., offl
William Stein wrote:
For his conscientious and technically excellent work as Sage release
manager, and his significant contributions to the Sage library,
Jeroen Demeyer is awarded the 2013 Spies Prize.
Just wonder whether he's already on vacation (i.e., offline)... ;-)
Anyway, congrats!
-lei
On 22 June 2013 19:48, William Stein wrote:
> Please join me in congratulating Jeroen!
>
> -- The 2013 Spies Prize Committee
Well done - an excellent choice.
Dave
--
You received this message because you are subscribed to the Google Groups
"sage-devel" group.
To unsubscribe from this group
Congratulations, Jeroen! Well deserved. Thanks for all your excellent
work with the releases!
Rob
--
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+un
Congrats Jeroen!
On Sat, Jun 22, 2013 at 2:48 PM, William Stein wrote:
> Jeroen Demeyer has provided excellent service to the Sage community as
> release manager, starting with Version 4.6.1 in January 2011, just
> five months after his first code contribution. He has continued to
> contribute
Jeroen Demeyer has provided excellent service to the Sage community as
release manager, starting with Version 4.6.1 in January 2011, just
five months after his first code contribution. He has continued to
contribute significant code to the Sage library in the area of number
theory, including over
It's better to import them at the module level (I've been told it's
faster when calling the function). However due to circular imports, this is
not always possible (unless you lazily import it). Although it sometimes is
best to put things in functions that only use a certain module in one (or
Hello,
Is there only one ppa server for Ubuntu ?
If YES, may be it would be reasonable to make mirrors: in my lab, I
install sage on all the machines using the ppa: it means 5 interactive
servers (we use ltsp for every day computer access) + a cluster of 12
machines +
Maybe the "tube"
Hi,
Thanks for the advice.
I have taken advice of Volker Braun and run "sudo yum install gcc-c++
gcc-gfortran", then I run "make" again, it runs for a while and it seems
the previous error is passed. But there is other similar error :
=
gfortran: e
Thanks, that works!
I thought it was better to import the modules outside the functions I am
writing. Is there a rule ?
Matthieu
Le samedi 22 juin 2013 09:56:46 UTC+2, Travis Scrimshaw a écrit :
>
> Hey Matthieu,
>Sounds like a circular import. You'll have to import FreeMonoid in the
> funct
Hey Matthieu,
Sounds like a circular import. You'll have to import FreeMonoid in the
function that you are using it in. For example:
def foo(x):
from sage.some.module import Bar
Bar(x)
...
Best,
Travis
On Friday, June 21, 2013 3:54:51 PM UTC+2, Matthieu Deneufchâtel wrote:
>
> I
On 2013-06-22, Volker Braun wrote:
> --=_Part_5_26369588.1371859450149
> Content-Type: text/plain; charset=ISO-8859-1
>
> http://www.python.org/dev/peps/pep-0318/
>
> On Friday, June 21, 2013 1:43:13 PM UTC-7, Dima Pasechnik wrote:
>>
>> Why does one even need a decorator in Simon's proposal?
17 matches
Mail list logo
