#14499: Some cleaup in sage/combinat/design
---------------------------------+------------------------------------------
       Reporter:  ncohen         |         Owner:  sage-combinat
           Type:  enhancement    |        Status:  needs_review 
       Priority:  major          |     Milestone:  sage-5.10    
      Component:  combinatorics  |    Resolution:               
       Keywords:                 |   Work issues:               
Report Upstream:  N/A            |     Reviewers:               
        Authors:  Nathann Cohen  |     Merged in:               
   Dependencies:  #14483         |      Stopgaps:               
---------------------------------+------------------------------------------

Comment (by Stefan):

 I just looked at this in the developer guide:

 http://www.sagemath.org/doc/developer/coding_in_python.html#deprecation

 It would apply to all of AffineGeometryDesign, ProjectiveGeometryDesign,
 WittDesign, HadamardDesign, BlockDesign_generic (well, maybe this one is
 trickier because it's a class that's still around),
 best_known_covering_design_www, points_from_gap.

 I don't know how strictly the deprecation procedure is enforced (I'm still
 new to Sage development), but it seems common courtesy to me to warn
 current users of where these things have moved to. I'll be ok with not
 deprecating if an experienced Sage developer supports it too.

-- 
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/14499#comment:11>
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?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.


Reply via email to