#18972: twographs and Seidel switching
-------------------------------------+-------------------------------------
       Reporter:  dimpase            |        Owner:
           Type:  enhancement        |       Status:  needs_review
       Priority:  major              |    Milestone:  sage-6.9
      Component:  graph theory       |   Resolution:
       Keywords:                     |    Merged in:
        Authors:                     |    Reviewers:  Nathann Cohen
Report Upstream:  N/A                |  Work issues:
         Branch:                     |       Commit:
  u/dimpase/seidelsw                 |  25eec1b6d18bb021eccd4b04774111097ff8f3b5
   Dependencies:  #18960, #18948,    |     Stopgaps:
  #18988, #18991, #18986, #19018,    |
  #19019                             |
-------------------------------------+-------------------------------------

Comment (by ncohen):

 > You are not alone, for many scientific discoveries were made this way,
 by mistake...

 Let me sum it up:
 1) You tell me that I am forced to accept it because there is a precedent
 and that somebody thought that it would be better this way. So I should
 obey his judgement.
 2) You learn that I did it myself, and I tell you that it was a mistake.
 3) You tell me that I should do it anyway, because many mistakes are
 valuable.

 I just see you bend the truth wherever it can help you.

 > well, you have invented it already, with `IncidenceSystem`. True, lots
 of deprecations ahead --- how else would you manage to clean up the global
 namespace?

 That's a design decision for sage-devel.

 > At the moment on this ticket you pursue the line that the classes must
 be hidden from the user

 I spent weeks writing code that has to be imported manually. Nobody died.

 > you admit it yourself.

 I am the only reference, when it comes to figure out what *I* think.

 > IMHO either having `TwoGraph` out there in the global namespace (with
 10000 other things already there), or having it in designs.TAB is
 reasonable; pick one, and let us move on.

 This is not the choice we have to make. The choice it between:
 1) Global namespace (No)
 2) Manual import (possible)
 3) `designs.TwoGraph` -- must be a collective decision to move everything
 into the catalogs.

 So we are not stuck. If you pick 2, we can have this ticket pass right now
 and discuss 3 on sage-devel while being able to continue the development
 of this SRG module. You will easily admit that it does not block us for
 anything.

 Nathann

--
Ticket URL: <http://trac.sagemath.org/ticket/18972#comment:129>
Sage <http://www.sagemath.org>
Sage: Creating a Viable Open Source Alternative to Magma, Maple, Mathematica, 
and MATLAB

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

Reply via email to