Greg Stein wrote:
>
> Jim Fulton wrote:
> >...
> > A while ago I asked for some documentation on the Buffer
> > interface. I basically got silence. At this point, I
>
> I think the silence was caused by the simple fact that the documentation
> does not (yet) exist. That's all... nothing nefarious.
I didn't mean to suggest anything nefarious. I do think that a change that
affects something as basic as the standard object type layout and that
generates this much discussion really should be documented before it
becomes part of the core. I'd especially like to see some kind of document
that includes information like:
- A problem statement that describes the problem the change is
solving,
- How does the solution solve the problem,
- When and how should people writing new types support the new
interfaces?
We're not talking about a new library module here. There's been
a change to the core object interface.
Jim
--
Jim Fulton mailto:jim@digicool.com Python Powered!
Technical Director (888) 344-4332 http://www.python.org
Digital Creations http://www.digicool.com http://www.zope.org
Under US Code Title 47, Sec.227(b)(1)(C), Sec.227(a)(2)(B) This email
address may not be added to any commercial mail list with out my
permission. Violation of my privacy with advertising or SPAM will
result in a suit for a MINIMUM of $500 damages/incident, $1500 for
repeats.
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