[Python-Dev] an alternative to embedding policy in PEP 418 (original) (raw)
Guido van Rossum guido at python.org
Fri Apr 6 23:54:39 CEST 2012
- Previous message: [Python-Dev] an alternative to embedding policy in PEP 418
- Next message: [Python-Dev] an alternative to embedding policy in PEP 418
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
I don't know who started this, but the PEP 418 threads have altogether too much snarkiness and not enough content. It's bad enough that we're bikeshedding so intensely; we don't need clever comebacks in triplicate to every out-of-context argument.
--Guido
On Fri, Apr 6, 2012 at 2:26 PM, Ethan Furman <ethan at stoneleaf.us> wrote:
Lennart Regebro wrote:
On Fri, Apr 6, 2012 at 00:17, Cameron Simpson <cs at zip.com.au> wrote:
Good point, but the same does for using flags. If you don't pass in the MONOTONIC flag, what happens? Only reading the documentation will tell you. As such this, if anything, is an indication that the getclock() API isn't ideal in any incarnation.
Gah! ALL functions are like that! How often do we see questions about max() or split() etc that a close reading of the docs obviate? My point exactly. Huh? Your point is that all APIs are less than ideal because you have to read the docs to know for certain how they work?
Ethan
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/guido%40python.org
-- --Guido van Rossum (python.org/~guido)
- Previous message: [Python-Dev] an alternative to embedding policy in PEP 418
- Next message: [Python-Dev] an alternative to embedding policy in PEP 418
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]