On 2013-08-20 23:21, Andrew Gainer-Dewar wrote:
How about extending the input signature of Graph.is_connected() to
include an option
empty_graph_is_connected = False
-1 for needless complication.
--
You received this message because you are subscribed to the Google Groups
"sage-devel" gr
Is anyone arguing for returning True? If not, let's return False and
put a note about it in the docs.
On Tue, Aug 20, 2013 at 2:21 PM, Andrew Gainer-Dewar
wrote:
> How about extending the input signature of Graph.is_connected() to
> include an option
>
> empty_graph_is_connected = False
>
> ?
On 2013-08-21, Volker Braun wrote:
> Hmm doesn't work with slrn 1.0.1 but works with slrn pre1.0.2-9. I
> guess its a cutting-edge feature.
>
Thanks for pointng this out. The git version of slang needs a patch (see
below) on OSX, but otherwise it's all well (I can read these solid
blocks of base64
On Wednesday, August 21, 2013 8:55:09 PM UTC+1, jason wrote:
> On 8/21/13 12:28 PM, Volker Braun wrote:
> > In fact, I have never seen one where question mark had syntactic
> > meaning: "prime?(5)" returns true, and "prime(5)" returns 11.
>
> Interesting. That's standard scheme syntax for a pr
On 8/21/13 12:28 PM, Volker Braun wrote:
In fact, I have never seen one where question mark had syntactic
meaning: "prime?(5)" returns true, and "prime(5)" returns 11.
Interesting. That's standard scheme syntax for a predicate:
http://www.scheme.com/tspl3/intro.html#g2
Jason
--
You recei
I managed to get it to run in iced tea. I'm pretty sure they wrote the CAS
part themselves. Its definitely nothing for real work, but covers about
undergrad calculus (gymnasium in Germany). I don't recognize the syntax
from anywhere. In fact, I have never seen one where question mark had
syntac
I stumbled across Wiris [1] which purports to be "the global solution for
mathematics education". It includes various things - apparently a CAS and
a web formula editor, including a TinyMCE plugin [2] used in Blackboard,
which is how I found out about it. (It didn't work in my browser,
presum
On Wed, 21 Aug 2013 at 04:48PM +0200, Jeroen Demeyer wrote:
> Not everything is UTF-8, the relevant setting here is LC_CTYPE.
Setting LC_CTYPE to en_US.utf8 (and variants) didn't change anything.
Same for LC_ALL.
Dan
--
--- Dan Drake
- www.math.wisc.edu/~ddrake/
---
signature.asc
De
On Wednesday, August 21, 2013 5:15:34 AM UTC-7, Daniel Krenn wrote:
>
> For some file I get
>
> [combinat ] /path/to/file/blub.py:docstring of sage.combinat.blub:27:
> ERROR: Unexpected indentation.
>
> or "WARNING: Block quote ends without a blank line; unexpected
> unindent." as output.
Dan, what worked for me was to make sure that the locale settings were
utf8 (and not reset to something else in a startup file such as
.bashrc) and then I had to log out and in again. It was not enough to
start a new gnome-terminal as it seemed to "remember".
John
On 21 August 2013 15:48, Jeroen
On 2013-08-21 16:43, Dan Drake wrote:
If I may go back to the regular terminal stuff...I am seeing the "weird"
banner even though I try to have everything set to UTF-8.
Not everything is UTF-8, the relevant setting here is LC_CTYPE.
--
You received this message because you are subscribed to the
Hi Volker,
On 2013-08-21, Volker Braun wrote:
> Most messages in sage-devel are actually base64-encoded, and slrn displays
> them fine. What slrn trips over is content/multipart. RFC1341 is only from
> 1992, so its understandable that slrn hasn't caught up yet :-P Actually,
> it does ship wit
Hmm doesn't work with slrn 1.0.1 but works with slrn pre1.0.2-9. I guess
its a cutting-edge feature.
On Wednesday, August 21, 2013 3:13:53 PM UTC+1, Simon King wrote:
>
> Hi Volker,
>
> On 2013-08-21, Volker Braun > wrote:
> > Most messages in sage-devel are actually base64-encoded, and slrn
Most messages in sage-devel are actually base64-encoded, and slrn displays
them fine. What slrn trips over is content/multipart. RFC1341 is only from
1992, so its understandable that slrn hasn't caught up yet :-P Actually,
it does ship with support for it but its disabled by default for some
m
On 2013-08-21 04:18, Dima Pasechnik wrote:
If not, what you get probably is semi-trivial, as mpir config rejects
the compiler for no good reason, mistaking it for an old buggy "real" gcc.
See http://trac.sagemath.org/ticket/13948
--
You received this message because you are subscribed to the Go
Hi Volker,
On 2013-08-21, Volker Braun wrote:
> --=_Part_9509_16842449.1377077319452
> Content-Type: text/plain; charset=ISO-8859-1
>
> Slnr decodes base64 in bodies by default since version 0.9.6.4. Which is at
> least 10 years old by now. Which version are you using?
I use this (on openSu
On 2013-08-21, Volker Braun wrote:
> --=_Part_9509_16842449.1377077319452
> Content-Type: text/plain; charset=ISO-8859-1
>
> Slnr decodes base64 in bodies by default since version 0.9.6.4. Which is at
> least 10 years old by now. Which version are you using?
pre1.0.0-26
I guess Simon, who ask
For some file I get
[combinat ] /path/to/file/blub.py:docstring of sage.combinat.blub:27:
ERROR: Unexpected indentation.
or "WARNING: Block quote ends without a blank line; unexpected
unindent." as output.
I want to solve that (the error/warning message itself is kind of
clear), but probably
Hi!
I just opened a new ticket
http://trac.sagemath.org/ticket/15072
sage --version
seems to hang with sage-5.12.beta1 (not with sage-5.11) on MacOS.
This means that I cannot use the sage-combinat script any longer
(which is very inconvenient!).
Best,
Anne
--
You received this message becau
Slnr decodes base64 in bodies by default since version 0.9.6.4. Which is at
least 10 years old by now. Which version are you using?
On Wednesday, August 21, 2013 4:01:49 AM UTC+1, Dima Pasechnik wrote:
>
> > So, could you (or someone else) please tell me how to configure slrn so
> > that I can
How about extending the input signature of Graph.is_connected() to
include an option
empty_graph_is_connected = False
? (It could, of course, default to True instead, but I'm an enumeration
guy and think this is nonsense.)
Advantages, as I see them:
* True-ists and False-ists both get their
Hi!
On 2013-08-19, Volker Braun wrote:
> Obviously you are deleting something in the remove callback, causing=20
> another remove callback to be called.
Meanwhile we made progress (or even found a solution).
One indeed obtained the "recursion depth exceeded ... ignored", when one
has a MonoDict
22 matches
Mail list logo
