backwards-incompatible: urlresolvers.reverse no longer silently accepts unused args

[Carl Meyer]

Pre-[8760], urlresolvers.reverse would silently accept "extra" args and return a matched URL that didn't need the arg. Post-[8760], all args must be matched in the URL pattern.

The newer behavior is probably more correct, but this is a backwards-incompatible change for anyone who was relying on the prior behavior.

If the correct thing here is to document this on the BackwardsIncompatibleChanges page, I'm happy to do so - just checking to be sure this isn't a bug, since the [8760] rewrite was advertised as "fully backwards-compatible."

[Julien Phalip]

Marking 1.0 just to make sure it doesn't get unnoticed.

[Malcolm Tredinnick]

I can probably fix this, at least for keyword arguments, so that extra arguments are permitted. Won't be possible for positional arguments, though. I'll have a look at it.

[Malcolm Tredinnick]

On second thoughts, it's a bad idea to allow this (which is a shame, because it's a three line change). It means that the first match (often the one requiring the least number of arguments) will work, not the one that exactly matches. Which means optional arguments will be omitted and that's bad. I'll update the backwards-incompatible changes page (you can't do it, since we made it read-only a while back after some vandalism).

[Jacob]

Milestone 1.0 deleted