Ok. Retracted. I have been admiring the purity and simplicity of the JSON spec which intentionally has no version number. New changes are therefore only allowed with a new name. That removes a lot of complexity around figuring out what versions of the spec what server implements, etc.
But the wsgi spec is far more complicated than JSON, and I expect that complexity is probably unavoidable. --Mark Ramm On Monday, November 22, 2010, Ian Bicking <i...@colorstudy.com> wrote: > On Mon, Nov 22, 2010 at 5:05 PM, Mark Ramm <mark.mchristen...@gmail.com> > wrote: > > > I would very much prefer it if we could keep the current name or > choose a new unrelated name, not wsgi2 as I think there API changes > warrant a new name to prevent confusion. > > Why? Obviously "2" implies some breaking changes, and the changes are > reasonable enough that it's not a complete change. Most of the changes have > been discussed as "WSGI 2" for a long time preceding this spec anyway. > > > -- > Ian Bicking | http://blog.ianbicking.org > -- Mark Ramm-Christensen email: mark at compoundthinking dot com blog: www.compoundthinking.com/blog _______________________________________________ Web-SIG mailing list Web-SIG@python.org Web SIG: http://www.python.org/sigs/web-sig Unsubscribe: http://mail.python.org/mailman/options/web-sig/archive%40mail-archive.com