Re: [sage-devel] What is the expected output of .version()?

2015-09-06 Thread François Bissey
On 09/07/15 06:33, Simon King wrote: > Hi! > > Removing characters on trac has a positive side-effect: I was pointed > to a ticket that was closed as duplicate of #5994. And the last serious work > on #5994 was done 6 years ago. > > Unfortunately, I have marked it as "needs info" 6 years ago, an

Re: [sage-devel] What is the expected output of .version()?

2015-09-06 Thread Volker Braun
There is a canonical "version without patchlevel" provided by the sage_bootstrap library, nobody should re-implement "chopping off chars". E.g. (note the edge case): In [1]: import sys In [2]: sys.path.append('build') In [3]: from sage_bootstrap.package import Package In [4]: Package('singular'

Re: [sage-devel] What is the expected output of .version()?

2015-09-06 Thread Nathann Cohen
> > I don't think that package-version.txt should be used as answer to > package.version() in Sage. I consider this file to be build metadata, > while package.version() should provide upstream's idea of the version > number, using some function or data from the upstream sources. > Can't we ex

Re: [sage-devel] What is the expected output of .version()?

2015-09-06 Thread Jeroen Demeyer
On 2015-09-06 20:33, Simon King wrote: First question: Would you agree that all interfaces should return a string that corresponds to the typical content of the package-version.txt files? No. I don't think that package-version.txt should be used as answer to package.version() in Sage. I consid

[sage-devel] What is the expected output of .version()?

2015-09-06 Thread Simon King
Hi! Removing characters on trac has a positive side-effect: I was pointed to a ticket that was closed as duplicate of #5994. And the last serious work on #5994 was done 6 years ago. Unfortunately, I have marked it as "needs info" 6 years ago, and although I reminded the participants of the ticke