On Wednesday, December 9, 2015 at 4:45:35 PM UTC-6, Nils Bruin wrote:
>
> On Wednesday, December 9, 2015 at 10:21:17 AM UTC-8, prateek sharma wrote:
>>
>> No . The system just says "Newly created local branch..." and processing
>> keeps on going.
>> I have to forcefully stop the programme.
>>
>
Works here, and your log definitely indicate ATLAS has been found.
The error message seem to indicate the wrong options are passed
to gfortran to link the shared object. This is probably due to some
confusion in the numpy build system which doesn't expect ATLAS
on OS X.
Francois
On 12/10/15 15:1
Have you set SAGE_ATLAS_ARCH? Doing so is definitely not supported.
We prefer using the accelerate framework on OS X.
I have just upgraded xcode so I will give it a try.
Francois
On 12/10/15 13:20, Ian Hoffman wrote:
This is my first post (and first time building Sage). I'm using El
Capitan wit
On Wednesday, December 9, 2015 at 10:21:17 AM UTC-8, prateek sharma wrote:
>
> No . The system just says "Newly created local branch..." and processing
> keeps on going.
> I have to forcefully stop the programme.
>
It works for me (it does take some time to finish, however. I don't know
what it
On 9 December 2015 at 19:47, Jeroen Demeyer wrote:
> I added this to
> http://trac.sagemath.org/ticket/18639
Thanks. I had forgotten all about that one.
>
>
> --
> You received this message because you are subscribed to the Google Groups
> "sage-devel" group.
> To unsubscribe from this group an
I added this to
http://trac.sagemath.org/ticket/18639
--
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 grou
Can we bring this thread back to topic? An innocent sage statement
causes as segfault, and that is a Bad Thing.
John
On 9 December 2015 at 19:41, Dima Pasechnik wrote:
>
>
> On Wednesday, 9 December 2015 16:36:05 UTC, John Cremona wrote:
>>
>> On 9 December 2015 at 16:28, Nathann Cohen wrote:
On Wednesday, 9 December 2015 16:36:05 UTC, John Cremona wrote:
>
> On 9 December 2015 at 16:28, Nathann Cohen > wrote:
> >> Try this (6.10.beta7):
> >
> > This concept of a zero in mathematics is fishy. There is not any of
> > our troubles that cannot be traced back to it.
> >
> > +1 for
On Wednesday, 9 December 2015 16:51:45 UTC, Volker Braun wrote:
>
> Can you compare the floating point rounding modes at entry and exit of
> solvers.sdp?
>
I cannot reproduce it anymore. I don't know, I ran
sage: from decimal import getcontext
sage: getcontext()
Context(prec=28, rounding=ROUND_
On Wednesday, December 9, 2015 at 10:55:18 PM UTC+5:30, Nils Bruin wrote:
>
> On Wednesday, December 9, 2015 at 5:13:58 AM UTC-8, prateek sharma wrote:
>>
>> Can you tell me how can I create a branch .When I do git-trac-checkout
>> 5415
>> It says "Newly created local branch: t/5415/problems_wit
On Wednesday, December 9, 2015 at 5:13:58 AM UTC-8, prateek sharma wrote:
>
> Can you tell me how can I create a branch .When I do git-trac-checkout 5415
> It says "Newly created local branch: t/5415/problems_with_multifactorial_"
>
Doesn't the system just tell you that you have now succeeded in c
Can you compare the floating point rounding modes at entry and exit of
solvers.sdp?
On Wednesday, December 9, 2015 at 5:04:45 PM UTC+1, Dima Pasechnik wrote:
>
> Are floating point settings (some low level flags???)
> subtly different for Sage's Python and Sage itself? Namely, the same code
> s
On 9 December 2015 at 16:28, Nathann Cohen wrote:
>> Try this (6.10.beta7):
>
> This concept of a zero in mathematics is fishy. There is not any of
> our troubles that cannot be traced back to it.
>
> +1 for the removal of 0 in Sage.
Nice try, Nathann! I will obey, and indeed will remove nothing
> Try this (6.10.beta7):
This concept of a zero in mathematics is fishy. There is not any of
our troubles that cannot be traced back to it.
+1 for the removal of 0 in Sage.
Nathann
--
You received this message because you are subscribed to the Google Groups
"sage-devel" group.
To unsubscribe
Try this (6.10.beta7):
sage: K. = NumberField(x^2-15)
sage: three = K.ideal(3)
sage: zero = K(0)
sage: three.divides(zero)
...
Saved trace to /home/jec/.sage/crash_logs/sage_crash_hnuaJL.log
Unhandled SIGSEGV: A segmentatio
Are floating point settings (some low level flags???)
subtly different for Sage's Python and Sage itself? Namely, the same code
succeeds or fails, depending on whether
it is invoked in Sage's Python, or in Sage proper (with preparser(False)).
It is an iterative procedure (call to solvers.sdp() be
On Wednesday, 9 December 2015 13:33:48 UTC, Frédéric Chapoton wrote:
>
> Hello,
>
> what error do you see exactly ? The latest branch is reported as "pending"
> by two bots. If this persists, this could be because
> it is deemed unsafe by the bots. This happens when files are modified
> outside
On 9 December 2015 at 13:13, prateek sharma
wrote:
> Can you tell me how can I create a branch .When I do git-trac-checkout 5415
> It says "Newly created local branch: t/5415/problems_with_multifactorial_"
> I have made my changes on git.How can I commit those changes on trac.
> Please help.
This
Hello,
what error do you see exactly ? The latest branch is reported as "pending"
by two bots. If this persists, this could be because
it is deemed unsafe by the bots. This happens when files are modified
outside of src/sage (or a few other allowed dirs). Did you introduce the
change in module_
Can you tell me how can I create a branch .When I do git-trac-checkout 5415
It says "Newly created local branch: t/5415/problems_with_multifactorial_"
I have made my changes on git.How can I commit those changes on trac.
Please help.
On Tuesday, December 8, 2015 at 10:14:09 PM UTC+5:30, Nils Bruin
Hi,
+1, that seems to make sense, and it's a good idea to have both
semantics available.
Note that there are also complicated mixes:
sage: R. = RR[]
sage: Zxy = PolynomialRing(ZZ,'x,y,z')
sage: xx,yy,zz = Zxy.gens()
sage: (xx+yy).subs(x=x).parent()
Multivariate Polynomial Ring in x, y, z over Re
If its not too much effort I'd prefer a note that says that you need
sage-6.10 for El Capitan
--
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, Dec 9, 2015 at 9:51 AM, Volker Braun wrote:
> Harald, do you want to do that?
Yes, also, the website itself needs to be changed. Should I remove
that warning entirely?
-- harald
--
You received this message because you are subscribed to the Google Groups
"sage-devel" group.
To unsubsc
We could change the "Currently, SageMath does not work on the new OS X
10.11!" message on http://files.sagemath.org/osx/intel/index.html
Harald, do you want to do that?
--
You received this message because you are subscribed to the Google Groups
"sage-devel" group.
To unsubscribe from this gro
This is a new beta release for the new OSX binaries, available at
http://files.sagemath.org/osx/intel/index.html
This should now work just like the old binaries; When you start it the
first time the paths are automatically patched for the new location, but
you do not have to run any special scr
25 matches
Mail list logo
