#17449: deprecate/remove Graph.to_partition and Poset.to_graph
-------------------------+-------------------------------------------------
       Reporter:         |        Owner:
  ncohen                 |       Status:  needs_review
           Type:         |    Milestone:  sage-6.5
  defect                 |   Resolution:
       Priority:  major  |    Merged in:
      Component:  graph  |    Reviewers:
  theory                 |  Work issues:
       Keywords:         |       Commit:
        Authors:         |  a8822900d5d9e428f4fd92d52ed9d00840ef61df
  Nathann Cohen          |     Stopgaps:
Report Upstream:  N/A    |
         Branch:         |
  u/ncohen/17449         |
   Dependencies:         |
-------------------------+-------------------------------------------------
Changes (by ncohen):

 * cc: dimpase (added)


Comment:

 > Again, the function is documented (and we have interactive
 documentation). It's not hurting anyone, so there's no problem; just leave
 it be.

 I do believe that it does harm by being there. It is not a function that
 should ever be used in Sage or by anyone else, as other ways exist to get
 the same result and because its name is unclear: we could very well decide
 to make it return a different graph later, the function would still be
 correct as ".to_graph()" would still turn the Poset into "a graph". I
 think that knowledgeable people here (like Dima) call that 'semantics'.

 While I understand that you want users to easily find out that there
 exists a way to get a graph from a `Poset` by looking at the list of
 methods, I also believe that ".incomparability_graph" does the job and
 that users will find it. Those who know what they are looking for will
 find `.hasse_diagram` quickly enough.

 Somehow, I think that it all boils down to not say "the integer" but "an
 integer" when "the integer" is not uniquely determined. It would be nice
 if Sage had this level of strictness unless it really goes in the way of
 readability.

 Would you be willing, despite everything, to let us procede with the
 removal of this function ? The considerations above matter to me, and also
 to some extent to the other persons who concurred on the sage-devel
 thread.

 Thanks,

 Nathann

--
Ticket URL: <http://trac.sagemath.org/ticket/17449#comment:19>
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