As this issue keeps popping up every week, how about a mechanism to cope
with this kind of change in the future:
In the wizard generated code, add a first line that calls
UpdatedForWeb2PyVersion('1.97.1', true)
(Where the 1.97.1 is the version that the wizard was run in, and 'true'
means raise an exception)
Then, if there are non-backward-compatible changes such as the generic views
thing, this will raise an error, with a link to the book page describing
needed changes. That guarantees attention of whoever is upgrading. After
they know it's working, they can update the version number.
Also, if the models/* code does not contain a call to
UpdatedForWeb2PyVersion .. at all, we can assume e.g. 1.65.1, and call
UpdatedForWeb2Py('1.65.1', false) before calling the client() code; the
'false' here would put the warning in response.flash but would not raise an
exception.
How does that sound as a future-proofing mechanism?
