>
> My favorite example: Sage cannot solve x == sqrt(x):
>
> sage: solve(x == sqrt(x), x)
> [x == sqrt(x)]
>
I'm not so sure whether this is really interesting, but since the
discussion is there, FriCAS does the right thing here:
(1) -> solve(x=sqrt(x), x)
(1) [x= 1,x= 0]
Hi,
Le 16/12/2014 01:20, rjf a écrit :
Well, you could assert that there is no discussion, but you are apparently
wrong.
May I suggest you to square the equation then solve the obtained
polynomial equation? (Then of course, since squaring is an implication,
check that the obtained solutions
Thanks for the feedback.
I don't know much about MPIR.
I'm talking to some GMP developers.
There is someone there who is planning on improving the situation
there...at least, for the temporary memory allocations done by mpn-level
routines in GMP, which is my main concern.
On Monday, December 15, 2
On Tue, Dec 16, 2014 at 1:20 AM, rjf wrote:
>
> Well, you could assert that there is no discussion, but you are apparently
> wrong.
> sqrt has 2 values except at zero. (in the complex plane, or on the real
> line).
>
> for example, sqrt(9) is the set {-3,3} . That is how it is extended.
> and
On Monday, December 15, 2014 11:44:25 AM UTC-8, William wrote:
>
> On Mon, Dec 15, 2014 at 11:34 AM, rjf >
> wrote:
>
> >> William said ... There's no question that in say 200?, Microsoft
> Windows support was
> >> absolutely critical for widespread adoption of a piece of software in
> >> a
Well, you could assert that there is no discussion, but you are apparently
wrong.
sqrt has 2 values except at zero. (in the complex plane, or on the real
line).
for example, sqrt(9) is the set {-3,3} . That is how it is extended.
and sqrt(1) is {-1,1}.
Is it true that 1 is equal to {-
On 2014-12-15 20:15, Victor Shoup wrote:
As I get closer to finishing this, I'm thinking more about gmp's lack of
proper error handling, which is just like NTL's currently: print error message
and
call abort.
No, MPIR (I haven't checked GMP, but I guess it's the same) is far
worse. MPIR doesn't
On 2014-12-15 20:47, rjf wrote:
Maybe it's an appropriate response?
No, it's not.
Note that dividing both sides by sqrt(x) gives you sqrt(x)=1.
So the solution is x=1 maybe.
But x=0 is obviously a solution too.
I think there is absolutely no discussion that the solution set of
[sqrt(x) == x]
On Mon, 15 Dec 2014 12:53:25 kcrisman wrote:
> https://www.openhub.net/p/sage
>
> What the heck happened in June 2013 that supposedly tripled our code size?
> Is this the git conversion?
I don't know but looking on github on the release page:
https://github.com/sagemath/sage/releases?after=6.1.be
https://www.openhub.net/p/sage
What the heck happened in June 2013 that supposedly tripled our code size?
Is this the git conversion?
--
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
On Monday, December 15, 2014 11:20:10 AM UTC-8, François wrote:
>
> Installing sage as root are we? This is not supported.
>
Allow me to advertise http://trac.sagemath.org/ticket/17420. This should
print a warning early in the build process if trying to build as root.
Please review!
John
On Friday, December 5, 2014 1:18:12 AM UTC-8, Jeroen Demeyer wrote:
>
> On 2014-12-05 08:17, Nathann Cohen wrote:
> > In your past experiences (possibly when using Sage to teach in a
> > classroom), in which areas do you think we are behind users'
> expectations ?
> I think the worst is symbo
On Mon, Dec 15, 2014 at 11:34 AM, rjf wrote:
>
>
> On Friday, December 5, 2014 12:39:55 PM UTC-8, William wrote:
>>
>> On Fri, Dec 5, 2014 at 12:19 PM, maldun wrote:
>> > What we still don't have is a working windows version. This is still a
>> > big
>> > blocker for being succesfull.
>>
>> I don
On Friday, December 5, 2014 12:39:55 PM UTC-8, William wrote:
>
> On Fri, Dec 5, 2014 at 12:19 PM, maldun >
> wrote:
> > What we still don't have is a working windows version. This is still a
> big
> > blocker for being succesfull.
>
> I don't want to in any way discourage anybody from worki
Installing sage as root are we? This is not supported.
François
> On 16/12/2014, at 05:18, Soomin Jeon wrote:
>
> I have problems in installing sage 6.4.1 using source, and the error message
> is as below:
>
> Error instal
I've just uploaded a bug-fix version of NTL (version 7.0.2) at
www.shoup.net/ntl.
Probably does not affect any Sage code, though.
Also, I'm getting closer to finish my quixotic quest to make NTL exception
safe.
It is an interesting experience, as I'm learning how to make use of "modern"
C++ idio
So I attached the file 'pynac-0.3.2.log'.
2014. 12. 16. 오전 2:11에 "kcrisman" 님이 작성:
> package: pynac-0.3.2
>> log file: /usr/local/sage-6.4.1/logs/pkgs/pynac-0.3.2.log
>>
>>
> Without seeing this file (or at least the tail end of it) it will be
> impossible to tell, probably.
>
> --
> You received
>
> package: pynac-0.3.2
> log file: /usr/local/sage-6.4.1/logs/pkgs/pynac-0.3.2.log
>
>
Without seeing this file (or at least the tail end of it) it will be
impossible to tell, probably.
--
You received this message because you are subscribed to the Google Groups
"sage-devel" group.
To unsub
I have problems in installing sage 6.4.1 using source, and the error
message is as below:
Error installing package pynac-0.3.2
Please email sage-devel (
>
> This will be more specificy than "trac sage keyword1 keyword2". Maybe we
> should add a site-specific google search box to our trac front page?
>
>>
Yes, please do! Amazingly, Google's search for Trac my inefficient way is
way, way better than Google's search of Google groups threads even u
The difference is in how cpdef functions interact with Cython vs Python
classes. If you want to override a cpdef method in a *Python* subclass
then you must use def (of course). But in a *Cython* subclass, you must
use cpdef. If you accidentally use def instead in a Cython class then it
doesn't
Yop !
> thanks for your answer, however, I'm not sure it solves my problem: yes, it
> is possible to change the viewer to something else, but for some reason the
> viewer does not open in the background (as a process) but in the foreground.
> So I can't continue with experimentation without closi
Hi Nathann!
thanks for your answer, however, I'm not sure it solves my problem: yes,
it is possible to change the viewer to something else, but for some reason
the viewer does not open in the background (as a process) but in the
foreground. So I can't continue with experimentation without clo
I don't understand what your problem is. If xdg-open is being called then
Sage is doing everything as it should. You might want to configure xdg (man
xdg-settings) to open your preferred applications.
On Monday, December 15, 2014 8:47:54 AM UTC+1, Martin R wrote:
>
> Hi there!
>
> I posted thi
Hello !
I have the following lines in my ~/.sage/init.sage file
from sage.misc.viewer import viewer
viewer.png_viewer('google-chrome')
the viewer.pdf_viewer method will let you change the default pdf viewer in
Sage. It is all there:
http://www.sagemath.org/doc/reference/misc/sage/misc/viewer.h
On Monday, December 15, 2014 2:26:59 PM UTC+9, Soomin Jeon wrote:
>
> I installed sage 5.9 last year and I found that sage 6.4.1 is released.
> So I try to update the sage version 5.9 to 6.4.1 using the command 'sage
> -upgrade', however, it just upgraded the sage version to 5.13.
> If I want to
26 matches
Mail list logo
