`engine.execute()` no longer accepts positional tuple

[Former user]

This .3.5 change:

    - fixed argument passing to straight textual execute() on engine,
      connection. can handle *args or a list instance for positional, **kwargs
      or a dict instance for named args, or a list of list or dicts to invoke
      executemany()

breaks backward compatibility when args are being passed as a tuple (e.g. self.engine.execute(sql, (docID,))). Positional tuple passing is the norm in DB-API libraries, so you might want to maintain this (especially if lists are accepted).

[Mike Bayer]

changeset:2490