Carlos Ribeiro wrote:
On Thu, 7 Oct 2004 19:55:03 -0400, Raymond Hettinger firstname.lastname@example.org wrote:
Where there are multiple, competing third party solutions, Guido has historically resisted ending exploration by locking in a single solution. Instead, he said he prefers "category killers" such as the unittest and logging modules. Martin has also been clear that community acceptance and a commitment to on-going maintenance are also important considerations.
I see the reasoning behind this position. But I fear it can lead to lack of standardization in some areas. There is at least one area where a firm position would greatly clarify things: standard interfaces for modules where multiple providers are always the norm, such as the DB API and WSGI. WSGI is working is way out, but it's still too early to tell if they will be successful. But the DB API could really take advantage of a BDFL-style intervention to settle things. (it does not *need* to be Guido, but it has to be someone with power enough to take a firm stand and enforce it; but I don't know anyone who could assume this role as the undisputed leader of the DB-API effort).
I don't know anything about the way the WSGI specification is developed. The DB-API specification was developed outside the Python development process and has so far been very successful at that.
The DB-SIG which manages the specification is in charge of the process and will continue to work together with module authors and users to accommodate for new features that may become generally available in databases or their interfaces.
Note that there is no need to "settle things": the DB-API spec has been around for many years, is very stable, widely used and still flexible enough to meet requirements of various different database backends.
If you feel that a certain feature is missing, I'd suggest you direct your constructive criticism to the email@example.com.