"Stephen J. Turnbull" <step...@xemacs.org> writes: > I have to admit Jean-Paul's explanation a pretty convincing reason for > adopting "future" rather than "promise". But I'm with Skip, I would > prefer that the module be named "future" rather than "futures".
Has anyone in this very long thread raised the issue that Python *already* uses this term for the name of a module with a totally unrelated purpose; the ‘__future__’ pseudo-module? That alone seems a pretty strong reason to avoid the word “future” (singular or plural) for some other module name. -- \ “Creativity can be a social contribution, but only in so far as | `\ society is free to use the results.” —Richard Stallman | _o__) | Ben Finney _______________________________________________ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
