[sage-devel] Re: maxima_calculus.load("blah.mac") throws, load("blah.mac'") in sage --maxima works

[Robert Dodier]

On 2017-01-12, Dima Pasechnik  wrote:

> maxima_calculus.load("blah.mac") throws a TypeError:
> ECL says: THROW: The catch MACSYMA-QUIT is undefined.

Well, there is more than one way to process an input file in Maxima, and
in one of those ways, the function reading the file throws MACSYMA-QUIT
and the caller is supposed to catch that to know the end of file was
reached. So it sounds as if the file was opened and the content was read
but the end of file wasn't handled correctly. Is there a way to see if
anything was actually processed? e.g. maybe look at values or function
definitions or print output.

> maxima.load("blah.mac") just hangs indefinitely.

A wild guess. Is it possible that it didn't switch back to reading from
the console after the file was processed? Completely guessing here.

best,

Robert Dodier

-- 
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 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-combinat-devel] combinat.sagemath.org

[William Stein]

On Thu, Jan 12, 2017 at 7:38 PM, Matthew Rennekamp
 wrote:
> I'm working on the www.sagemath.org & SageWiki. What happened to
> combinat.sagemath.org? Are there other places those files are stored?

The machine exists, and I have a backup copy of all files.  As with
sage.math.washington.edu, let me know if you're interested in going
through and collating and cleaning things up, and I can get you
access...

William

>
> --
> You received this message because you are subscribed to the Google Groups
> "sage-combinat-devel" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to sage-combinat-devel+unsubscr...@googlegroups.com.
> To post to this group, send email to sage-combinat-devel@googlegroups.com.
> Visit this group at https://groups.google.com/group/sage-combinat-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-combinat-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-combinat-devel+unsubscr...@googlegroups.com.
To post to this group, send email to sage-combinat-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-combinat-devel.
For more options, visit https://groups.google.com/d/optout.

[sage-combinat-devel] combinat.sagemath.org

[Matthew Rennekamp]

I'm working on the www.sagemath.org & SageWiki. What happened to 
combinat.sagemath.org? Are there other places those files are stored?

-- 
You received this message because you are subscribed to the Google Groups 
"sage-combinat-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-combinat-devel+unsubscr...@googlegroups.com.
To post to this group, send email to sage-combinat-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-combinat-devel.
For more options, visit https://groups.google.com/d/optout.

[sage-devel] Error when attaching file, NameError: name 'cython' is not defined

[Michael Frey]

I am trying to attach a code file to a sage notebook.  The call is : attach 
("~/.sage/MHF_Bloch_n_Plot.sage").  The error I get is "NameError: name 
'cython' is not defined".  The code in the attach file is:

...

cython("""

#Parallel Cython, Numpy calls -- 3 part3

#Part 1

#Cython version for parallel

import numpy as np

import scipy as sp

from scipy import linalg

cimport numpy as np

cdef extern from "math.h":

float cosf(float theta)

float sinf(float theta)

...

""")

...


Am I missing something or is this a bug?

I am using SageMath version 7.5, Release Date: 2017-01-11 built from source 
in a MacBook Pro with MacOS 10.12.2


Thank you for your help. 

Mike

-- 
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 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: maxima_calculus.load("blah.mac") throws, load("blah.mac'") in sage --maxima works

[Nils Bruin]

This works:

sage: maxima_calculus.load('to_poly_solve')
\"/usr/local/sage/sage-git/local/share/maxima/5.35.1/share/to_poly_solve/to_poly_solve.mac\"

whereas this does not:

sage: maxima_calculus.load('to_poly_solve.mac')
TypeError: ECL says: In function PATHNAME, the value of the only argument is
  ((MNCTIMES SIMP) $TO_POLY_SOLVE $MAC)
which is not of the expected type (OR FILE-STREAM STRING PATHNAME)

(clearly, the filename is parsed rather than taken as a string)

This does seem to work:

sage: maxima_calculus.load('"to_poly_solve.mac"')
\"/usr/local/sage/sage-git/local/share/maxima/5.35.1/share/to_poly_solve/to_poly_solve.mac\"

as does this:

sage: 
maxima_calculus.load('"/usr/local/sage/sage-git/local/share/maxima/5.35.1/share/to_poly_solve/to_poly_solve.mac"')
\"/usr/local/sage/sage-git/local/share/maxima/5.35.1/share/to_poly_solve/to_poly_solve.mac\"

so it looks like there's nothing particularly wrong with the load command 
once you let it deal with strings properly.

If you want to take it a little closer to the metal you can do

sage: maxima_calculus._eval_line('load("to_poly_solve.mac")')
'\\"/usr/local/sage/sage-git/local/share/maxima/5.35.1/share/to_poly_solve/to_poly_solve.mac\\"

which seems to work as well. 

Working with a nonexisting file gives a rather uninformative error message:

sage: maxima_calculus.load('"blah.mac"')
TypeError: ECL says: Error executing code in Maxima:

whereas maxima tells exactly what goes wrong. So the error message 
capturing technology can perhaps be improved.

-- 
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 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: Release note auto-generation RFC

[Kwankyu Lee]

On Thursday, January 12, 2017 at 8:10:54 PM UTC+1, Dima Pasechnik wrote:
>
>
>
> On Thursday, January 12, 2017 at 6:01:55 PM UTC, Volker Braun wrote:
>>
>> The whole point of NEWS would be to have coarser granularity than 
>> individual tickets. E.g. 7.4 -> 7.5 is over 300 tickets, and a 300-item 
>> list is never a good answer to the question "whats new in this release". I 
>> would envision a list of, say, 10-20 highlights to have associated news 
>> fragments.
>>
>
> yes, right, so you'd tag these "interesting for NEWS" tickets on trac, 
> using some kind of trac plugin.
>

I guess Volker's idea is that the author of the ticket decides if his/her 
ticket is worth to be highlighted and provide a well-phrased blurb for 
general users.

>

-- 
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 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] maxima_calculus.load("blah.mac") throws, load("blah.mac'") in sage --maxima works

[Dima Pasechnik]

I am trying to understand how to load Maxima user code into 
maxima_calculus().

Running 
maxima_calculus.load("blah.mac") throws a TypeError:
ECL says: THROW: The catch MACSYMA-QUIT is undefined.

maxima.load("blah.mac") just hangs indefinitely.

Trying the same code in sage --maxima, there
load("blah.mac'"); works 
It does emit quite a few messages from the ECL
lisp compiler though, saying ";;; Compiling...", ";;; Emitting code", etc.

What am I doing wrong?
Do I miss some kind of building step?





-- 
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 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: A triangulate method that produces quadrilaterals. Why ?

[ams]

Hi. Thank you for the explanation.
You can add me to the list of people telling : export to stl is definitely 
good to have! 

A

On Thursday, January 12, 2017 at 7:25:50 PM UTC+1, Frédéric Chapoton wrote:
>
> Hello,
>
> I think this is more subtle than that. The procedure "triangulate" is used 
> in several places, and sometimes it may generate triangles.
> When I wrote the old stl_ascii_string, I was lazy and did not care about 
> faces other than triangles, even if I knew perfectly that they could 
> happen. I have never seen any feedback on somebody using this STL export 
> and saying "that's good to have", so my motivation was low.
> I do not think that the name "triangulate" is good, but there is not much 
> value in changing it. This is a rather deep internal method.
>
> Frederic
>
>
>
> Le jeudi 12 janvier 2017 12:29:13 UTC+1, ams a écrit :
>>
>> While investigating the stl export from 3D plots, (which have been 
>> recently improved, see trac-ticket-22144 
>> ) I found a method in 
>> plot/plot3d/parametric_surface.pyx 
>> 
>>  
>> that is called *triangulate*, but that actually quadrangulates the 
>> underlying self (maybe it also produces triangles, when some quadrilateral 
>> is degenerate, I am not sure).
>>
>> def triangulate(self, render_params=None):
>> r"""
>> […] so normals of the triangles […] 
>> """
>> # […]
>> face.n = 4 # […]
>>
>> The reason I looked into it was that it caused problem for saving to stl 
>> format because the old version of *stl_ascii_string* method assumed that 
>> the output of a method called *triangulate* would always have only 
>> *triangles*. *stl_ascii_string* have been modified in ticket 22144 
>> , but I still thing it's kind of 
>> counterintuitive to have a *triangulate* method that do not produces 
>> triangles but quadrilaterals instead. 
>>
>> Does anybody here knows what were the reasons behind this choice ? And 
>> where is it used ? 
>>
>

-- 
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 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] trouble compiling on debian sid

[Matthias Koeppe]

I haven't looked at the details, but I would guess that singular's polymake 
interface is out of date / untested (our polymake package is up to date). A 
ticket should be created and upstream singular be notified.

Matthias

On Thursday, January 12, 2017 at 11:00:36 AM UTC-8, François wrote:
>
> I now see that was indeed the problem. No easy to solve it sage side 
> without dropping the experimental polymake package or never building the 
> singular interface to it. 
> Considering version problems between singular and polymake, the later 
> would be my inclination.
>
> Francois 
>
> On 13/01/2017, at 7:51 AM, Francois Bissey  > wrote:
>
> Would you happen to have polymake installed system wide?
>
> Francois 
>
> On 13/01/2017, at 12:29 AM, moritz  
> wrote:
>
> When trying to build sage from source on my debian box with a current sid 
> install, I get the following error:
>
> [singular-4.1.0p1] ../../../gfanlib/gfanlib_matrix.h:221:24: warning: 
> comparison between signed and unsigned integer expressions [-Wsign-compare]
> [singular-4.1.0p1] Makefile:573: recipe for target 
> 'polymake_la-polymake_conversion.lo' failed
> [singular-4.1.0p1] make[8]: *** [polymake_la-polymake_conversion.lo] Error 
> 1
>
> In the log file, I get a couple of the following errors:
> polymake_conversion.cc:176:56: error: cannot convert 
> 'pm::array_traits::iterator {aka pm::ptr_wrapper false>}' to 'const pm::Integer*' in initialization
>
> If it helps I will gladly attach the log file.
>
> The version I am trying to build is the current develop branch 7.5.rc3, 
> but I also get an error for the master branch.
>
> Any help would be highly appreciated!
>
>
> -- 
> 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+...@googlegroups.com .
> To post to this group, send email to sage...@googlegroups.com 
> .
> Visit this group at https://groups.google.com/group/sage-devel.
> For more options, visit https://groups.google.com/d/optout.
>
> This email may be confidential and subject to legal privilege, it may
> not reflect the views of the University of Canterbury, and it is not
> guaranteed to be virus free. If you are not an intended recipient,
> please notify the sender immediately and erase all copies of the message
> and any attachments.
>
> Please refer to http://www.canterbury.ac.nz/emaildisclaimer for more
> information.
>
> -- 
> 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+...@googlegroups.com .
> To post to this group, send email to sage...@googlegroups.com 
> .
> Visit this group at https://groups.google.com/group/sage-devel.
> For more options, visit https://groups.google.com/d/optout.
>
> This email may be confidential and subject to legal privilege, it may
> not reflect the views of the University of Canterbury, and it is not
> guaranteed to be virus free. If you are not an intended recipient,
> please notify the sender immediately and erase all copies of the message
> and any attachments.
>
> Please refer to http://www.canterbury.ac.nz/emaildisclaimer for more
> information.
>
>

-- 
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 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: Release note auto-generation RFC

[Dima Pasechnik]

On Thursday, January 12, 2017 at 6:01:55 PM UTC, Volker Braun wrote:
>
> The whole point of NEWS would be to have coarser granularity than 
> individual tickets. E.g. 7.4 -> 7.5 is over 300 tickets, and a 300-item 
> list is never a good answer to the question "whats new in this release". I 
> would envision a list of, say, 10-20 highlights to have associated news 
> fragments.
>

yes, right, so you'd tag these "interesting for NEWS" tickets on trac, 
using some kind of trac plugin.
 

>
>
>
>
> On Thursday, January 12, 2017 at 5:14:23 PM UTC+1, Dima Pasechnik wrote:
>>
>> Wouldn't it be better to relate news to closed/merged trac tickets?
>> This might need an extra trac feature allowing for tagging tickets for 
>> priority in the sense
>> of how much value a ticket adds.
>> (critical/blocker/major hierarchy is something different)
>>
>> Then NEWS would come from harvesting ticket's summaries and arranging 
>> them 
>> w.r.t.  the value-adding priority.
>> This would be indeed almost painless, as opposed to extra files somewhere 
>> etc etc.
>> (This might even fit within some of ODK deliverables :-))
>>
>> Dima
>>
>>
>>
>> On Wednesday, January 11, 2017 at 11:09:53 PM UTC, Volker Braun wrote:
>>>
>>> There is a somewhat painless approach to generating human-readable 
>>> release notes using https://github.com/hawkowl/towncrier. As far as the 
>>> ticket author is concerned, if you think that your ticket #12435 is of 
>>> wider interest and should be announced then all you'd have to do is add a 
>>> file
>>>
>>> echo "Added the last twin prime" > newsfragments/12435.feature
>>>
>>> Note that the fragment filename starts with the ticket number, so it 
>>> won't conflict with other news fragments. Then, when making a new release, 
>>> I concatenate the fragments into NEWS.rst as, for example, in 
>>> https://github.com/hawkowl/towncrier/blob/master/NEWS.rst
>>>
>>

-- 
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 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: Release note auto-generation RFC

[Matthias Koeppe]

One could perhaps use metatickets on trac for that.

On Thursday, January 12, 2017 at 10:01:55 AM UTC-8, Volker Braun wrote:
>
> The whole point of NEWS would be to have coarser granularity than 
> individual tickets. E.g. 7.4 -> 7.5 is over 300 tickets, and a 300-item 
> list is never a good answer to the question "whats new in this release". I 
> would envision a list of, say, 10-20 highlights to have associated news 
> fragments.
>
>>

-- 
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 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] trouble compiling on debian sid

[Francois Bissey]

I now see that was indeed the problem. No easy to solve it sage side without 
dropping the experimental polymake package or never building the singular 
interface to it.
Considering version problems between singular and polymake, the later would be 
my inclination.

Francois

On 13/01/2017, at 7:51 AM, Francois Bissey 
> 
wrote:

Would you happen to have polymake installed system wide?

Francois

On 13/01/2017, at 12:29 AM, moritz 
> wrote:

When trying to build sage from source on my debian box with a current sid 
install, I get the following error:

[singular-4.1.0p1] ../../../gfanlib/gfanlib_matrix.h:221:24: warning: 
comparison between signed and unsigned integer expressions [-Wsign-compare]
[singular-4.1.0p1] Makefile:573: recipe for target 
'polymake_la-polymake_conversion.lo' failed
[singular-4.1.0p1] make[8]: *** [polymake_la-polymake_conversion.lo] Error 1

In the log file, I get a couple of the following errors:
polymake_conversion.cc:176:56: error: cannot convert 
'pm::array_traits::iterator {aka pm::ptr_wrapper}' to 'const pm::Integer*' in initialization

If it helps I will gladly attach the log file.

The version I am trying to build is the current develop branch 7.5.rc3, but I 
also get an error for the master branch.

Any help would be highly appreciated!



--
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 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.

This email may be confidential and subject to legal privilege, it may
not reflect the views of the University of Canterbury, and it is not
guaranteed to be virus free. If you are not an intended recipient,
please notify the sender immediately and erase all copies of the message
and any attachments.

Please refer to http://www.canterbury.ac.nz/emaildisclaimer for more
information.


--
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 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.

This email may be confidential and subject to legal privilege, it may
not reflect the views of the University of Canterbury, and it is not
guaranteed to be virus free. If you are not an intended recipient,
please notify the sender immediately and erase all copies of the message
and any attachments.

Please refer to http://www.canterbury.ac.nz/emaildisclaimer for more
information.

-- 
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 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] trouble compiling on debian sid

[Francois Bissey]

Would you happen to have polymake installed system wide?

Francois

On 13/01/2017, at 12:29 AM, moritz 
> wrote:

When trying to build sage from source on my debian box with a current sid 
install, I get the following error:

[singular-4.1.0p1] ../../../gfanlib/gfanlib_matrix.h:221:24: warning: 
comparison between signed and unsigned integer expressions [-Wsign-compare]
[singular-4.1.0p1] Makefile:573: recipe for target 
'polymake_la-polymake_conversion.lo' failed
[singular-4.1.0p1] make[8]: *** [polymake_la-polymake_conversion.lo] Error 1

In the log file, I get a couple of the following errors:
polymake_conversion.cc:176:56: error: cannot convert 
'pm::array_traits::iterator {aka pm::ptr_wrapper}' to 'const pm::Integer*' in initialization

If it helps I will gladly attach the log file.

The version I am trying to build is the current develop branch 7.5.rc3, but I 
also get an error for the master branch.

Any help would be highly appreciated!



--
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 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.

This email may be confidential and subject to legal privilege, it may
not reflect the views of the University of Canterbury, and it is not
guaranteed to be virus free. If you are not an intended recipient,
please notify the sender immediately and erase all copies of the message
and any attachments.

Please refer to http://www.canterbury.ac.nz/emaildisclaimer for more
information.

-- 
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 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: A triangulate method that produces quadrilaterals. Why ?

[Frédéric Chapoton]

Hello,

I think this is more subtle than that. The procedure "triangulate" is used 
in several places, and sometimes it may generate triangles.
When I wrote the old stl_ascii_string, I was lazy and did not care about 
faces other than triangles, even if I knew perfectly that they could 
happen. I have never seen any feedback on somebody using this STL export 
and saying "that's good to have", so my motivation was low.
I do not think that the name "triangulate" is good, but there is not much 
value in changing it. This is a rather deep internal method.

Frederic



Le jeudi 12 janvier 2017 12:29:13 UTC+1, ams a écrit :
>
> While investigating the stl export from 3D plots, (which have been 
> recently improved, see trac-ticket-22144 
> ) I found a method in 
> plot/plot3d/parametric_surface.pyx 
> 
>  
> that is called *triangulate*, but that actually quadrangulates the 
> underlying self (maybe it also produces triangles, when some quadrilateral 
> is degenerate, I am not sure).
>
> def triangulate(self, render_params=None):
> r"""
> […] so normals of the triangles […] 
> """
> # […]
> face.n = 4 # […]
>
> The reason I looked into it was that it caused problem for saving to stl 
> format because the old version of *stl_ascii_string* method assumed that 
> the output of a method called *triangulate* would always have only 
> *triangles*. *stl_ascii_string* have been modified in ticket 22144 
> , but I still thing it's kind of 
> counterintuitive to have a *triangulate* method that do not produces 
> triangles but quadrilaterals instead. 
>
> Does anybody here knows what were the reasons behind this choice ? And 
> where is it used ? 
>

-- 
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 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: Release note auto-generation RFC

[Volker Braun]

The whole point of NEWS would be to have coarser granularity than 
individual tickets. E.g. 7.4 -> 7.5 is over 300 tickets, and a 300-item 
list is never a good answer to the question "whats new in this release". I 
would envision a list of, say, 10-20 highlights to have associated news 
fragments.




On Thursday, January 12, 2017 at 5:14:23 PM UTC+1, Dima Pasechnik wrote:
>
> Wouldn't it be better to relate news to closed/merged trac tickets?
> This might need an extra trac feature allowing for tagging tickets for 
> priority in the sense
> of how much value a ticket adds.
> (critical/blocker/major hierarchy is something different)
>
> Then NEWS would come from harvesting ticket's summaries and arranging them 
> w.r.t.  the value-adding priority.
> This would be indeed almost painless, as opposed to extra files somewhere 
> etc etc.
> (This might even fit within some of ODK deliverables :-))
>
> Dima
>
>
>
> On Wednesday, January 11, 2017 at 11:09:53 PM UTC, Volker Braun wrote:
>>
>> There is a somewhat painless approach to generating human-readable 
>> release notes using https://github.com/hawkowl/towncrier. As far as the 
>> ticket author is concerned, if you think that your ticket #12435 is of 
>> wider interest and should be announced then all you'd have to do is add a 
>> file
>>
>> echo "Added the last twin prime" > newsfragments/12435.feature
>>
>> Note that the fragment filename starts with the ticket number, so it 
>> won't conflict with other news fragments. Then, when making a new release, 
>> I concatenate the fragments into NEWS.rst as, for example, in 
>> https://github.com/hawkowl/towncrier/blob/master/NEWS.rst
>>
>

-- 
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 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: Release note auto-generation RFC

[Dima Pasechnik]

Wouldn't it be better to relate news to closed/merged trac tickets?
This might need an extra trac feature allowing for tagging tickets for 
priority in the sense
of how much value a ticket adds.
(critical/blocker/major hierarchy is something different)

Then NEWS would come from harvesting ticket's summaries and arranging them 
w.r.t.  the value-adding priority.
This would be indeed almost painless, as opposed to extra files somewhere 
etc etc.
(This might even fit within some of ODK deliverables :-))

Dima



On Wednesday, January 11, 2017 at 11:09:53 PM UTC, Volker Braun wrote:
>
> There is a somewhat painless approach to generating human-readable release 
> notes using https://github.com/hawkowl/towncrier. As far as the ticket 
> author is concerned, if you think that your ticket #12435 is of wider 
> interest and should be announced then all you'd have to do is add a file
>
> echo "Added the last twin prime" > newsfragments/12435.feature
>
> Note that the fragment filename starts with the ticket number, so it won't 
> conflict with other news fragments. Then, when making a new release, I 
> concatenate the fragments into NEWS.rst as, for example, in 
> https://github.com/hawkowl/towncrier/blob/master/NEWS.rst
>

-- 
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 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] Release note auto-generation RFC

[Johan S . H . Rosenkilde]

Volker Braun writes:

> There is a somewhat painless approach to generating human-readable release 
> notes using https://github.com/hawkowl/towncrier. As far as the ticket 
> author is concerned, if you think that your ticket #12435 is of wider 
> interest and should be announced then all you'd have to do is add a file
>
> echo "Added the last twin prime" > newsfragments/12435.feature
>
> Note that the fragment filename starts with the ticket number, so it won't 
> conflict with other news fragments. Then, when making a new release, I 
> concatenate the fragments into NEWS.rst as, for example, 
> in https://github.com/hawkowl/towncrier/blob/master/NEWS.rst

I support the idea of providing users (and developers) with a NEWS file.
My first reaction to your suggestion with towncrier is to ask why it is
necessary to manually add news for a subset of tickets, instead of
auto-generating a NEWS file from all closed tickets.

Many tickets will be bug fixes or technical stuff, not very pleasant or
relevant to a user. But what if the "types" we have on tickets were more
meaningful, perhaps these could serve to divide such a NEWS file into
headings, e.g.

== New Features ==

24454: Added the last twin prime


== Enhancements ==

28042: A faster implementation of Q[x] factorisation
...

== Bug-fixes ==

25233: Fixed a crash when plotting.
...


Best,
Johan

-- 
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 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: Release note auto-generation RFC

[Ralf Stephan]

On Thursday, January 12, 2017 at 1:48:28 PM UTC+1, Simon King wrote:
>
> On 2017-01-12, Volker Braun  wrote: 
> > Yes, to the Sage src tree. That is, we would add a newsfragments 
> directory 
> > somewhere under $SAGE_ROOT. 
>
> Seriously??? 
>

How else would the ticket authors associate a self-written blurb with
the respective branch? It must be committed via git. On release the
RM collects them all and removes the files.

Oh, and editing a NEWS file will produce merge conflicts. That's why
single files.
 

-- 
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 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: Release note auto-generation RFC

[Simon King]

On 2017-01-12, Volker Braun  wrote:
> Yes, to the Sage src tree. That is, we would add a newsfragments directory 
> somewhere under $SAGE_ROOT.

Seriously???

-- 
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 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: trouble compiling singular

[Dima Pasechnik]

Thanks for the report.
Sage has an experimental polymake 
package: https://trac.sagemath.org/ticket/20892

Not sure if we ever checked how well it lives together with Singular --- 
but we should.

On Thursday, January 12, 2017 at 10:53:19 AM UTC, moritz wrote:
>
> I figured out what the problem was: I had a version of polymake installed 
> (3.0.6) and singular checks for a polymake install. However when I removed 
> polymake and polymake-config from /usr/local/bin sage could be build 
> successfully. When configuring singular one could also pass the 
> --disable-polymake flag. 
>
> I hope somebody with a similar problem might find this useful.. 
>
>

-- 
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 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] trouble compiling on debian sid

[moritz]

When trying to build sage from source on my debian box with a current sid 
install, I get the following error:

[singular-4.1.0p1] ../../../gfanlib/gfanlib_matrix.h:221:24: warning: 
comparison between signed and unsigned integer expressions [-Wsign-compare]
[singular-4.1.0p1] Makefile:573: recipe for target 
'polymake_la-polymake_conversion.lo' failed
[singular-4.1.0p1] make[8]: *** [polymake_la-polymake_conversion.lo] Error 1

In the log file, I get a couple of the following errors:
polymake_conversion.cc:176:56: error: cannot convert 
'pm::array_traits::iterator {aka pm::ptr_wrapper}' to 'const pm::Integer*' in initialization

If it helps I will gladly attach the log file.

The version I am trying to build is the current develop branch 7.5.rc3, but 
I also get an error for the master branch.

Any help would be highly appreciated!


-- 
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 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] A triangulate method that produces quadrilaterals. Why ?

[ams]

While investigating the stl export from 3D plots, (which have been recently 
improved, see trac-ticket-22144 ) I 
found a method in plot/plot3d/parametric_surface.pyx 

 
that is called *triangulate*, but that actually quadrangulates the 
underlying self (maybe it also produces triangles, when some quadrilateral 
is degenerate, I am not sure).

def triangulate(self, render_params=None):
r"""
[…] so normals of the triangles […] 
"""
# […]
face.n = 4 # […]

The reason I looked into it was that it caused problem for saving to stl 
format because the old version of *stl_ascii_string* method assumed that 
the output of a method called *triangulate* would always have only 
*triangles*. *stl_ascii_string* have been modified in ticket 22144 
, but I still thing it's kind of 
counterintuitive to have a *triangulate* method that do not produces 
triangles but quadrilaterals instead. 

Does anybody here knows what were the reasons behind this choice ? And 
where is it used ? 

-- 
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 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] Sage runs in Window's 10's new Unix subsystem

[David Joyner]

On Thu, Jan 12, 2017 at 3:43 AM, GK  wrote:
>
>>
>> I am not having any problem starting the notebook. You might genuinely be
>> out of memory, or hard drive space.
>>
>
> I am not having trouble starting the notebook either, but I can not do
> anything with it, also, no, I am not running out of memory nor hard disk
> space.
>

I've tested the notebook out at work where there's a windows machine.
(a) It doesn't seem to work in IE.
(b) In chrome and FF, the initial command is very slow. Maybe 15
seconds or more. After that, it speeds up but is never snappy like the
CLI.
(c) I only tried the CLI once in windows and it seems to work fine. I
don't remember it being slow.

GK: Does your experience match this?

> I have increased the amount of virtual memory usable by windows to a
> ridiculous amount and I am running everything and monitoring my system at
> the same time and memory/hard disk space do not run out. Perhaps the amount
> of memory or hard disk space allocated by windows to the linux subsystem
> does actually run out, but I do not know how to check that. I related the
> problem with the windows update, as exactly before the update everything ran
> smoothly and right after the update sage never ran again. I do not think
> this is a coincidence...
>
> --
> 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 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+unsubscr...@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: trouble compiling singular

[moritz]

I figured out what the problem was: I had a version of polymake installed 
(3.0.6) and singular checks for a polymake install. However when I removed 
polymake and polymake-config from /usr/local/bin sage could be build 
successfully. When configuring singular one could also pass the 
--disable-polymake flag. 

I hope somebody with a similar problem might find this useful.. 

-- 
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 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-combinat-devel] Fomin's growth diagrams

['Martin R' via sage-combinat-devel]

In https://trac.sagemath.org/ticket/21594 there is a implementation of 
Fomin's growth diagrams for dual graded graphs in quite some generality. 
 For illustration, I implemented RSK and its variants, Domino insertion, 
the Binary Word growth, the Sylvester graph, Young Fibonacci.

I took some care to make adding new growth diagrams very easy.

Could somebody please review it?  The code is already needing review since 
four months...

Many thanks,

Martin

-- 
You received this message because you are subscribed to the Google Groups 
"sage-combinat-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-combinat-devel+unsubscr...@googlegroups.com.
To post to this group, send email to sage-combinat-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-combinat-devel.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-devel] Release note auto-generation RFC

[TB]

On 12/01/17 10:41, 'Julien Puydt' via sage-devel wrote:

I have to point out that this isn't auto-generated since a specific
command has to be entered.

I also notice that towncrier has pretty rough single-level structuring
(feature, bugfix, doc, removal, misc), which might be a bit limitative
for a large project like sagemath.

Wouldn't some directive like "If you think ticket #314159 is of wider
interest, all you have to do is to fill in the Changes-7.6.rst file"
make it possible to both drop this new tool and allow a richer
structure? Said Changes-.rst could start as a copy from a
Changes-template.rst with a prepared structured, which the release
manager would prune at the last moment to remove empty sections.

Snark on #sagemath


What do you think about Debian packages' changelog format?
As a non-expert, I see one can easily add new entries with dch, and 
there are tools which know how to parse the changelog file.


Regards,
TB

--
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 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] Release note auto-generation RFC

['Julien Puydt' via sage-devel]

On 12/01/2017 09:54, Kwankyu Lee wrote:

Wouldn't some directive like "If you think ticket #314159 is of wider
interest, all you have to do is to fill in the Changes-7.6.rst file"
make it possible to both drop this new tool and allow a richer
structure? Said Changes-.rst could start as a copy from a
Changes-template.rst with a prepared structured, which the release
manager would prune at the last moment to remove empty sections.

I guess the idea is to have one "news fragment" file for one merged
ticket instead of a single file that contains all news.


And my point is that this tool doesn't bring anything substantial : if 
you have to get out of your way to add something to the news, then at 
least do so for something nice and complete. In my opinion the 
categories provided by towncrier make it a tiny convenience for a small 
project and uninteresting for a large project.


Now, if towncrier made it possible to name the fragment files something 
like 314159.features.algebraic-geometry.elliptic-curves and generated a 
more structured changelog from that, that would be more convincing. 
[Using a dictionary somewhere to turn the various filename chunks into 
something human-readable and falling back to changing '-' to space and 
capitalizing the first word, say].


Snark on #sagemath

--
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 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] Release note auto-generation RFC

[Kwankyu Lee]

>
> Wouldn't some directive like "If you think ticket #314159 is of wider 
> interest, all you have to do is to fill in the Changes-7.6.rst file" 
> make it possible to both drop this new tool and allow a richer 
> structure? Said Changes-.rst could start as a copy from a 
> Changes-template.rst with a prepared structured, which the release 
> manager would prune at the last moment to remove empty sections. 
>

I guess the idea is to have one "news fragment" file for one merged ticket 
instead of a single file that contains all news.

-- 
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 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] Sage runs in Window's 10's new Unix subsystem

[GK]

>
> I am not having any problem starting the notebook. You might genuinely be 
> out of memory, or hard drive space.
>
>
I am not having trouble starting the notebook either, but I can not do 
anything with it, also, no, I am not running out of memory nor hard disk 
space.

I have increased the amount of virtual memory usable by windows to a 
ridiculous amount and I am running everything and monitoring my system at 
the same time and memory/hard disk space do not run out. Perhaps the amount 
of memory or hard disk space allocated by windows to the linux subsystem 
does actually run out, but I do not know how to check that. I related the 
problem with the windows update, as exactly before the update everything 
ran smoothly and right after the update sage never ran again. I do not 
think this is a coincidence...

-- 
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 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] Release note auto-generation RFC

['Julien Puydt' via sage-devel]

Hi,

On 12/01/2017 00:09, Volker Braun wrote:

There is a somewhat painless approach to generating human-readable
release notes using https://github.com/hawkowl/towncrier. As far as the
ticket author is concerned, if you think that your ticket #12435 is of
wider interest and should be announced then all you'd have to do is add
a file

echo "Added the last twin prime" > newsfragments/12435.feature

Note that the fragment filename starts with the ticket number, so it
won't conflict with other news fragments. Then, when making a new
release, I concatenate the fragments into NEWS.rst as, for example,
in https://github.com/hawkowl/towncrier/blob/master/NEWS.rst


I have to point out that this isn't auto-generated since a specific 
command has to be entered.


I also notice that towncrier has pretty rough single-level structuring 
(feature, bugfix, doc, removal, misc), which might be a bit limitative 
for a large project like sagemath.


Wouldn't some directive like "If you think ticket #314159 is of wider 
interest, all you have to do is to fill in the Changes-7.6.rst file" 
make it possible to both drop this new tool and allow a richer 
structure? Said Changes-.rst could start as a copy from a 
Changes-template.rst with a prepared structured, which the release 
manager would prune at the last moment to remove empty sections.


Snark on #sagemath

--
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 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: Release note auto-generation RFC

[Ralf Stephan]

If you want the name "Sage" (vs. "sage") it must be under src/Sage
like in https://trac.sagemath.org/ticket/22176

-- 
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 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] trouble compiling singular

[moritz]

[I tried to post already yesterday, but my message somehow didn't get 
through]

When trying to build sage (the current develop-branch 7.5) I get an error 
on my debian box with a current sid-install. 

For the end of the logfile, see the end of this post. It also throws some 
of the following errors:

polymake_conversion.cc:176:56: error: cannot convert 
'pm::array_traits::iterator {aka pm::ptr_wrapper}' to 'const pm::Integer*' in initialization

I will gladly attach the entire log file, if that helps. 

part of logs/pkgs/singular-4.1.0p1.log:

../../../gfanlib/gfanlib_matrix.h: In instantiation of 
'gfan::Matrix::RowRef& gfan::Matrix::RowRef::operator=(const 
gfan::Vector&) [with typ = gfan::Rational]':
../../../gfanlib/gfanlib_matrix.h:777:57:   required from here
../../../gfanlib/gfanlib_matrix.h:221:24: warning: comparison between 
signed and unsigned integer expressions [-Wsign-compare]
 assert(v.size()==matrix.width);
^
../../../gfanlib/gfanlib_matrix.h: In instantiation of 
'gfan::Matrix::RowRef& gfan::Matrix::RowRef::operator=(const 
gfan::Vector&) [with typ = gfan::Integer]':
../../../gfanlib/gfanlib_matrix.h:784:66:   required from here
../../../gfanlib/gfanlib_matrix.h:221:24: warning: comparison between 
signed and unsigned integer expressions [-Wsign-compare]
../../../gfanlib/gfanlib_matrix.h: In instantiation of 
'gfan::Matrix::RowRef& gfan::Matrix::RowRef::operator=(const 
gfan::Vector&) [with typ = int]':
../../../gfanlib/gfanlib_matrix.h:792:59:   required from here
../../../gfanlib/gfanlib_matrix.h:221:24: warning: comparison between 
signed and unsigned integer expressions [-Wsign-compare]
Makefile:573: recipe for target 'polymake_la-polymake_conversion.lo' failed
make[8]: *** [polymake_la-polymake_conversion.lo] Error 1



-- 
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 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.