A RetroSearch Logo

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Search Query:

Showing content from https://mail.python.org/pipermail/python-dev/2005-October/057818.html below:

[Python-Dev] PEP 351, the freeze protocol

[Python-Dev] PEP 351, the freeze protocolJosiah Carlson jcarlson at uci.edu
Mon Oct 31 20:28:20 CET 2005
Steve Holden <steve at holdenweb.com> wrote:
> 
> Josiah Carlson wrote:
> [...]
> >>Perhaps I didn't make it clear. The difference between wxPython's Grid
> >>and my table is that in the table, most values are *computed*. This
> >>means that there's no point in changing the values themselves. They
> >>are also used frequently as set members (I can describe why, but it's
> >>a bit complicated.)
> > 
> > Again, user semantics.  Tell your users not to modify entries, and/or
> > you can make copies of objects you return.  If your users are too daft
> > to read and/or follow directions, then they deserve to have their
> > software not work.
> > 
> That sounds like a "get out of jail free" card for Microsoft and many 
> other software vendors ...

If/when vendors are COMPLETE in their specifications and documentation,
they can have that card, but being that even when they specify such
behaviors they are woefully incomplete, there is not a card to be found,
and I stand by my opinion.

 - Josiah

More information about the Python-Dev mailing list

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