OK, I see, thanks. It was just my point view that you devs might
consider for the future.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To post to this group, send email to django-develope
On Sun, Feb 22, 2009 at 11:29 AM, rihad wrote:
> Nothing, really, It was just a design suggestion.
I think that's the basic hang-up you're running into here: we don't
really do that kind of development. Every single piece of code in
Django exists because someone -- often lots of people -- have a
On Sun, Feb 22, 2009 at 12:29 PM, rihad wrote:
>
>
>
> On Feb 22, 7:47 pm, Jacob Kaplan-Moss
> wrote:
> > On Sun, Feb 22, 2009 at 9:37 AM, rihad wrote:
> > > Unless someone kindly proves me wrong, I really do think trailing
> > > slashes in the URL should be optional,
> >
> > As Russ already sa
On Feb 22, 7:47 pm, Jacob Kaplan-Moss
wrote:
> On Sun, Feb 22, 2009 at 9:37 AM, rihad wrote:
> > Unless someone kindly proves me wrong, I really do think trailing
> > slashes in the URL should be optional,
>
> As Russ already said -- did you read his post? -- this is already *up
> to you*. If
On Sun, Feb 22, 2009 at 9:37 AM, rihad wrote:
> Unless someone kindly proves me wrong, I really do think trailing
> slashes in the URL should be optional,
As Russ already said -- did you read his post? -- this is already *up
to you*. If you want trailing slashes to be optional:
1. Set APPEND_SL
On Feb 22, 5:29 pm, George Vilches wrote:
> Take this example:
>
> urlpatterns = patterns('',
> (r'hello', 'view1'),
> (r'hello/', 'view2'),
> )
>
(I assume both ^ and $ are in their place) Relying on the difference
in only the trailing slashes is, ugh, awkward. Slash shouldn't be
trea
"Those are most *NOT* definitely the same". Typos too early in the
morning, sorry about that.
On Feb 22, 2009, at 8:29 AM, George Vilches wrote:
>
>
> On Feb 22, 2009, at 7:44 AM, rihad wrote:
>> I was just special-casing the backslash, which is special anyway,
>> otherwise APPEND_SLASH would
On Feb 22, 2009, at 7:44 AM, rihad wrote:
> I was just special-casing the backslash, which is special anyway,
> otherwise APPEND_SLASH wouldn't exist.
> Moreover, hello and hello/ (and hello/) _are_ the same URL to
> Django, otherwise it wouldn't redirect to the url with the slash
> appended.
On Feb 22, 4:44 pm, rihad wrote:
> amount of trailing slashes
number of trailing slashes. Sorry for my English. ;-/
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To post to this group,
On Feb 22, 3:55 pm, Russell Keith-Magee
wrote:
> So - what exactly are you proposing that we change in Django?
>
> Looking at your proposal as a purely end-user suggestion: using
> 'hello/*$' means that hello// will match your URL pattern.
> 'hello/?$' would be a safer match, as it would on
On Sun, Feb 22, 2009 at 8:36 PM, rihad wrote:
>
> Hi, devs,
> I'm sure I'm not the only user who doesn't like the look of trailing
> slashes in URLs, or more precisely, the difference in behavior that
> they imply for Django users. How about simply changing this:
>
>(r'^hello/$', hello),
Hi, devs,
I'm sure I'm not the only user who doesn't like the look of trailing
slashes in URLs, or more precisely, the difference in behavior that
they imply for Django users. How about simply changing this:
(r'^hello/$', hello),
to this
(r'^hello/*$', hello),
so that any numbe
12 matches
Mail list logo
