Changes between Initial Version and Version 1 of Ticket #8764


Ignore:
Timestamp:
Sep 1, 2008, 5:22:13 PM (16 years ago)
Author:
Malcolm Tredinnick
Comment:

(Fixed description formatting)

It's pretty much accidental that that ever worked. There are cases where mixing positional and keyword arguments will given incorrect results in the previous code and even more so now (with optional groups). So, ok, there's an inadvertent backwards incompatibility for something that only worked by accident. It's simple to work around: pass in either just positional arguments or just keyword arguments. Both are easy enough to do.

Somebody will update the BackwardsIncompatibleChanges page at some point and we can add a docs note. For now, the error message is clear enough about what needs to be changed in anybody's code that was relying on this.

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #8764

    • Property Milestone 1.0
  • Ticket #8764 – Description

    initial v1  
    1616I'll write an example of the problem. All my urls are prepared
    1717following the best SEO rules, so in many places I have urls like:
    18 (r'^(.*)-f(?P<id>\d+)\.html$','view_photo')
     18`(r'^(.*)-f(?P<id>\d+)\.html$','view_photo') `
    1919
    2020this would make the url:
    21 my-photo-f2.html
     21`my-photo-f2.html`
    2222
    2323I get the url using:
Back to Top