On Tue, 29 Feb 2000, Greg Stein wrote: > On Tue, 29 Feb 2000, Ken Manheimer wrote: > >... > > None the less, for those practicing it, the incorrectness of it will be > > fresh news. I would be less sympathetic with them if there was recent > > warning, eg, the schedule for changing it in the next release was part of > > the current release. But if you tell somebody you're going to change > > something, and then don't for a few years, you probably need to renew the > > warning before you make the change. Don't you think so? Why not? > > I agree. > > Note that Guido posted a note to c.l.py on Monday. I believe that meets > your notification criteria. Actually, by "part of the current release", i meant having the deprecation/impending-deletion warning in the release notes for the release before the one where the deletion happens - saying it's being deprecated now, will be deleted next time around. Ken klm@digicool.com I mean, you tell one guy it's blue. He tells his guy it's brown, and it lands on the page sorta purple. Wavy Gravy/Hugh Romney
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