or
URL('account', 'log_in')
On Dec 29, 3:14 am, Kenneth Lundström
wrote:
> If I remember correctly there was something about this on the list.
>
> I think you use the URL the wrong way and until version 1.83.2 the
> helper worked wrongly. In your case it "worked" but it has been
> corrected and
It doesn't break backwards compatibility, because it *should not* work
the way it did.
@massimo: I think a SyntaxError should not be used for a case like
this. See that the syntax is correct and the passed values not, a
ValueError or the like shall be used.
On 29 Dez., 11:59, Kenneth Lundström
w
I agree.
On Dec 29, 7:29 am, snapy666 wrote:
> It doesn't break backwards compatibility, because it *should not* work
> the way it did.
>
> @massimo: I think a SyntaxError should not be used for a case like
> this. See that the syntax is correct and the passed values not, a
> ValueError or the li
Thanks everyone.
It worked.
On Dec 29, 6:45 pm, mdipierro wrote:
> or
>
> URL('account', 'log_in')
>
> On Dec 29, 3:14 am, Kenneth Lundström
> wrote:
>
> > If I remember correctly there was something about this on the list.
>
> > I think you use the URL the wrong way and until version 1.83.2 th
Btw, in case you're new to these things, the main point of URL helpers
(called URL generators in some frameworks) is to generate the URL
based on the information about the internal structure of the
application. This is done to avoid hard-coding the paths. If you
merely use the URL helper function t
On Dec 29, 2010, at 4:32 PM, Branko Vukelić wrote:
>
> Btw, in case you're new to these things, the main point of URL helpers
> (called URL generators in some frameworks) is to generate the URL
> based on the information about the internal structure of the
> application. This is done to avoid hard
6 matches
Mail list logo
