Stephen J. Turner wrote:
>  
>  Hello all,
>  
>  Calling the new spec "1.1" would to me suggest backward compatibility
>  with the 1.0 spec.  If this were true, then I would expect that
>  applications originally written to use a 1.0 implementation should work
>  unmodified with a 1.1 implementation.
>  
>  However, some of the proposed 1.1 changes seem to be incompatible with
>  1.0, including:
>  - renaming the connection function from <ModuleName> to Connect

It's been lower-cased again... connect(). AFAIK, the convention
of calling the connector <ModuleName>  was not always adhered to,
so this may not be a big change.

>  - requiring keyword args for the connection function

Note that the module implementor can put the keywords into a
certain order that makes the constructor behave just like it did
for 1.0, e.g. dsn='',user='',passwd=''.

Hmm, maybe we should fix an order for the most important
keyword arguments.

>  - the new exception class hierarchy

The old "error" exception could be aliased to "Error".

>  - moving the callproc method from the Connection object to the Cursor
>  object

This may look like a big change, but since most interfaces did not
implement callproc() in the first place, I guess it's as bad as
it looks.

>  Should we therefore call the new spec "2.0" instead?

To be honest: I don't really care about the version number. Note that
in Python's own numbering scheme small changes like the ones above
are indeed allowed for minor revisions. Other opinions ?

Maybe we should add an appendix to the spec about the changes
from 1.0 to 1.1.

-- 
Marc-Andre Lemburg                               Y2000: 294 days left
---------------------------------------------------------------------
          : Python Pages > >> http://starship.skyport.net/~lemburg/  :
           ---------------------------------------------------------