[sage-devel] Re: [min_spanning_tree] It is not operating correctly

2017-12-04 Thread John H Palmieri
Can you explain more fully what is wrong? The output looks like a spanning tree to me. A question and a comment: what do you mean by "the result is 193"? Also, according to the documentation, the "starting_vertex" option is only available for the algorithms "Prim_fringe" and "Prim_edge". On

[sage-devel] Re: Issue with quick start

2017-12-04 Thread Dima Pasechnik
Mind you, some components of Sage have versions of the same command in two different English spellings, e.g. GAP has Center() and Centre(). I propose switching to a language with a consistent meaningful spelling, not all that impossible to understand arbitrary multiple choices. I will open a

[sage-devel] Re: Issue with quick start

2017-12-04 Thread DC
Despite my attempt to bring the discussion into the realm of objectivity, it is apparent that personal preference has won. >>>On Friday, December 1, 2017 at 7:37:57 PM UTC-8, John H Palmieri wrote: > > I think it is much more important to fix bugs and to add new functionality > to Sage. >

Re: [sage-devel] Re: Failure in building Sage (problem with python2-2.7.14)

2017-12-04 Thread Emmanuel Charpentier
Don't worry too much about this one, Trac#24107 is under way (slowly, I know... There is a ton of docs to understand and update...). -- Emmanuel Charpentier Le lundi 4 décembre 2017 16:13:26 UTC+1, Thierry (sage-googlesucks@xxx) a écrit : > > On Mon,

Re: [sage-devel] Re: Failure in building Sage (problem with python2-2.7.14)

2017-12-04 Thread Jeroen Demeyer
On 2017-12-04 16:04, Thierry wrote: The problem in just rebuilding is that there might be old files lying around still interacting Well, those shouldn't interact. If they do, that's a bug. -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To

Re: [sage-devel] Re: Failure in building Sage (problem with python2-2.7.14)

2017-12-04 Thread Thierry
On Mon, Dec 04, 2017 at 04:13:20PM +0100, Thierry wrote: [...] > perhaps python is a "dependent" of openssl spkg, not a "dependency", or > perhaps it is a "dependency" of some virtual openssl package that will be Damn, of course i meant the other way (python depends on meta-openssl, so

Re: [sage-devel] Re: Failure in building Sage (problem with python2-2.7.14)

2017-12-04 Thread Thierry
On Mon, Dec 04, 2017 at 03:58:03PM +0100, Erik Bray wrote: > On Mon, Dec 4, 2017 at 3:47 PM, Jeroen Demeyer wrote: > > On 2017-12-04 15:37, Thierry wrote: > >> > >> No, we have to be able to remove all the old stuff from the package. > > > > > > You said "rebuilds the

Re: [sage-devel] Re: Failure in building Sage (problem with python2-2.7.14)

2017-12-04 Thread Thierry
On Mon, Dec 04, 2017 at 03:47:31PM +0100, Jeroen Demeyer wrote: > On 2017-12-04 15:37, Thierry wrote: > >No, we have to be able to remove all the old stuff from the package. > > You said "rebuilds the package and its dependencies" but you really mean > "uninstalls the package and its

Re: [sage-devel] Re: Failure in building Sage (problem with python2-2.7.14)

2017-12-04 Thread Erik Bray
On Mon, Dec 4, 2017 at 3:47 PM, Jeroen Demeyer wrote: > On 2017-12-04 15:37, Thierry wrote: >> >> No, we have to be able to remove all the old stuff from the package. > > > You said "rebuilds the package and its dependencies" but you really mean > "uninstalls the package

Re: [sage-devel] Re: Failure in building Sage (problem with python2-2.7.14)

2017-12-04 Thread Jeroen Demeyer
On 2017-12-04 15:37, Thierry wrote: No, we have to be able to remove all the old stuff from the package. You said "rebuilds the package and its dependencies" but you really mean "uninstalls the package and its dependencies" (possibly followed by a rebuild which is just a normal build at that

Re: [sage-devel] Re: Failure in building Sage (problem with python2-2.7.14)

2017-12-04 Thread Thierry
On Mon, Dec 04, 2017 at 03:31:13PM +0100, Jeroen Demeyer wrote: > On 2017-12-04 15:23, Thierry wrote: > >A great improvement in > >the dev workflow would be to have a kind of "make clean " that > >rebuilds the package and its dependencies > > Doesn't "make -B " do something like that? I haven't

Re: [sage-devel] Re: Failure in building Sage (problem with python2-2.7.14)

2017-12-04 Thread Jeroen Demeyer
On 2017-12-04 15:23, Thierry wrote: A great improvement in the dev workflow would be to have a kind of "make clean " that rebuilds the package and its dependencies Doesn't "make -B " do something like that? I haven't tried. -- You received this message because you are subscribed to the Google

Re: [sage-devel] Re: Failure in building Sage (problem with python2-2.7.14)

2017-12-04 Thread Jeroen Demeyer
On 2017-12-04 15:23, Thierry wrote: i would vote to consider such issues as not-a-bug I would *personally* report it as a bug if it would happen to me and I know what causes it. Upgrade failures can be because of real bugs. For example, if this would happen on every beta, it would be quite

Re: [sage-devel] Re: Failure in building Sage (problem with python2-2.7.14)

2017-12-04 Thread Erik Bray
On Mon, Dec 4, 2017 at 3:23 PM, Thierry wrote: > Hi, > > On Mon, Dec 04, 2017 at 03:00:07PM +0100, Jeroen Demeyer wrote: >> On 2017-12-04 10:53, Dima Pasechnik wrote: >> >Anyway, it's not a bug. >> >> We are supposed to support incremental builds, so it is a bug.

Re: [sage-devel] Re: Failure in building Sage (problem with python2-2.7.14)

2017-12-04 Thread Thierry
Hi, On Mon, Dec 04, 2017 at 03:00:07PM +0100, Jeroen Demeyer wrote: > On 2017-12-04 10:53, Dima Pasechnik wrote: > >Anyway, it's not a bug. > > We are supposed to support incremental builds, so it is a bug. There have > been several reports of if, so it cannot be due to one misconfigured system.

Re: [sage-devel] Re: Failure in building Sage (problem with python2-2.7.14)

2017-12-04 Thread Erik Bray
On Mon, Dec 4, 2017 at 3:00 PM, Jeroen Demeyer wrote: > On 2017-12-04 10:53, Dima Pasechnik wrote: >> >> Anyway, it's not a bug. > > > We are supposed to support incremental builds, so it is a bug. There have > been several reports of if, so it cannot be due to one

Re: [sage-devel] Re: Failure in building Sage (problem with python2-2.7.14)

2017-12-04 Thread Jeroen Demeyer
On 2017-12-04 10:53, Dima Pasechnik wrote: Anyway, it's not a bug. We are supposed to support incremental builds, so it is a bug. There have been several reports of if, so it cannot be due to one misconfigured system. On the other hand, nobody has bothered to create a ticket for it, so

Re: [sage-devel] Re: Failure in building Sage (problem with python2-2.7.14)

2017-12-04 Thread Dima Pasechnik
On Monday, December 4, 2017 at 9:37:42 AM UTC, Jeroen Demeyer wrote: > > On 2017-12-04 00:46, Dima Pasechnik wrote: > > I saw this as well, while incrementally building 8.1.rc4. > > I cannot reproduce this... > Anyway, it's not a bug. Of course it's not possible to test for all the possible

Re: [sage-devel] Re: Failure in building Sage (problem with python2-2.7.14)

2017-12-04 Thread Jeroen Demeyer
On 2017-12-04 00:46, Dima Pasechnik wrote: I saw this as well, while incrementally building 8.1.rc4. I cannot reproduce 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,