Re: [sage-devel] Re: SageNB, publishing and error 500

2017-08-23 Thread Jori Mäntysalo
Is there an easy way to see what has been done in .../sage/local/lib/python2.7/site-packages/flask/ and in .../sage/local/lib/python2.7/site-packages/sagenb/flask_version/ between version 8.0 and the one before it? Something like git blame? With Google I found for example https://stackoverflo

Re: [sage-devel] Template (cookiecutter) for easily distributing SageMath code

2017-08-23 Thread Jean-Pierre Flori
Oh and the MANIFEST.in file is not quite good at the moment. You could add pxd files in there. On Wednesday, August 23, 2017 at 2:57:03 PM UTC-7, Jean-Pierre Flori wrote: > > Yes! > I support this :) > > My only suggestion would be to get rid of using the travis command. > And maybe move the get_a

Re: [sage-devel] Template (cookiecutter) for easily distributing SageMath code

2017-08-23 Thread Jean-Pierre Flori
Yes! I support this :) My only suggestion would be to get rid of using the travis command. And maybe move the get_all_version_names into the fake sagemath package. On Wednesday, August 23, 2017 at 2:45:18 PM UTC-7, Marc Masdeu wrote: > > This is essentially what they are supposed to be. The main

Re: [sage-devel] Template (cookiecutter) for easily distributing SageMath code

2017-08-23 Thread Marc Masdeu
This is essentially what they are supposed to be. The main goal of this cookie cutter is to easily set up the project with Travis CI and automatic documentation generation and deployment. Marc - marc.masdeu AT gmail DOT com

Re: [sage-devel] Re: Template (cookiecutter) for easily distributing SageMath code

2017-08-23 Thread Marc Masdeu
This seems like a great idea. I am happy to be in the list of "maintenance" people as well. On the other issue, you are not probably the right target for the cookie cutter thingy, but I believe that it's a quite convenient tool if a developer has never set this up before (like myself six months ag

Re: [sage-devel] Re: Random testing for finite lattices

2017-08-23 Thread Travis Scrimshaw
On Wednesday, August 23, 2017 at 12:51:54 PM UTC-5, Jori Mäntysalo wrote: > > On Wed, 23 Aug 2017, Travis Scrimshaw wrote: > > > Thank you for doing this. Do you want to add this as a file into the > > $SAGE_SRC/sage/tests? How long does it take to run these tests on your > > system? > > It s

Re: [sage-devel] Re: Random testing for finite lattices

2017-08-23 Thread Jori Mäntysalo
On Wed, 23 Aug 2017, Travis Scrimshaw wrote: Thank you for doing this. Do you want to add this as a file into the $SAGE_SRC/sage/tests? How long does it take to run these tests on your system? It seems to already be more than a second per lattice. This kind of randomized stress testing can n

Re: [sage-devel] Template (cookiecutter) for easily distributing SageMath code

2017-08-23 Thread Jeroen Demeyer
On 2017-08-23 17:44, Marc Masdeu wrote: I know that there is several people who think that this is not the way that code should be distributed. I am asking feedback from the complementary set of people, really (although constructive comments from anyone are definitely welcome!). My personal opi

[sage-devel] Re: Template (cookiecutter) for easily distributing SageMath code

2017-08-23 Thread Vincent Delecroix
One thing (IMHO much more important than the "cookie cutter" buisness) is to actually have a community supported language for SageMath in travis [1]. My aim is to allow the following in the travis script {{{ language: "SageMath" version: - "7.6" - "8.0" }}} What need to be done 1) have 3 "o

[sage-devel] Template (cookiecutter) for easily distributing SageMath code

2017-08-23 Thread Marc Masdeu
After some work (building upon github.com/sagemath/sage_sample) that some of us did during Sage Days 87 and the Leiden workshop that took place a few weeks ago, I'd like to collect some feedback / pull requests on a first attempt at making it super easy for anyone to get their own working GitHu

[sage-devel] Re: Random testing for finite lattices

2017-08-23 Thread Travis Scrimshaw
Thank you for doing this. Do you want to add this as a file into the $SAGE_SRC/sage/tests? How long does it take to run these tests on your system? Best, Travis On Tuesday, August 22, 2017 at 11:27:28 PM UTC-5, Jori Mäntysalo wrote: > > I have been doing some quality check for finite lattice c

[sage-devel] Re: mozilla-firefox not found; notebook does not open browser

2017-08-23 Thread Jan Groenewald
Hi On 23 August 2017 at 15:22, Jan Groenewald wrote: > /srv/sage-8.0/local/bin/sage-native-execute: 6: > /srv/sage-8.0/local/bin/sage-native-execute: mozilla-firefox: not found > The sage7.4 from debian repositories does the same, using xdg-open 0 jan@jan-desktop:/srv/sage-8.0$sage ┌

[sage-devel] mozilla-firefox not found; notebook does not open browser

2017-08-23 Thread Jan Groenewald
Hi There is no command mozilla-firefox on Debian 9, so the notebook does not automatically open in a browser: 0 jan@jan-desktop:/srv/sage-8.0$./sage ┌┐ │ SageMath version 8.0, Release Date: 2017-07-21 │ │ Type

Re: [sage-devel] decorators on cdef (member) functions

2017-08-23 Thread Jeroen Demeyer
On 2017-08-22 16:43, Ralf Stephan wrote: Is there a chance one can put a @doc_index decorator on cdef methods in a Cython file? Not without patching Cython. This isn't the first time this problem came up, so maybe this is a less crazy idea than it sounds initially. Now, often the *features*

Re: [sage-devel] Re: SageNB, publishing and error 500

2017-08-23 Thread Jori Mäntysalo
On Tue, 22 Aug 2017, kcrisman wrote:  What happens if you ignore that and directly do sage --notebook=sagenb? Tested, no help. The same internal error, but the publishing and unpublishing works. -- Jori Mäntysalo