On 2016-03-31 23:15, Ursula Whitcher wrote:

> I noticed that the Wiki entry on citing Sage

>

> https://wiki.sagemath.org/Publications_using_SAGE

>

> does not reflect the rebranding of Sage as SageMath. How should the

> citation change?

In my opinion, yes!

I suggest something like:

@Manual{SageMath:2016:7.1,

key = {SageMath},

author = {The SageMath Developers},

title = {{SageMath} {M}athematics {S}oftware ({V}ersion 7.1)},

note = {\url{http://www.sagemath.org}},

year = 2016,

}

Best wishes

Daniel

--

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+unsubscribe@googlegroups.com.

To post to this group, send email to sage-devel@googlegroups.com.

Visit this group at https://groups.google.com/group/sage-devel.

For more options, visit https://groups.google.com/d/optout.

## วันพฤหัสบดีที่ 31 มีนาคม พ.ศ. 2559

### Re: [sage-devel] Pythonics

On Mar 31, 2016, at 16:15 , David Roe wrote:

> On Thu, Mar 31, 2016 at 7:11 PM, Justin C. Walker <justin@mac.com> wrote:

>

>>

>> On Mar 31, 2016, at 15:37 , Vincent Delecroix wrote:

>>

>>> On 31/03/16 18:22, Johannes wrote:

>>>> On 31.03.2016 23:08, Justin C. Walker wrote:

>>>>> 2. Is there a way to tell, when hasattr(X, "foo") returns True,

>>>>> whether "X.foo" can be called?

>>>>

>>>> X.foo and x.foo.__call__ is None

>>>

>>> !?

>>>

>>> The only way to go here is

>>>

>>> if callable(X.foo):

>>> print "X.foo is callable"

>>

>> Thanks for the all the responses. They help, but I'm sensing confusion

>> (at least on my part):

>>

>> sage: Q

>> Univariate Quotient Polynomial Ring in xbar over Rational Field with

>> modulus x^2

>>

>> sage: hasattr(Q,"is_integral_domain")

>> True

>>

>> sage: Q.is_integral_domain

>> <built-in method is_integral_domain of

>> PolynomialQuotientRing_generic_with_category object at 0x19c8dcec0>

>>

>> sage: callable(Q.is_integral_domain)

>> True

>>

>> sage: Q.is_integral_domain()

>> ---------------------------------------------------------------------------

>> NotImplementedError Traceback (most recent call last)

>> <ipython-input-48-73145f43c3d0> in <module>()

>> ----> 1 Q.is_integral_domain()

>> NotImplementedError:

>>

>> Help and corrections much appreciated, as always.

>>

>

> Just because a method is callable doesn't mean that it can't raise

> exceptions, including NotImplementedErrors. There's no reasonable way to

> tell if a method will raise an exception or not without calling it.

Shazbat! I was afraid of that.

Thanks for the clarification. Back to the keyboard...

--

Justin C. Walker, Curmudgeon at Large

Institute for the Absorption of Federal Funds

-----------

My wife 'n kids 'n dogs are gone,

I can't get Jesus on the phone,

But Ol' Milwaukee's Best is my best friend.

-----------

--

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+unsubscribe@googlegroups.com.

To post to this group, send email to sage-devel@googlegroups.com.

Visit this group at https://groups.google.com/group/sage-devel.

For more options, visit https://groups.google.com/d/optout.

> On Thu, Mar 31, 2016 at 7:11 PM, Justin C. Walker <justin@mac.com> wrote:

>

>>

>> On Mar 31, 2016, at 15:37 , Vincent Delecroix wrote:

>>

>>> On 31/03/16 18:22, Johannes wrote:

>>>> On 31.03.2016 23:08, Justin C. Walker wrote:

>>>>> 2. Is there a way to tell, when hasattr(X, "foo") returns True,

>>>>> whether "X.foo" can be called?

>>>>

>>>> X.foo and x.foo.__call__ is None

>>>

>>> !?

>>>

>>> The only way to go here is

>>>

>>> if callable(X.foo):

>>> print "X.foo is callable"

>>

>> Thanks for the all the responses. They help, but I'm sensing confusion

>> (at least on my part):

>>

>> sage: Q

>> Univariate Quotient Polynomial Ring in xbar over Rational Field with

>> modulus x^2

>>

>> sage: hasattr(Q,"is_integral_domain")

>> True

>>

>> sage: Q.is_integral_domain

>> <built-in method is_integral_domain of

>> PolynomialQuotientRing_generic_with_category object at 0x19c8dcec0>

>>

>> sage: callable(Q.is_integral_domain)

>> True

>>

>> sage: Q.is_integral_domain()

>> ---------------------------------------------------------------------------

>> NotImplementedError Traceback (most recent call last)

>> <ipython-input-48-73145f43c3d0> in <module>()

>> ----> 1 Q.is_integral_domain()

>> NotImplementedError:

>>

>> Help and corrections much appreciated, as always.

>>

>

> Just because a method is callable doesn't mean that it can't raise

> exceptions, including NotImplementedErrors. There's no reasonable way to

> tell if a method will raise an exception or not without calling it.

Shazbat! I was afraid of that.

Thanks for the clarification. Back to the keyboard...

--

Justin C. Walker, Curmudgeon at Large

Institute for the Absorption of Federal Funds

-----------

My wife 'n kids 'n dogs are gone,

I can't get Jesus on the phone,

But Ol' Milwaukee's Best is my best friend.

-----------

--

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+unsubscribe@googlegroups.com.

To post to this group, send email to sage-devel@googlegroups.com.

Visit this group at https://groups.google.com/group/sage-devel.

For more options, visit https://groups.google.com/d/optout.

### Re: [sage-devel] Pythonics

On Thu, Mar 31, 2016 at 7:11 PM, Justin C. Walker <justin@mac.com> wrote:

On Mar 31, 2016, at 15:37 , Vincent Delecroix wrote:

> On 31/03/16 18:22, Johannes wrote:

>> On 31.03.2016 23:08, Justin C. Walker wrote:

>>> 2. Is there a way to tell, when hasattr(X, "foo") returns True,

>>> whether "X.foo" can be called?

>>

>> X.foo and x.foo.__call__ is None

>

> !?

>

> The only way to go here is

>

> if callable(X.foo):

> print "X.foo is callable"

Thanks for the all the responses. They help, but I'm sensing confusion (at least on my part):

sage: Q

Univariate Quotient Polynomial Ring in xbar over Rational Field with modulus x^2

sage: hasattr(Q,"is_integral_domain")

True

sage: Q.is_integral_domain

<built-in method is_integral_domain of PolynomialQuotientRing_generic_with_category object at 0x19c8dcec0>

sage: callable(Q.is_integral_domain)

True

sage: Q.is_integral_domain()

---------------------------------------------------------------------------

NotImplementedError Traceback (most recent call last)

<ipython-input-48-73145f43c3d0> in <module>()

----> 1 Q.is_integral_domain()

NotImplementedError:

Help and corrections much appreciated, as always.

Just because a method is callable doesn't mean that it can't raise exceptions, including NotImplementedErrors. There's no reasonable way to tell if a method will raise an exception or not without calling it.

David

Thanks!

--

Justin C. Walker

Director

Institute for the Enhancement of the Director's Income

--

Fame is fleeting, but obscurity

just drags on and on. F&E

--

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+unsubscribe@googlegroups.com.

To post to this group, send email to sage-devel@googlegroups.com.

Visit this group at https://groups.google.com/group/sage-devel.

For more options, visit https://groups.google.com/d/optout.

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+unsubscribe@googlegroups.com.

To post to this group, send email to sage-devel@googlegroups.com.

Visit this group at https://groups.google.com/group/sage-devel.

For more options, visit https://groups.google.com/d/optout.

### Re: [sage-devel] Pythonics

On Mar 31, 2016, at 15:37 , Vincent Delecroix wrote:

> On 31/03/16 18:22, Johannes wrote:

>> On 31.03.2016 23:08, Justin C. Walker wrote:

>>> 2. Is there a way to tell, when hasattr(X, "foo") returns True,

>>> whether "X.foo" can be called?

>>

>> X.foo and x.foo.__call__ is None

>

> !?

>

> The only way to go here is

>

> if callable(X.foo):

> print "X.foo is callable"

Thanks for the all the responses. They help, but I'm sensing confusion (at least on my part):

sage: Q

Univariate Quotient Polynomial Ring in xbar over Rational Field with modulus x^2

sage: hasattr(Q,"is_integral_domain")

True

sage: Q.is_integral_domain

<built-in method is_integral_domain of PolynomialQuotientRing_generic_with_category object at 0x19c8dcec0>

sage: callable(Q.is_integral_domain)

True

sage: Q.is_integral_domain()

---------------------------------------------------------------------------

NotImplementedError Traceback (most recent call last)

<ipython-input-48-73145f43c3d0> in <module>()

----> 1 Q.is_integral_domain()

NotImplementedError:

Help and corrections much appreciated, as always.

Thanks!

--

Justin C. Walker

Director

Institute for the Enhancement of the Director's Income

--

Fame is fleeting, but obscurity

just drags on and on. F&E

--

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+unsubscribe@googlegroups.com.

To post to this group, send email to sage-devel@googlegroups.com.

Visit this group at https://groups.google.com/group/sage-devel.

For more options, visit https://groups.google.com/d/optout.

> On 31/03/16 18:22, Johannes wrote:

>> On 31.03.2016 23:08, Justin C. Walker wrote:

>>> 2. Is there a way to tell, when hasattr(X, "foo") returns True,

>>> whether "X.foo" can be called?

>>

>> X.foo and x.foo.__call__ is None

>

> !?

>

> The only way to go here is

>

> if callable(X.foo):

> print "X.foo is callable"

Thanks for the all the responses. They help, but I'm sensing confusion (at least on my part):

sage: Q

Univariate Quotient Polynomial Ring in xbar over Rational Field with modulus x^2

sage: hasattr(Q,"is_integral_domain")

True

sage: Q.is_integral_domain

<built-in method is_integral_domain of PolynomialQuotientRing_generic_with_category object at 0x19c8dcec0>

sage: callable(Q.is_integral_domain)

True

sage: Q.is_integral_domain()

---------------------------------------------------------------------------

NotImplementedError Traceback (most recent call last)

<ipython-input-48-73145f43c3d0> in <module>()

----> 1 Q.is_integral_domain()

NotImplementedError:

Help and corrections much appreciated, as always.

Thanks!

--

Justin C. Walker

Director

Institute for the Enhancement of the Director's Income

--

Fame is fleeting, but obscurity

just drags on and on. F&E

--

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+unsubscribe@googlegroups.com.

To post to this group, send email to sage-devel@googlegroups.com.

Visit this group at https://groups.google.com/group/sage-devel.

For more options, visit https://groups.google.com/d/optout.

### Re: [sage-devel] Pythonics

On Mar 31, 2016, at 14:17 , William Stein wrote:

> On Thu, Mar 31, 2016 at 2:08 PM, Justin C. Walker <justin@mac.com> wrote:

>> Hi, all,

>>

>> I have couple of questions regarding "attributes" in Python/Sage:

>>

>> 1. If hasattr(X, "foo") returns True, does that mean that "X.foo" should not blow up?

>

> What's the definition of "blow up"? I think X.foo could -- due to

> Python "properties" -- run arbitrary Python code, e.g., to launch a

> missile (or raise an exception).

Ooh...I have to try that...

In my particular case, I'm not expecting percussion. I'm seeing exceptions (see following email).

>>

>> 2. Is there a way to tell, when hasattr(X, "foo") returns True, whether "X.foo" can be called?

>>

>> 3. If "X.foo" is callable, is it expected that "X.foo()" will *not* blow up with "Not Implemented"?

>

> Not necessarily.

>

> try:

> X.foo()

> except (NotImplementedError, AttributeError):

> ....

That's always the fall-back, I know. I suppose with object orientation, one has to expect this kind of thing...

Thanks!

--

Justin C. Walker, Curmudgeon at Large

Institute for the Absorption of Federal Funds

-----------

I'm beginning to like the cut of his jibberish.

-----------

--

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+unsubscribe@googlegroups.com.

To post to this group, send email to sage-devel@googlegroups.com.

Visit this group at https://groups.google.com/group/sage-devel.

For more options, visit https://groups.google.com/d/optout.

> On Thu, Mar 31, 2016 at 2:08 PM, Justin C. Walker <justin@mac.com> wrote:

>> Hi, all,

>>

>> I have couple of questions regarding "attributes" in Python/Sage:

>>

>> 1. If hasattr(X, "foo") returns True, does that mean that "X.foo" should not blow up?

>

> What's the definition of "blow up"? I think X.foo could -- due to

> Python "properties" -- run arbitrary Python code, e.g., to launch a

> missile (or raise an exception).

Ooh...I have to try that...

In my particular case, I'm not expecting percussion. I'm seeing exceptions (see following email).

>>

>> 2. Is there a way to tell, when hasattr(X, "foo") returns True, whether "X.foo" can be called?

>>

>> 3. If "X.foo" is callable, is it expected that "X.foo()" will *not* blow up with "Not Implemented"?

>

> Not necessarily.

>

> try:

> X.foo()

> except (NotImplementedError, AttributeError):

> ....

That's always the fall-back, I know. I suppose with object orientation, one has to expect this kind of thing...

Thanks!

--

Justin C. Walker, Curmudgeon at Large

Institute for the Absorption of Federal Funds

-----------

I'm beginning to like the cut of his jibberish.

-----------

--

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+unsubscribe@googlegroups.com.

To post to this group, send email to sage-devel@googlegroups.com.

Visit this group at https://groups.google.com/group/sage-devel.

For more options, visit https://groups.google.com/d/optout.

### Re: [sage-devel] Pythonics

On 31/03/16 18:22, Johannes wrote:

> On 31.03.2016 23:08, Justin C. Walker wrote:

>> 2. Is there a way to tell, when hasattr(X, "foo") returns True,

>> whether "X.foo" can be called?

>

> X.foo and x.foo.__call__ is None

!?

The only way to go here is

if callable(X.foo):

print "X.foo is callable"

Vincent

--

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+unsubscribe@googlegroups.com.

To post to this group, send email to sage-devel@googlegroups.com.

Visit this group at https://groups.google.com/group/sage-devel.

For more options, visit https://groups.google.com/d/optout.

> On 31.03.2016 23:08, Justin C. Walker wrote:

>> 2. Is there a way to tell, when hasattr(X, "foo") returns True,

>> whether "X.foo" can be called?

>

> X.foo and x.foo.__call__ is None

!?

The only way to go here is

if callable(X.foo):

print "X.foo is callable"

Vincent

--

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+unsubscribe@googlegroups.com.

To post to this group, send email to sage-devel@googlegroups.com.

Visit this group at https://groups.google.com/group/sage-devel.

For more options, visit https://groups.google.com/d/optout.

### Re: [sage-devel] Pythonics

On 31.03.2016 23:08, Justin C. Walker wrote:

> Hi, all,

>

> I have couple of questions regarding "attributes" in Python/Sage:

>

> 1. If hasattr(X, "foo") returns True, does that mean that "X.foo" should not blow up?

>

this means X.foo is defined.

> 2. Is there a way to tell, when hasattr(X, "foo") returns True, whether "X.foo" can be called?

X.foo and x.foo.__call__ is None

>

> 3. If "X.foo" is callable, is it expected that "X.foo()" will *not* blow up with "Not Implemented"?

No. For example you can have

class x(object):

def foo(self): raise NotImplemented()

x = new X()

x.foo() # this will raise a not implemented exception. but x.foo is well

defined.

bg,

Jo

>

> I'm hoping that makes sense...

>

> Thanks!

>

> Justin

>

> --

> Justin C. Walker, Curmudgeon-At-Large, Director

> Institute for the Enhancement of the Director's Income

> --------

> The path of least resistance:

> it's not just for electricity any more.

> --------

>

>

>

--

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+unsubscribe@googlegroups.com.

To post to this group, send email to sage-devel@googlegroups.com.

Visit this group at https://groups.google.com/group/sage-devel.

For more options, visit https://groups.google.com/d/optout.

> Hi, all,

>

> I have couple of questions regarding "attributes" in Python/Sage:

>

> 1. If hasattr(X, "foo") returns True, does that mean that "X.foo" should not blow up?

>

this means X.foo is defined.

> 2. Is there a way to tell, when hasattr(X, "foo") returns True, whether "X.foo" can be called?

X.foo and x.foo.__call__ is None

>

> 3. If "X.foo" is callable, is it expected that "X.foo()" will *not* blow up with "Not Implemented"?

No. For example you can have

class x(object):

def foo(self): raise NotImplemented()

x = new X()

x.foo() # this will raise a not implemented exception. but x.foo is well

defined.

bg,

Jo

>

> I'm hoping that makes sense...

>

> Thanks!

>

> Justin

>

> --

> Justin C. Walker, Curmudgeon-At-Large, Director

> Institute for the Enhancement of the Director's Income

> --------

> The path of least resistance:

> it's not just for electricity any more.

> --------

>

>

>

--

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+unsubscribe@googlegroups.com.

To post to this group, send email to sage-devel@googlegroups.com.

Visit this group at https://groups.google.com/group/sage-devel.

For more options, visit https://groups.google.com/d/optout.

### Re: [sage-devel] Pythonics

On Thu, Mar 31, 2016 at 2:08 PM, Justin C. Walker <justin@mac.com> wrote:

> Hi, all,

>

> I have couple of questions regarding "attributes" in Python/Sage:

>

> 1. If hasattr(X, "foo") returns True, does that mean that "X.foo" should not blow up?

What's the definition of "blow up"? I think X.foo could -- due to

Python "properties" -- run arbitrary Python code, e.g., to launch a

missile (or raise an exception).

>

> 2. Is there a way to tell, when hasattr(X, "foo") returns True, whether "X.foo" can be called?

>

> 3. If "X.foo" is callable, is it expected that "X.foo()" will *not* blow up with "Not Implemented"?

Not necessarily.

try:

X.foo()

except (NotImplementedError, AttributeError):

....

>

> I'm hoping that makes sense...

>

> Thanks!

>

> Justin

>

> --

> Justin C. Walker, Curmudgeon-At-Large, Director

> Institute for the Enhancement of the Director's Income

> --------

> The path of least resistance:

> it's not just for electricity any more.

> --------

>

>

>

> --

> 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+unsubscribe@googlegroups.com.

> To post to this group, send email to sage-devel@googlegroups.com.

> Visit this group at https://groups.google.com/group/sage-devel.

> For more options, visit https://groups.google.com/d/optout.

--

William (http://wstein.org)

--

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+unsubscribe@googlegroups.com.

To post to this group, send email to sage-devel@googlegroups.com.

Visit this group at https://groups.google.com/group/sage-devel.

For more options, visit https://groups.google.com/d/optout.

> Hi, all,

>

> I have couple of questions regarding "attributes" in Python/Sage:

>

> 1. If hasattr(X, "foo") returns True, does that mean that "X.foo" should not blow up?

What's the definition of "blow up"? I think X.foo could -- due to

Python "properties" -- run arbitrary Python code, e.g., to launch a

missile (or raise an exception).

>

> 2. Is there a way to tell, when hasattr(X, "foo") returns True, whether "X.foo" can be called?

>

> 3. If "X.foo" is callable, is it expected that "X.foo()" will *not* blow up with "Not Implemented"?

Not necessarily.

try:

X.foo()

except (NotImplementedError, AttributeError):

....

>

> I'm hoping that makes sense...

>

> Thanks!

>

> Justin

>

> --

> Justin C. Walker, Curmudgeon-At-Large, Director

> Institute for the Enhancement of the Director's Income

> --------

> The path of least resistance:

> it's not just for electricity any more.

> --------

>

>

>

> --

> 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+unsubscribe@googlegroups.com.

> To post to this group, send email to sage-devel@googlegroups.com.

> Visit this group at https://groups.google.com/group/sage-devel.

> For more options, visit https://groups.google.com/d/optout.

--

William (http://wstein.org)

--

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+unsubscribe@googlegroups.com.

To post to this group, send email to sage-devel@googlegroups.com.

Visit this group at https://groups.google.com/group/sage-devel.

For more options, visit https://groups.google.com/d/optout.

### [sage-devel] citing Sage: the SageMath version

I noticed that the Wiki entry on citing Sage

https://wiki.sagemath.org/Publications_using_SAGE

does not reflect the rebranding of Sage as SageMath. How should the citation change?

--Ursula.

-- https://wiki.sagemath.org/Publications_using_SAGE

does not reflect the rebranding of Sage as SageMath. How should the citation change?

--Ursula.

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+unsubscribe@googlegroups.com.

To post to this group, send email to sage-devel@googlegroups.com.

Visit this group at https://groups.google.com/group/sage-devel.

For more options, visit https://groups.google.com/d/optout.

### [sage-devel] Pythonics

Hi, all,

I have couple of questions regarding "attributes" in Python/Sage:

1. If hasattr(X, "foo") returns True, does that mean that "X.foo" should not blow up?

2. Is there a way to tell, when hasattr(X, "foo") returns True, whether "X.foo" can be called?

3. If "X.foo" is callable, is it expected that "X.foo()" will *not* blow up with "Not Implemented"?

I'm hoping that makes sense...

Thanks!

Justin

--

Justin C. Walker, Curmudgeon-At-Large, Director

Institute for the Enhancement of the Director's Income

--------

The path of least resistance:

it's not just for electricity any more.

--------

--

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+unsubscribe@googlegroups.com.

To post to this group, send email to sage-devel@googlegroups.com.

Visit this group at https://groups.google.com/group/sage-devel.

For more options, visit https://groups.google.com/d/optout.

I have couple of questions regarding "attributes" in Python/Sage:

1. If hasattr(X, "foo") returns True, does that mean that "X.foo" should not blow up?

2. Is there a way to tell, when hasattr(X, "foo") returns True, whether "X.foo" can be called?

3. If "X.foo" is callable, is it expected that "X.foo()" will *not* blow up with "Not Implemented"?

I'm hoping that makes sense...

Thanks!

Justin

--

Justin C. Walker, Curmudgeon-At-Large, Director

Institute for the Enhancement of the Director's Income

--------

The path of least resistance:

it's not just for electricity any more.

--------

--

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+unsubscribe@googlegroups.com.

To post to this group, send email to sage-devel@googlegroups.com.

Visit this group at https://groups.google.com/group/sage-devel.

For more options, visit https://groups.google.com/d/optout.

### [sage-devel] Re: online documentation and "long time"

I created ticket 20339 for that, and fixed it. (needs review if you wish)

El martes, 22 de marzo de 2016, 9:49:29 (UTC+1), Samuel Lelievre escribió:

-- El martes, 22 de marzo de 2016, 9:49:29 (UTC+1), Samuel Lelievre escribió:

The page

http://doc.sagemath.org/html/en/reference/plotting/sage/ plot/plot.html

has this:

Pi Axis

sage: g1 = plot(sin(x), 0, 2*pi)

sage: g2 = plot(cos(x), 0, 2*pi, linestyle = "--")

sage: (g1+g2).show(ticks=pi/6, tick_formatter=pi) # long time

# show their sum, nicely formatted

with no illustration appearing after the code.

Shouldn't the "long time" stuff appear anyway in the online documentation?

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+unsubscribe@googlegroups.com.

To post to this group, send email to sage-devel@googlegroups.com.

Visit this group at https://groups.google.com/group/sage-devel.

For more options, visit https://groups.google.com/d/optout.

### Re: [sage-devel] matrix rational_form

Hi William, Thanks for the reply. I see that decomposition probably does give info that I could use to get the transition matrix. I'll think about it.

Victor

PS. How massive is your iPhone 6 plus :-)?

On Thursday, March 31, 2016 at 11:48:49 AM UTC-4, William wrote:

-- Victor

PS. How massive is your iPhone 6 plus :-)?

On Thursday, March 31, 2016 at 11:48:49 AM UTC-4, William wrote:

On Thursday, March 31, 2016, VictorMiller <victor...@gmail.com> wrote:The method rational_form for matrices just returns the class representative of the conjugacy class of a matrix by other rational matrices. A similar function PrimaryRationalForm in magma returns 3 things -- the class representative, a rational matrix which, when conjugated by the input, gives the representative, and a list of pairs: irreducible polynomial and multplicity. It would be nice if SAGE could return the same things as an option. The third one is easy to reconstruct from SAGE's output (since it outputs a subdivided matrix), but the second one isn't

VictorQuick remark: You might also find the decomposition method of square matrices helpful for whatever problem you're really trying to solve...--

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+unsubscribe@googlegroups.com .

To post to this group, send email to sage-devel@googlegroups.com.

Visit this group at https://groups.google.com/group/sage-devel .

For more options, visit https://groups.google.com/d/optout .

--

Sent from my massive iPhone 6 plus.

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+unsubscribe@googlegroups.com.

To post to this group, send email to sage-devel@googlegroups.com.

Visit this group at https://groups.google.com/group/sage-devel.

For more options, visit https://groups.google.com/d/optout.

### Re: [sage-devel] matrix rational_form

On Thursday, March 31, 2016, VictorMiller <victorsmiller@gmail.com> wrote:

The method rational_form for matrices just returns the class representative of the conjugacy class of a matrix by other rational matrices. A similar function PrimaryRationalForm in magma returns 3 things -- the class representative, a rational matrix which, when conjugated by the input, gives the representative, and a list of pairs: irreducible polynomial and multplicity. It would be nice if SAGE could return the same things as an option. The third one is easy to reconstruct from SAGE's output (since it outputs a subdivided matrix), but the second one isn't

Victor

Quick remark: You might also find the decomposition method of square matrices helpful for whatever problem you're really trying to solve...

--

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+unsubscribe@googlegroups.com.

To post to this group, send email to sage-devel@googlegroups.com.

Visit this group at https://groups.google.com/group/sage-devel.

For more options, visit https://groups.google.com/d/optout.

--

Sent from my massive iPhone 6 plus.

--

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+unsubscribe@googlegroups.com.

To post to this group, send email to sage-devel@googlegroups.com.

Visit this group at https://groups.google.com/group/sage-devel.

For more options, visit https://groups.google.com/d/optout.

### [sage-devel] matrix rational_form

The method rational_form for matrices just returns the class representative of the conjugacy class of a matrix by other rational matrices. A similar function PrimaryRationalForm in magma returns 3 things -- the class representative, a rational matrix which, when conjugated by the input, gives the representative, and a list of pairs: irreducible polynomial and multplicity. It would be nice if SAGE could return the same things as an option. The third one is easy to reconstruct from SAGE's output (since it outputs a subdivided matrix), but the second one isn't

Victor

-- Victor

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+unsubscribe@googlegroups.com.

To post to this group, send email to sage-devel@googlegroups.com.

Visit this group at https://groups.google.com/group/sage-devel.

For more options, visit https://groups.google.com/d/optout.

### [sage-devel] memory leak with SR equality test

See the report at

http://ask.sagemath.org/question/32920/memory-saturation-when-i-test-equalities-in-symbolic-ring/

-- http://ask.sagemath.org/question/32920/memory-saturation-when-i-test-equalities-in-symbolic-ring/

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+unsubscribe@googlegroups.com.

To post to this group, send email to sage-devel@googlegroups.com.

Visit this group at https://groups.google.com/group/sage-devel.

For more options, visit https://groups.google.com/d/optout.

### [sage-devel] More cryptography-related functionality for mq.SBox : #20336 (needs review)

It is an implementation for some functionality to determine various cryptographic properties of an S-Box such as nonlinearity, differential uniformity, linear structures, etc.

-- Best Regards,

--

Rusydi H. Makarim

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+unsubscribe@googlegroups.com.

To post to this group, send email to sage-devel@googlegroups.com.

Visit this group at https://groups.google.com/group/sage-devel.

For more options, visit https://groups.google.com/d/optout.

### Re: [sage-devel] Re: Sage 7.1 Windows 8.1 Cygwin make error

On Tue, Mar 29, 2016 at 8:41 PM, Dima Pasechnik <dimpase@gmail.com> wrote:

>

>

> On Tuesday, March 29, 2016 at 6:49:27 PM UTC+1, Witold Żarowski wrote:

>>

>> Thanks. I could theoretically do it, if I only knew

>> 1) where to get the Cygwin package for mpfr from and

>

>

> probably you need this 2-line patch:

> https://github.com/Alexpux/MSYS2-packages/blob/master/mpfr/mpfr-3.1.4-1.src.patch

> (this is perhaps not quite the same as the "proper" cygwin patch - MSYS2 is

> a fork of Cygwin,

> which is sort of more developer-friendly --- perhaps we should consider

> switching to it)

I'm working on that ;)

--

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+unsubscribe@googlegroups.com.

To post to this group, send email to sage-devel@googlegroups.com.

Visit this group at https://groups.google.com/group/sage-devel.

For more options, visit https://groups.google.com/d/optout.

>

>

> On Tuesday, March 29, 2016 at 6:49:27 PM UTC+1, Witold Żarowski wrote:

>>

>> Thanks. I could theoretically do it, if I only knew

>> 1) where to get the Cygwin package for mpfr from and

>

>

> probably you need this 2-line patch:

> https://github.com/Alexpux/MSYS2-packages/blob/master/mpfr/mpfr-3.1.4-1.src.patch

> (this is perhaps not quite the same as the "proper" cygwin patch - MSYS2 is

> a fork of Cygwin,

> which is sort of more developer-friendly --- perhaps we should consider

> switching to it)

I'm working on that ;)

--

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+unsubscribe@googlegroups.com.

To post to this group, send email to sage-devel@googlegroups.com.

Visit this group at https://groups.google.com/group/sage-devel.

For more options, visit https://groups.google.com/d/optout.

### [sage-devel] Re: online documentation and "long time"

As far as I know there is only a switch to "all" plots. ¿Should we append the "long time" comment to the sphinx_plot command, in case somebody decides to implement such a swithc later?

El martes, 22 de marzo de 2016, 11:24:26 (UTC+1), Dima Pasechnik escribió:

-- El martes, 22 de marzo de 2016, 11:24:26 (UTC+1), Dima Pasechnik escribió:

On Tuesday, March 22, 2016 at 9:53:42 AM UTC, Eric Gourgoulhon wrote:

Le mardi 22 mars 2016 10:38:43 UTC+1, Harald Schilly a écrit :

On Tuesday, March 22, 2016 at 9:49:29 AM UTC+1, Samuel Lelievre wrote:

Shouldn't the "long time" stuff appear anyway in the online documentation?Well, do you have any idea how to do that?It's easy: the Sphinx plot directive is independent from the doctest one. One has simply to repeat the plot instructions.

In the above case (assuming we maintain the long time marker), this would be:

sage: g1 = plot(sin(x), 0, 2*pi)

sage: g2 = plot(cos(x), 0, 2*pi, linestyle = "--")

sage: (g1+g2).show(ticks=pi/6, tick_formatter=pi) # long time

.. PLOT::

g1 = plot(sin(x), 0, 2*pi, ticks=pi/6, tick_formatter=pi)

g2 = plot(cos(x), 0, 2*pi, linestyle = "--", ticks=pi/6, tick_formatter=pi)

sphinx_plot(g1+g2)well, I suppose one wants to have all # long time docs in your manual, plot or no plot. Is there an switch to do this?

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+unsubscribe@googlegroups.com.

To post to this group, send email to sage-devel@googlegroups.com.

Visit this group at https://groups.google.com/group/sage-devel.

For more options, visit https://groups.google.com/d/optout.

### [sage-devel] Re: online documentation and "long time"

I remember that a few of the plots just didn't work (and I didn't find a work around) so I dropped them . I will look into it and my notes and get back with either a trac ticket or more information on this.

El martes, 22 de marzo de 2016, 10:53:42 (UTC+1), Eric Gourgoulhon escribió:

-- El martes, 22 de marzo de 2016, 10:53:42 (UTC+1), Eric Gourgoulhon escribió:

Le mardi 22 mars 2016 10:38:43 UTC+1, Harald Schilly a écrit :

On Tuesday, March 22, 2016 at 9:49:29 AM UTC+1, Samuel Lelievre wrote:

Shouldn't the "long time" stuff appear anyway in the online documentation?Well, do you have any idea how to do that?It's easy: the Sphinx plot directive is independent from the doctest one. One has simply to repeat the plot instructions.

In the above case (assuming we maintain the long time marker), this would be:

sage: g1 = plot(sin(x), 0, 2*pi)

sage: g2 = plot(cos(x), 0, 2*pi, linestyle = "--")

sage: (g1+g2).show(ticks=pi/6, tick_formatter=pi) # long time

.. PLOT::

g1 = plot(sin(x), 0, 2*pi, ticks=pi/6, tick_formatter=pi)

g2 = plot(cos(x), 0, 2*pi, linestyle = "--", ticks=pi/6, tick_formatter=pi)

sphinx_plot(g1+g2)

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+unsubscribe@googlegroups.com.

To post to this group, send email to sage-devel@googlegroups.com.

Visit this group at https://groups.google.com/group/sage-devel.

For more options, visit https://groups.google.com/d/optout.

### Re: [sage-devel] Re: Linux on Windows

Maybe it is time for another Sage Days at Microsoft... (we had one

there a few years ago).

On Thu, Mar 31, 2016 at 1:02 AM, Volker Braun <vbraun.name@gmail.com> wrote:

> On Thursday, March 31, 2016 at 9:23:56 AM UTC+2, bluescarni wrote:

>>

>> On the theme of hell freezing over, this also happened:

>>

>> https://blogs.msdn.microsoft.com/vcblog/2016/03/30/visual-c-for-linux-development/

>

>

> Though that is less surprising since they released Linux remote debugging

> (gdb over ssh) support last year...

>

> --

> 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+unsubscribe@googlegroups.com.

> To post to this group, send email to sage-devel@googlegroups.com.

> Visit this group at https://groups.google.com/group/sage-devel.

> For more options, visit https://groups.google.com/d/optout.

--

William (http://wstein.org)

--

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+unsubscribe@googlegroups.com.

To post to this group, send email to sage-devel@googlegroups.com.

Visit this group at https://groups.google.com/group/sage-devel.

For more options, visit https://groups.google.com/d/optout.

there a few years ago).

On Thu, Mar 31, 2016 at 1:02 AM, Volker Braun <vbraun.name@gmail.com> wrote:

> On Thursday, March 31, 2016 at 9:23:56 AM UTC+2, bluescarni wrote:

>>

>> On the theme of hell freezing over, this also happened:

>>

>> https://blogs.msdn.microsoft.com/vcblog/2016/03/30/visual-c-for-linux-development/

>

>

> Though that is less surprising since they released Linux remote debugging

> (gdb over ssh) support last year...

>

> --

> 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+unsubscribe@googlegroups.com.

> To post to this group, send email to sage-devel@googlegroups.com.

> Visit this group at https://groups.google.com/group/sage-devel.

> For more options, visit https://groups.google.com/d/optout.

--

William (http://wstein.org)

--

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+unsubscribe@googlegroups.com.

To post to this group, send email to sage-devel@googlegroups.com.

Visit this group at https://groups.google.com/group/sage-devel.

For more options, visit https://groups.google.com/d/optout.

### [sage-devel] fplll upgrade review

Hi there,

anybody up for reviewing

http://trac.sagemath.org/ticket/20291

which upgrades fplll to the current upstream master. This enables to

install fpylll[1] in Sage, which is a much nicer Python interface for

lattice-reduction than what Sage currently has (optional package in preparation.)

Cheers,

Martin

Footnotes:

[1] https://github.com/malb/fpylll

--

_pgp: https://keybase.io/martinralbrecht

_www: https://martinralbrecht.wordpress.com

_jab: martinralbrecht@jabber.ccc.de

_otr: 47F43D1A 5D68C36F 468BAEBA 640E8856 D7951CCF

--

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+unsubscribe@googlegroups.com.

To post to this group, send email to sage-devel@googlegroups.com.

Visit this group at https://groups.google.com/group/sage-devel.

For more options, visit https://groups.google.com/d/optout.

anybody up for reviewing

http://trac.sagemath.org/ticket/20291

which upgrades fplll to the current upstream master. This enables to

install fpylll[1] in Sage, which is a much nicer Python interface for

lattice-reduction than what Sage currently has (optional package in preparation.)

Cheers,

Martin

Footnotes:

[1] https://github.com/malb/fpylll

--

_pgp: https://keybase.io/martinralbrecht

_www: https://martinralbrecht.wordpress.com

_jab: martinralbrecht@jabber.ccc.de

_otr: 47F43D1A 5D68C36F 468BAEBA 640E8856 D7951CCF

--

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+unsubscribe@googlegroups.com.

To post to this group, send email to sage-devel@googlegroups.com.

Visit this group at https://groups.google.com/group/sage-devel.

For more options, visit https://groups.google.com/d/optout.

### Re: [sage-devel] Re: Linux on Windows

On Thursday, March 31, 2016 at 9:23:56 AM UTC+2, bluescarni wrote:

-- On the theme of hell freezing over, this also happened:

https://blogs.msdn.microsoft.com/vcblog/2016/03/30/visual- c-for-linux-development/

Though that is less surprising since they released Linux remote debugging (gdb over ssh) support last year...

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+unsubscribe@googlegroups.com.

To post to this group, send email to sage-devel@googlegroups.com.

Visit this group at https://groups.google.com/group/sage-devel.

For more options, visit https://groups.google.com/d/optout.

### Re: [sage-devel] Docbuild: Unable to fetch knots/environment.pickle

On 2016-03-31 08:13, Jori Mäntysalo wrote:

> [reference] WARNING: Unable to fetch

> /home/jm58660/sage/local/share/doc/sage/doctrees/en/reference/knots/environment.pickle

This is http://trac.sagemath.org/ticket/20321

--

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+unsubscribe@googlegroups.com.

To post to this group, send email to sage-devel@googlegroups.com.

Visit this group at https://groups.google.com/group/sage-devel.

For more options, visit https://groups.google.com/d/optout.

> [reference] WARNING: Unable to fetch

> /home/jm58660/sage/local/share/doc/sage/doctrees/en/reference/knots/environment.pickle

This is http://trac.sagemath.org/ticket/20321

--

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+unsubscribe@googlegroups.com.

To post to this group, send email to sage-devel@googlegroups.com.

Visit this group at https://groups.google.com/group/sage-devel.

For more options, visit https://groups.google.com/d/optout.

### Re: [sage-devel] Re: Linux on Windows

On the theme of hell freezing over, this also happened:

https://blogs.msdn.microsoft.com/vcblog/2016/03/30/visual-c-for-linux-development/

https://blogs.msdn.microsoft.com/vcblog/2016/03/30/visual-c-for-linux-development/

On 31 March 2016 at 02:17, 'Bill Hart' via sage-devel <sage-devel@googlegroups.com> wrote:

It's almost a year since I predicted Microsoft would do something like this. I have an email from September last year which was a followup email some months after I told a colleague something like this would happen. If I recall our conversation correctly, I was pretty specific about being able to run native Linux apps in a console similar to the usual dos console but without a VM or something like Cygwin. Naturally he thought I was mad.I almost feel like I should make another tech prediction to celebrate. However, I still have a few outstanding. Towards the end of 2014 I predicted 2015-2025 would be a decade of AI breakthroughs. A couple of weeks ago I made two additional predictions. 1) Within 3 years someone will show how to beat world champions at Go on a computer without neural nets or AI, 2) Within 5 years someone will demonstrate meaningful theorem proving using neural networks, say theorems in set theory, group theory and other elementary algebraic topics. Both I will enjoy.Bill.

On Thursday, 31 March 2016 01:52:40 UTC+2, Bill Hart wrote:It looks like this thing is going to be pretty solid [1]. I'm actually incredibly excited about it, more than I have been about Windows for about 20 years.--

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+unsubscribe@googlegroups.com.

To post to this group, send email to sage-devel@googlegroups.com.

Visit this group at https://groups.google.com/group/sage-devel.

For more options, visit https://groups.google.com/d/optout.

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+unsubscribe@googlegroups.com.

To post to this group, send email to sage-devel@googlegroups.com.

Visit this group at https://groups.google.com/group/sage-devel.

For more options, visit https://groups.google.com/d/optout.

## วันพุธที่ 30 มีนาคม พ.ศ. 2559

### [sage-devel] Docbuild: Unable to fetch knots/environment.pickle

I try to work on #19435, which has nothing to do with knot theory. What I

got is

[reference] history_and_license: 0 todos, 1 index, 0 citations, 0 modules

[reference] homology: 1 todos, 19 index, 32 citations, 18 modules

[reference] interfaces: 2 todos, 46 index, 2 citations, 45 modules

[reference] knots:

[reference] WARNING: Unable to fetch

/home/jm58660/sage/local/share/doc/sage/doctrees/en/reference/knots/environment.pickle

Error building the documentation.

Traceback (most recent call last):

File "/home/jm58660/sage/local/lib/python/runpy.py", line 162, in

_run_module_

as_main

. . .

And then it ends. make doc-clean does not help. Full log is at

http://www.sis.uta.fi/~jm58660/dochtml.log

--

Jori Mäntysalo

got is

[reference] history_and_license: 0 todos, 1 index, 0 citations, 0 modules

[reference] homology: 1 todos, 19 index, 32 citations, 18 modules

[reference] interfaces: 2 todos, 46 index, 2 citations, 45 modules

[reference] knots:

[reference] WARNING: Unable to fetch

/home/jm58660/sage/local/share/doc/sage/doctrees/en/reference/knots/environment.pickle

Error building the documentation.

Traceback (most recent call last):

File "/home/jm58660/sage/local/lib/python/runpy.py", line 162, in

_run_module_

as_main

. . .

And then it ends. make doc-clean does not help. Full log is at

http://www.sis.uta.fi/~jm58660/dochtml.log

--

Jori Mäntysalo

### Re: [sage-devel] Installation error: "Error: Source directory doesn't contain a conf.py file." & "Unable to fetch..."

Hello

Executing ./sage runs Sage beautifully :-)

Thank you.

Miguel-Angel Manrique

-- Executing ./sage runs Sage beautifully :-)

Thank you.

Miguel-Angel Manrique

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+unsubscribe@googlegroups.com.

To post to this group, send email to sage-devel@googlegroups.com.

Visit this group at https://groups.google.com/group/sage-devel.

For more options, visit https://groups.google.com/d/optout.

### Re: [sage-devel] Installation error: "Error: Source directory doesn't contain a conf.py file." & "Unable to fetch..."

Hello

Executing ./sage runs Sage beautifully :-)

Thank you.

Miguel-Angel Manrique

On Wednesday, March 30, 2016 at 5:43:12 PM UTC-7, David Roe wrote:

Executing ./sage runs Sage beautifully :-)

Thank you.

Miguel-Angel Manrique

On Wednesday, March 30, 2016 at 5:43:12 PM UTC-7, David Roe wrote:

I'm not sure what's going on with the docbuild, but FYI you should be able to run Sage (documentation is built after Sage is built). What happens when you run /mnt/zeta/sage-7.1/sage?DavidOn Wed, Mar 30, 2016 at 8:20 PM, miguel <snare...@gmail.com> wrote:Hello,

I am trying to compile from source. I am running Kubuntu (Ubuntu 15.10) on kernel 4.2.0-34-generic.

I have attached the dochtml.log file in .../sage-7.1/logs

In awe and thanks,

Miguel-Angel Manrique

----------------------------------------------

Setting permissions of DOT_SAGE directory so only you can read and write it.

Building reference manual, first pass.

[tensor_fr] Error: Source directory doesn't contain a conf.py file.

Build finished. The built documents can be found in /mnt/zeta/sage-7.1/local/share/doc/sage/inventory/en/ reference/tensor_free_modules

[dynamics ] Error: Source directory doesn't contain a conf.py file.

Build finished. The built documents can be found in /mnt/zeta/sage-7.1/local/share/doc/sage/inventory/en/ reference/dynamics

[combinat ] Error: Source directory doesn't contain a conf.py file.

Build finished. The built documents can be found in /mnt/zeta/sage-7.1/local/share/doc/sage/inventory/en/ reference/combinat

[arithgrou] Error: Source directory doesn't contain a conf.py file.

Build finished. The built documents can be found in /mnt/zeta/sage-7.1/local/share/doc/sage/inventory/en/ reference/arithgroup

[polynomia] Error: Source directory doesn't contain a conf.py file.

Build finished. The built documents can be found in /mnt/zeta/sage-7.1/local/share/doc/sage/inventory/en/ reference/polynomial_rings

[homology ] Error: Source directory doesn't contain a conf.py file.

Build finished. The built documents can be found in /mnt/zeta/sage-7.1/local/share/doc/sage/inventory/en/ reference/homology

[manifolds] Error: Source directory doesn't contain a conf.py file.

Build finished. The built documents can be found in /mnt/zeta/sage-7.1/local/share/doc/sage/inventory/en/ reference/manifolds

[graphs ] Error: Source directory doesn't contain a conf.py file.

Build finished. The built documents can be found in /mnt/zeta/sage-7.1/local/share/doc/sage/inventory/en/ reference/graphs

[asymptoti] Error: Source directory doesn't contain a conf.py file.

Build finished. The built documents can be found in /mnt/zeta/sage-7.1/local/share/doc/sage/inventory/en/ reference/asymptotic

[calculus ] Error: Source directory doesn't contain a conf.py file.

Build finished. The built documents can be found in /mnt/zeta/sage-7.1/local/share/doc/sage/inventory/en/ reference/calculus

[categorie] Error: Source directory doesn't contain a conf.py file.

Build finished. The built documents can be found in /mnt/zeta/sage-7.1/local/share/doc/sage/inventory/en/ reference/categories

[misc ] Error: Source directory doesn't contain a conf.py file.

Build finished. The built documents can be found in /mnt/zeta/sage-7.1/local/share/doc/sage/inventory/en/ reference/misc

[algebras ] Error: Source directory doesn't contain a conf.py file.

Build finished. The built documents can be found in /mnt/zeta/sage-7.1/local/share/doc/sage/inventory/en/ reference/algebras

[coercion ] Error: Source directory doesn't contain a conf.py file.

Build finished. The built documents can be found in /mnt/zeta/sage-7.1/local/share/doc/sage/inventory/en/ reference/coercion

[constants] Error: Source directory doesn't contain a conf.py file.

Build finished. The built documents can be found in /mnt/zeta/sage-7.1/local/share/doc/sage/inventory/en/ reference/constants

[cryptogra] Error: Source directory doesn't contain a conf.py file.

Build finished. The built documents can be found in /mnt/zeta/sage-7.1/local/share/doc/sage/inventory/en/ reference/cryptography

[data_stru] Error: Source directory doesn't contain a conf.py file.

Build finished. The built documents can be found in /mnt/zeta/sage-7.1/local/share/doc/sage/inventory/en/ reference/data_structures

[databases] Error: Source directory doesn't contain a conf.py file.

Build finished. The built documents can be found in /mnt/zeta/sage-7.1/local/share/doc/sage/inventory/en/ reference/databases

[coding ] Error: Source directory doesn't contain a conf.py file.

Build finished. The built documents can be found in /mnt/zeta/sage-7.1/local/share/doc/sage/inventory/en/ reference/coding

[diophanti] Error: Source directory doesn't contain a conf.py file.

Build finished. The built documents can be found in /mnt/zeta/sage-7.1/local/share/doc/sage/inventory/en/ reference/diophantine_ approximation

[doctest ] Error: Source directory doesn't contain a conf.py file.

Build finished. The built documents can be found in /mnt/zeta/sage-7.1/local/share/doc/sage/inventory/en/ reference/doctest

[finance ] Error: Source directory doesn't contain a conf.py file.

Build finished. The built documents can be found in /mnt/zeta/sage-7.1/local/share/doc/sage/inventory/en/ reference/finance

[repl ] Error: Source directory doesn't contain a conf.py file.

Build finished. The built documents can be found in /mnt/zeta/sage-7.1/local/share/doc/sage/inventory/en/ reference/repl

[finite_ri] Error: Source directory doesn't contain a conf.py file.

Build finished. The built documents can be found in /mnt/zeta/sage-7.1/local/share/doc/sage/inventory/en/ reference/finite_rings

[function_] Error: Source directory doesn't contain a conf.py file.

Build finished. The built documents can be found in /mnt/zeta/sage-7.1/local/share/doc/sage/inventory/en/ reference/function_fields

[functions] Error: Source directory doesn't contain a conf.py file.

Build finished. The built documents can be found in /mnt/zeta/sage-7.1/local/share/doc/sage/inventory/en/ reference/functions

[game_theo] Error: Source directory doesn't contain a conf.py file.

Build finished. The built documents can be found in /mnt/zeta/sage-7.1/local/share/doc/sage/inventory/en/ reference/game_theory

[games ] Error: Source directory doesn't contain a conf.py file.

Build finished. The built documents can be found in /mnt/zeta/sage-7.1/local/share/doc/sage/inventory/en/ reference/games

[geometry ] Error: Source directory doesn't contain a conf.py file.

Build finished. The built documents can be found in /mnt/zeta/sage-7.1/local/share/doc/sage/inventory/en/ reference/geometry

[hecke ] Error: Source directory doesn't contain a conf.py file.

Build finished. The built documents can be found in /mnt/zeta/sage-7.1/local/share/doc/sage/inventory/en/ reference/hecke

[history_a] Error: Source directory doesn't contain a conf.py file.

Build finished. The built documents can be found in /mnt/zeta/sage-7.1/local/share/doc/sage/inventory/en/ reference/history_and_license

[lfunction] Error: Source directory doesn't contain a conf.py file.

Build finished. The built documents can be found in /mnt/zeta/sage-7.1/local/share/doc/sage/inventory/en/ reference/lfunctions

[logic ] Error: Source directory doesn't contain a conf.py file.

Build finished. The built documents can be found in /mnt/zeta/sage-7.1/local/share/doc/sage/inventory/en/ reference/logic

[matrices ] Error: Source directory doesn't contain a conf.py file.

Build finished. The built documents can be found in /mnt/zeta/sage-7.1/local/share/doc/sage/inventory/en/ reference/matrices

[interface] Error: Source directory doesn't contain a conf.py file.

Build finished. The built documents can be found in /mnt/zeta/sage-7.1/local/share/doc/sage/inventory/en/ reference/interfaces

[matroids ] Error: Source directory doesn't contain a conf.py file.

Build finished. The built documents can be found in /mnt/zeta/sage-7.1/local/share/doc/sage/inventory/en/ reference/matroids

[modabvar ] Error: Source directory doesn't contain a conf.py file.

Build finished. The built documents can be found in /mnt/zeta/sage-7.1/local/share/doc/sage/inventory/en/ reference/modabvar

[modfrm ] Error: Source directory doesn't contain a conf.py file.

Build finished. The built documents can be found in /mnt/zeta/sage-7.1/local/share/doc/sage/inventory/en/ reference/modfrm

[modfrm_he] Error: Source directory doesn't contain a conf.py file.

Build finished. The built documents can be found in /mnt/zeta/sage-7.1/local/share/doc/sage/inventory/en/ reference/modfrm_hecketriangle

[modmisc ] Error: Source directory doesn't contain a conf.py file.

Build finished. The built documents can be found in /mnt/zeta/sage-7.1/local/share/doc/sage/inventory/en/ reference/modmisc

[modsym ] Error: Source directory doesn't contain a conf.py file.

Build finished. The built documents can be found in /mnt/zeta/sage-7.1/local/share/doc/sage/inventory/en/ reference/modsym

[monoids ] Error: Source directory doesn't contain a conf.py file.

Build finished. The built documents can be found in /mnt/zeta/sage-7.1/local/share/doc/sage/inventory/en/ reference/monoids

[modules ] Error: Source directory doesn't contain a conf.py file.

Build finished. The built documents can be found in /mnt/zeta/sage-7.1/local/share/doc/sage/inventory/en/ reference/modules

[number_fi] Error: Source directory doesn't contain a conf.py file.

Build finished. The built documents can be found in /mnt/zeta/sage-7.1/local/share/doc/sage/inventory/en/ reference/number_fields

[numerical] Error: Source directory doesn't contain a conf.py file.

Build finished. The built documents can be found in /mnt/zeta/sage-7.1/local/share/doc/sage/inventory/en/ reference/numerical

[padics ] Error: Source directory doesn't contain a conf.py file.

Build finished. The built documents can be found in /mnt/zeta/sage-7.1/local/share/doc/sage/inventory/en/ reference/padics

[notebook ] Error: Source directory doesn't contain a conf.py file.

Build finished. The built documents can be found in /mnt/zeta/sage-7.1/local/share/doc/sage/inventory/en/ reference/notebook

[parallel ] Error: Source directory doesn't contain a conf.py file.

Build finished. The built documents can be found in /mnt/zeta/sage-7.1/local/share/doc/sage/inventory/en/ reference/parallel

[plot3d ] Error: Source directory doesn't contain a conf.py file.

Build finished. The built documents can be found in /mnt/zeta/sage-7.1/local/share/doc/sage/inventory/en/ reference/plot3d

[plane_cur] Error: Source directory doesn't contain a conf.py file.

Build finished. The built documents can be found in /mnt/zeta/sage-7.1/local/share/doc/sage/inventory/en/ reference/plane_curves

[plotting ] Error: Source directory doesn't contain a conf.py file.

Build finished. The built documents can be found in /mnt/zeta/sage-7.1/local/share/doc/sage/inventory/en/ reference/plotting

[power_ser] Error: Source directory doesn't contain a conf.py file.

Build finished. The built documents can be found in /mnt/zeta/sage-7.1/local/share/doc/sage/inventory/en/ reference/power_series

[probabili] Error: Source directory doesn't contain a conf.py file.

Build finished. The built documents can be found in /mnt/zeta/sage-7.1/local/share/doc/sage/inventory/en/ reference/probability

[quat_alge] Error: Source directory doesn't contain a conf.py file.

Build finished. The built documents can be found in /mnt/zeta/sage-7.1/local/share/doc/sage/inventory/en/ reference/quat_algebras

[quadratic] Error: Source directory doesn't contain a conf.py file.

Build finished. The built documents can be found in /mnt/zeta/sage-7.1/local/share/doc/sage/inventory/en/ reference/quadratic_forms

[riemannia] Error: Source directory doesn't contain a conf.py file.

Build finished. The built documents can be found in /mnt/zeta/sage-7.1/local/share/doc/sage/inventory/en/ reference/riemannian_geometry

[quivers ] Error: Source directory doesn't contain a conf.py file.

Build finished. The built documents can be found in /mnt/zeta/sage-7.1/local/share/doc/sage/inventory/en/ reference/quivers

/mnt/zeta/sage-7.1/local/lib/python2.7/site-packages/sage_ setup/docbuild/__init__.py: 921: DeprecationWarning: the module sage.rings.commutative_ring is deprecated and will be removed

See http://trac.sagemath.org/20011 for details.

__import__(module_name)

/mnt/zeta/sage-7.1/local/lib/python2.7/site-packages/sage_ setup/docbuild/__init__.py: 921: DeprecationWarning: the module sage.rings.dedekind_domain is deprecated and will be removed

See http://trac.sagemath.org/20011 for details.

__import__(module_name)

/mnt/zeta/sage-7.1/local/lib/python2.7/site-packages/sage_ setup/docbuild/__init__.py: 921: DeprecationWarning: the module sage.rings.euclidean_domain is deprecated and will be removed

See http://trac.sagemath.org/20011 for details.

__import__(module_name)

/mnt/zeta/sage-7.1/local/lib/python2.7/site-packages/sage_ setup/docbuild/__init__.py: 921: DeprecationWarning: the module sage.rings.integral_domain is deprecated and will be removed

See http://trac.sagemath.org/20011 for details.

__import__(module_name)

/mnt/zeta/sage-7.1/local/lib/python2.7/site-packages/sage_ setup/docbuild/__init__.py: 921: DeprecationWarning: the module sage.rings.principal_ideal_ domain is deprecated and will be removed

See http://trac.sagemath.org/20011 for details.

__import__(module_name)

[rings_num] Error: Source directory doesn't contain a conf.py file.

Build finished. The built documents can be found in /mnt/zeta/sage-7.1/local/share/doc/sage/inventory/en/ reference/rings_numerical

[rings ] Error: Source directory doesn't contain a conf.py file.

Build finished. The built documents can be found in /mnt/zeta/sage-7.1/local/share/doc/sage/inventory/en/ reference/rings

[rings_sta] Error: Source directory doesn't contain a conf.py file.

Build finished. The built documents can be found in /mnt/zeta/sage-7.1/local/share/doc/sage/inventory/en/ reference/rings_standard

[sat ] Error: Source directory doesn't contain a conf.py file.

Build finished. The built documents can be found in /mnt/zeta/sage-7.1/local/share/doc/sage/inventory/en/ reference/sat

[schemes ] Error: Source directory doesn't contain a conf.py file.

Build finished. The built documents can be found in /mnt/zeta/sage-7.1/local/share/doc/sage/inventory/en/ reference/schemes

[semirings] Error: Source directory doesn't contain a conf.py file.

Build finished. The built documents can be found in /mnt/zeta/sage-7.1/local/share/doc/sage/inventory/en/ reference/semirings

[stats ] Error: Source directory doesn't contain a conf.py file.

Build finished. The built documents can be found in /mnt/zeta/sage-7.1/local/share/doc/sage/inventory/en/ reference/stats

[tensor ] Error: Source directory doesn't contain a conf.py file.

Build finished. The built documents can be found in /mnt/zeta/sage-7.1/local/share/doc/sage/inventory/en/ reference/tensor

[structure] Error: Source directory doesn't contain a conf.py file.

Build finished. The built documents can be found in /mnt/zeta/sage-7.1/local/share/doc/sage/inventory/en/ reference/structure

Warning: Missing title for sage.groups.perm_gps.partn_ref

Warning: Missing title for sage.groups.perm_gps.partn_ref2

[groups ] Error: Source directory doesn't contain a conf.py file.

Build finished. The built documents can be found in /mnt/zeta/sage-7.1/local/share/doc/sage/inventory/en/ reference/groups

[libs ] Error: Source directory doesn't contain a conf.py file.

Build finished. The built documents can be found in /mnt/zeta/sage-7.1/local/share/doc/sage/inventory/en/ reference/libs

[reference] /mnt/zeta/sage-7.1/local/lib/python2.7/site-packages/ matplotlib-1.5.1-py2.7-linux- x86_64.egg/matplotlib/font_ manager.py:273: UserWarning: Matplotlib is building the font cache using fc-list. This may take a moment.

[reference] warnings.warn('Matplotlib is building the font cache using fc-list. This may take a moment.')

[reference] loading pickled environment... not yet created

[reference] Compiling the master document

[reference] building [inventory]: targets for 1 source files that are out of date

[reference] updating environment: 1 added, 0 changed, 0 removed

[reference] reading sources... [100%] index

[reference] Merging environment/index files...

[reference] algebras:

[reference] WARNING: Unable to fetch /mnt/zeta/sage-7.1/local/share/doc/sage/doctrees/en/ reference/algebras/ environment.pickle

[reference] WARNING: Unable to fetch /mnt/zeta/sage-7.1/local/share/doc/sage/doctrees/en/ reference/arithgroup/ environment.pickle

[reference] WARNING: Unable to fetch /mnt/zeta/sage-7.1/local/share/doc/sage/doctrees/en/ reference/asymptotic/ environment.pickle

[reference] WARNING: Unable to fetch /mnt/zeta/sage-7.1/local/share/doc/sage/doctrees/en/ reference/calculus/ environment.pickle

[reference] WARNING: Unable to fetch /mnt/zeta/sage-7.1/local/share/doc/sage/doctrees/en/ reference/categories/ environment.pickle

[reference] WARNING: Unable to fetch /mnt/zeta/sage-7.1/local/share/doc/sage/doctrees/en/ reference/coding/environment. pickle

[reference] WARNING: Unable to fetch /mnt/zeta/sage-7.1/local/share/doc/sage/doctrees/en/ reference/coercion/ environment.pickle

[reference] WARNING: Unable to fetch /mnt/zeta/sage-7.1/local/share/doc/sage/doctrees/en/ reference/combinat/ environment.pickle

[reference] WARNING: Unable to fetch /mnt/zeta/sage-7.1/local/share/doc/sage/doctrees/en/ reference/constants/ environment.pickle

[reference] WARNING: Unable to fetch /mnt/zeta/sage-7.1/local/share/doc/sage/doctrees/en/ reference/cryptography/ environment.pickle

[reference] WARNING: Unable to fetch /mnt/zeta/sage-7.1/local/share/doc/sage/doctrees/en/ reference/data_structures/ environment.pickle

[reference] WARNING: Unable to fetch /mnt/zeta/sage-7.1/local/share/doc/sage/doctrees/en/ reference/databases/ environment.pickle

[reference] WARNING: Unable to fetch /mnt/zeta/sage-7.1/local/share/doc/sage/doctrees/en/ reference/diophantine_ approximation/environment. pickle

[reference] WARNING: Unable to fetch /mnt/zeta/sage-7.1/local/share/doc/sage/doctrees/en/ reference/doctest/environment. pickle

[reference] WARNING: Unable to fetch /mnt/zeta/sage-7.1/local/share/doc/sage/doctrees/en/ reference/dynamics/ environment.pickle

[reference] WARNING: Unable to fetch /mnt/zeta/sage-7.1/local/share/doc/sage/doctrees/en/ reference/finance/environment. pickle

[reference] WARNING: Unable to fetch /mnt/zeta/sage-7.1/local/share/doc/sage/doctrees/en/ reference/finite_rings/ environment.pickle

[reference] WARNING: Unable to fetch /mnt/zeta/sage-7.1/local/share/doc/sage/doctrees/en/ reference/function_fields/ environment.pickle

[reference] WARNING: Unable to fetch /mnt/zeta/sage-7.1/local/share/doc/sage/doctrees/en/ reference/functions/ environment.pickle

[reference] WARNING: Unable to fetch /mnt/zeta/sage-7.1/local/share/doc/sage/doctrees/en/ reference/game_theory/ environment.pickle

[reference] WARNING: Unable to fetch /mnt/zeta/sage-7.1/local/share/doc/sage/doctrees/en/ reference/games/environment. pickle

[reference] WARNING: Unable to fetch /mnt/zeta/sage-7.1/local/share/doc/sage/doctrees/en/ reference/geometry/ environment.pickle

[reference] WARNING: Unable to fetch /mnt/zeta/sage-7.1/local/share/doc/sage/doctrees/en/ reference/graphs/environment. pickle

[reference] WARNING: Unable to fetch /mnt/zeta/sage-7.1/local/share/doc/sage/doctrees/en/ reference/groups/environment. pickle

[reference] WARNING: Unable to fetch /mnt/zeta/sage-7.1/local/share/doc/sage/doctrees/en/ reference/hecke/environment. pickle

[reference] WARNING: Unable to fetch /mnt/zeta/sage-7.1/local/share/doc/sage/doctrees/en/ reference/history_and_license/