On Wed, 20 Feb 2002, Fred L. Drake, Jr. wrote: > Moore, Paul writes: > > [BTW, this reminds me of your point on what is documented. I believe that > > the PEPs and descrintro count as the canonical documentation of these > > features. If they haven't been fully migrated into the Python documentation > > set yet, that's a secondary issue. The PEPs *are* the definition of what was > > agreed - people had time to comment on the PEPs at the time. And the > > descrintro document is the current draft of the user-level documentation. > > You can assume it will end up in the manuals. That's my view...] > > This is my perspective as well. I'm not in a hurry to document > relatively volatile feature that may change and (hopefully!) be > available using a nicer syntax in the future. Then what is the criterion for deciding when to apply the standard Python deprecation procedures when things like super() and the __slots__ change? # Python 2.3? from __future__ import super_as_builtin from __future__ import hidden_slots I had (possibly incorrectly) assumed that the criterion was when it was officially documented in a release. -Kevin -- Kevin Jacobs The OPAL Group - Enterprise Systems Architect Voice: (216) 986-0710 x 19 E-mail: jacobs@theopalgroup.com Fax: (216) 986-0714 WWW: http://www.theopalgroup.com
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