IMHO it would be best to not have deprecated methods in the tab completion 
to start with.

However, its not trivial to find out that something is deprecated. Of 
course you can easily check for the decorator, but a method could also end 
up throwing a deprecation warning because it calls a deprecated method. Or 
call the deprecation warning in the method body.



On Wednesday, September 24, 2014 3:54:16 PM UTC+1, Nathann Cohen wrote:
>
> Hello everybody !
>
> Here I was deprecating stuff, and I wondered: could we make it explicit in 
> the tab-completion that some functions are deprecated ?
>
> In particular, I have to (I am not proud) replace a (now deprecated) 
> designs.orthogonal_array with a (note the terminal 's') 
> designs.orthogonal_arrays.
>
> Wouldn't it be cool if typing "designs.<tab>" would display the first 
> deprecated function in light gray, so as to mean "it's disappearing" ?
>
> I was wondering how to prevent users from reading the (long) documentation 
> of this function before noticing that it is deprecated when they call it, 
> only to see how the new one works.
>
> Clearly not critical :-P
>
> Nathann
>

-- 
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, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

Reply via email to