IMHO undecidability has exception semantics so really there is only one
correct solution, namely raise. Otherwise you get
sage: foo() == bar() # haha both Unknown
True
On Tuesday, December 1, 2015 at 11:20:53 PM UTC+1, vdelecroix wrote:
>
> Unknown is not broken. It just does not behave like
An error is perhaps the most appropriate but not very user friendly.
None is better but a bit disappointing
sage: my_equation.has_solution() # haha answer is None
sage:
And moreover has the same "boolean" behavior as Unknown
sage: None or False
False
sage: False or None
sage: not None
False
Its quite terrible, in Python you can either raise an exception or maybe
return None if you can't decide on a boolean return value. The only
redeeming quality of Unknown is that it documents that it doesn't work,
horray. IMHO we should deprecate it.
On Wednesday, November 25, 2015 at 5:56:02
Just completing the answers here, in case somebody needs it:
'view(g)' has a different behaviour in Sage and in SMC. In Sage it uses
LaTeX, while in SMC it is more or less equivalent to g.show(method='js')
(which relies on javascript/d3js, hence no latex whatsoever).
Currently, there is no way
On 01/12/15 15:18, Emmanuel Charpentier wrote:
Le mercredi 25 novembre 2015 12:28:45 UTC+1, vdelecroix a écrit :
Hello,
[ Snip... ]
The only way to fix Unknown would be to patch (non trivially) Python.
Boolean inherits from int... and it would be hard to have a third party
"Unknown" co
On Tue, Dec 1, 2015 at 10:08 AM, John H Palmieri wrote:
> On Tuesday, December 1, 2015 at 9:40:18 AM UTC-8, Pedro Cruz wrote:
>>
>> The following code (sage 6.9):
>>
>> sage: g = graphs.PetersenGraph()
>> sage: g.set_latex_options(vertex_color='green')
>> sage: view(g)
>>
>>
>> produces a black-an
Le mercredi 25 novembre 2015 12:28:45 UTC+1, vdelecroix a écrit :
>
> Hello,
>
[ Snip... ]
The only way to fix Unknown would be to patch (non trivially) Python.
> Boolean inherits from int... and it would be hard to have a third party
> "Unknown" coherent with this inheritance. There was a s
On 01/12/15 15:01, kcrisman wrote:
This is inconsistent (and documented ;-).
But is it documented someplace easy for Sage users to find? Thanks!
I would say "no". It is in the `__init__` method of the `UnknownClass`.
It should be moved to the main documentation class.
For the operat
On Tuesday, December 1, 2015 at 9:40:18 AM UTC-8, Pedro Cruz wrote:
>
> The following code (sage 6.9):
>
> sage: g = graphs.PetersenGraph()
> sage: g.set_latex_options(vertex_color='green')
> sage: view(g)
>
>
> produces a black-and-white graph.
>
Can you use "g.plot()" instead? If so, "g.plot?" l
>
>
>
> This is inconsistent (and documented ;-).
But is it documented someplace easy for Sage users to find? Thanks!
> For the operations "or" and
> "and" Python actually uses "__nonzero__". *Not* "__or__" and "__and__"
> which are the bitwise operation "|" and "&".
>
> They work as f
On Tue, Dec 1, 2015 at 9:40 AM, Pedro Cruz wrote:
> The following code (sage 6.9):
>
> sage: g = graphs.PetersenGraph()
> sage: g.set_latex_options(vertex_color='green')
> sage: view(g)
>
>
> produces a black-and-white graph.
>
> In SMC produces a graph with blue vertices.
>
> What can I do?
I ha
The following code (sage 6.9):
sage: g = graphs.PetersenGraph()
sage: g.set_latex_options(vertex_color='green')
sage: view(g)
produces a black-and-white graph.
In SMC produces a graph with blue vertices.
What can I do?
Thank you,
Pedro
--
You received this message because you are subscribe
The following code (sage 6.9):
sage: g = graphs.PetersenGraph()
sage: g.set_latex_options(vertex_color='green')
sage: view(g)
produces a black-and-white graph.
In SMC produces a graph with blue vertices.
What can I do?
Thank you,
Pedro
--
You received this message because you are subscri
The following code (sage 6.9):
sage: g = graphs.PetersenGraph()
sage: g.set_latex_options(vertex_color='green')
sage: view(g)
produces a black-and-white graph.
In SMC produces a graph with blue vertices.
What can I do?
Thank you,
Pedro
--
You received this message because you are subscribe
On Fri, Nov 27, 2015 at 1:39 AM, Pierre wrote:
> Hi !
>
> Is it possible, in a sage worksheet on SMC, to hide the traceback and just
> keep the last line?
No, this isn't implemented yet. Here's a ticket:
https://github.com/sagemathinc/smc/issues/299
>
> I have the same question about the ju
Thanks,
Got it .
--
You received this message because you are subscribed to the Google Groups
"sage-support" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to sage-support+unsubscr...@googlegroups.com.
To post to this group, send email to sage
On Tuesday, 1 December 2015 08:44:47 UTC, Ninad Bhat wrote:
>
> Hi,
> I installed sage from source code(downloading it from git)
>
from git?
Do you mean github, or sage trac git server?
(you can tell by looking at the output of
git remote -v
)
Note that 6.10 is not yet release, there
On Wednesday, 25 November 2015 22:35:16 UTC, Peter Mueller wrote:
>
> The last activity of this thread is almost 6 years ago. So I'm wondering
> if in the meantime it is possible to use latex code in text annotations for
> 3d graphics. I don't care about toys like jmol -- it would be fine to
>
Hi,
I installed sage from source code(downloading it from git).Is there a
way to update it to sage 6.10 without downloading it again?
Thanks in advance.
--
You received this message because you are subscribed to the Google Groups
"sage-support" group.
To unsubscribe from this group and st
19 matches
Mail list logo
