#6521: [with patch, needs work] replace .copy() with .__copy__() in
matrix/matrix0.pyx
----------------------------+-----------------------------------------------
 Reporter:  AlexGhitza      |       Owner:  was       
     Type:  enhancement     |      Status:  new       
 Priority:  minor           |   Milestone:  sage-4.1.2
Component:  user interface  |    Keywords:            
 Reviewer:                  |      Author:            
   Merged:                  |  
----------------------------+-----------------------------------------------

Comment(by kcrisman):

 Replying to [comment:4 jason]:
 > Replying to [comment:3 kcrisman]:
 > > Replying to [comment:2 jason]:
 > > > Is there a deprecation warning now on .copy()?  I didn't see one on
 this patch.
 > > Does there need to be?  I don't recall that in #111 there was, but
 maybe there is supposed to be?
 >
 > Yes, there does need to be a deprecation warning.  #111 was *way* before
 we had the deprecation warning policy, so that's why it wasn't mentioned
 there.  Unfortunately, I think a lot of code (including my code!) has used
 the .copy() function since then that would break.  We need to give us poor
 folks a warning that things are changing.
 Unfortunately, the patch for #111 was only merged a few weeks ago, and is
 new in 4.1.1!   That means that you should probably open a followup patch
 for putting deprecation warnings in for all of those.   And then opening
 another patch that says to remove them in 6 months...

-- 
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/6521#comment:5>
Sage <http://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 post to this group, send email to [email protected]
To unsubscribe from this group, send email to 
[email protected]
For more options, visit this group at 
http://groups.google.com/group/sage-trac?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to