[Python-Dev] Terminology for PEP 343 (original) (raw)
Brett Cannon bcannon at gmail.com
Fri Jul 1 01:03:48 CEST 2005
- Previous message: [Python-Dev] Terminology for PEP 343
- Next message: [Python-Dev] List copy and clear (was Re: Inconsistent API for sets.Set and build-in set)
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
"Resource managed"?
On 6/30/05, Raymond Hettinger <raymond.hettinger at verizon.net> wrote:
With 343 accepted, we can now add enter() and exit() methods to objects.
What term should describe those objects in the documentation? For instance, if the new magic methods are added to decimal.Context(), do we then describe Context objects as "withable" ;-) The PEP itself doesn't provide much of a clue. The terms "template", "wrapper", and "block" are over-broad and do not provide a metaphor for setup/teardown, r entry/exit, or initialization/finalization. Whatever term is selected, it should be well thought-out and added to the glossary. The choice of words will likely have a great effect on learnability and on how people think about the new tool.
Raymond
Python-Dev mailing list Python-Dev at python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/brett%40python.org
- Previous message: [Python-Dev] Terminology for PEP 343
- Next message: [Python-Dev] List copy and clear (was Re: Inconsistent API for sets.Set and build-in set)
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]