On Mon, May 05, 2003 at 09:50:05AM -0400, Guido van Rossum wrote:
> > My comment was not specifically about Moshe's use case - it's about
> > the meaning of deprecation in Python.
> >
> > Does it always have to mean "start replacing because it *will* go
> > away" as seems to be implied by PEP 5 or perhaps in some cases it
> > could just mean "please don't use this in new code, okay" ?
>
> I think that can be safely left up to the individual programmer, who
> has a better idea (hopefully) on the life expectancy of his code. We
> try to give guidance about the urgency of the deprecation e.g. in PEPs
> or by using the normally-silent PendingDeprecation (which suggests
> it's not urgent :-).
I'm afraid this is too subtle for me. I'll ask my question a third time,
hoping for an answer that a mere mortal can understand:
Are all deprecated features on death row or are some of them merely
serving a life sentence?
Oren
"Do not meddle in the affairs of BDFLs,
for they are subtle and quick to anger"
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4