Malcolm Tredinnick wrote:
> Don't reopen issues that have been marked "wontfix". This mark
> means that the decision has been made that we can't or won't fix
> this particular issue. If you're not sure why, please ask on
> `django-developers`_.
>
> That's
Malcolm,
Thank you for clarification. Just getting used to the open-source
project. BTW feeling myself very strange, because experience only in
commercial software is available :-)
~Alex
You wrote 11 августа 2007 г., 7:35:01:
> On Mon, 2007-08-06 at 09:49 +0400, Alex Nikolaenkov wrote:
> [...]
On Mon, 2007-08-06 at 09:49 +0400, Alex Nikolaenkov wrote:
[...]
> > (B) Reopening tickets because you disagree with the resolution is also
> > quite impolite. Bringing the issue here is the right way to go, but
> > leave the ticket closed unless you can convince us to rep-open it.
> I never heard
Tom,
Thank you for clarification. Now that makes a lot of sense for me.
~ Alex
You wrote 6 ??? 2007 ?., 20:28:20:
> On 8/6/07, Alex Nikolaenkov <[EMAIL PROTECTED]> wrote:
>> > If a core dev closes a ticket with a "wontfix", you shouldn't re-open
>> > the ticket unless you've made a compelli
On 8/6/07, Alex Nikolaenkov <[EMAIL PROTECTED]> wrote:
> > If a core dev closes a ticket with a "wontfix", you shouldn't re-open
> > the ticket unless you've made a compelling case on django-dev and
> > gotten the core devs to change their minds. "Wontfix" essentially
> > means that a design deci
> On 8/6/07, Alex Nikolaenkov <[EMAIL PROTECTED]> wrote:
>>
>> I never heard that tickets should not be reopened if you disagree. If
>> the bug is still reproducible it should be reopened. If its
>> resolution is changed to "won't fix", one should point why. And
>> not just - "Oh, it is good enoug
You wrote 6 ??? 2007 ?., 16:38:25:
> On 8/6/07, Alex Nikolaenkov <[EMAIL PROTECTED]> wrote:
>> BTW, Can we attach configurable plug-ins to the built-in webserver?
>> (* I'm interested in possibility. Can code "case insensitive urls
>> plug-in" by myself. *)
> You're looking for "middleware":
On 8/6/07, Alex Nikolaenkov <[EMAIL PROTECTED]> wrote:
>
> I never heard that tickets should not be reopened if you disagree. If
> the bug is still reproducible it should be reopened. If its
> resolution is changed to "won't fix", one should point why. And
> not just - "Oh, it is good enough now".
On 8/6/07, Kai Kuehne <[EMAIL PROTECTED]> wrote:
> Please just learn django. Thank you.
Hey, that's out of line. Around here we treat everyone with respect;
Alex deserves better. Next time you feel the urge to post something of
this nature, take it to Digg.
Only *you* can prevent flamewars!
Jac
Hi,
On 8/6/07, Alex Nikolaenkov <[EMAIL PROTECTED]> wrote:
> > Right, so moving on to your real question:
> >>Here is an example of case-insensitive urls. They rock:
> >>http://www.askeri.ru/PUBLISH/
> >>http://www.askeri.ru/publish/
>
> > They do indeed rock. Luckily, supporting them
On 8/6/07, Alex Nikolaenkov <[EMAIL PROTECTED]> wrote:
> BTW, Can we attach configurable plug-ins to the built-in webserver?
> (* I'm interested in possibility. Can code "case insensitive urls
> plug-in" by myself. *)
You're looking for "middleware":
http://www.djangoproject.com/documentation/mid
Twas brillig at 09:49:49 06.08.2007 UTC+04 when Alex Nikolaenkov did gyre and
gimble:
AN> BTW, Can we attach configurable plug-ins to the built-in webserver? (* I'm
AN> interested in possibility. Can code "case insensitive urls plug-in" by
AN> myself. *)
I already pointed out that Django m
GUYS, ME BAD. Neither dicking, nor trolling. Answers to Jacob's letter
below. Thank you for your responses.
> On 8/5/07, Alex Nikolaenkov <[EMAIL PROTECTED]> wrote:
>>** I've posted corresponding ticket.
>>http://code.djangoproject.com/ticket/5090
>>Now it is closed as "won't fix". At
On 8/5/07, James Bennett <[EMAIL PROTECTED]> wrote:
> I'm almost certain it has to do with a combination of the regular
> expression patterns for the URLs (minor contribution) and the database
> collation in use (major contribution). Which, again, means that it's
> not something Django is necessar
On 8/5/07, Alex Nikolaenkov <[EMAIL PROTECTED]> wrote:
>** I've posted corresponding ticket.
>http://code.djangoproject.com/ticket/5090
>Now it is closed as "won't fix". At least the resolution should be
>changed to "By Design" if you guys don't like sites built on django
>bein
On 8/5/07, Brett Hoerner <[EMAIL PROTECTED]> wrote:
> Not on our live site. And I just made a fresh django-trunk project to
> test it, didn't work there either. Although aren't resolvers just
> normal Python REs, so you could possibly have set this for yourself
> somehow?
I'm almost certain it
On 8/5/07, James Bennett <[EMAIL PROTECTED]> wrote:
> Django handles both just fine, returns the same page for both.
Not on our live site. And I just made a fresh django-trunk project to
test it, didn't work there either. Although aren't resolvers just
normal Python REs, so you could possibly h
> And again, I'll reiterate that the type of user who doesn't understand
> case-sensitivity is the type of user who -- verified by repeated
> real-world usability testing -- finds MySpace by going to Google and
> typing "myspace.com" into the search box. An astonishingly high
> percentage of web
Finger slipped on the "send" shortcut, continuing where I left off...
On 8/5/07, James Bennett <[EMAIL PROTECTED]> wrote:
> And again, I'll reiterate that the type of user who doesn't understand
> case-sensitivity is the type of user who -- verified by repeated
> real-world usability testing -- f
On 8/5/07, Alex Nikolaenkov <[EMAIL PROTECTED]> wrote:
> Imagine that your site hosting photos has got the following urls
> belonging to different users:
> http://mysite.com/John/
> http://mysite.com/john.
Except those aren't different URLs. And now that I'm slightly more
awake I'm wondering why
Twas brillig at 17:31:05 05.08.2007 UTC+04 when Alex Nikolaenkov did gyre and
gimble:
AN> Some of them do not and some do. Now a lot of people work with computer but
AN> only a few are programmers and understand THE BIG DIFFERENCE. The
AN> comprehensive urls are very good. You can remember t
You wrote 5 ??? 2007 ?., 17:15:11:
> On 8/5/07, Alex Nikolaenkov <[EMAIL PROTECTED]> wrote:
>>The urls are pretty same. But the second one causes 404 Response.
>>While typing the second url the user tries to access typing its
>>address and types "Simpsons" instead of "simpsons". I
On 8/5/07, Alex Nikolaenkov <[EMAIL PROTECTED]> wrote:
>The urls are pretty same. But the second one causes 404 Response.
>While typing the second url the user tries to access typing its
>address and types "Simpsons" instead of "simpsons". In terms of
>nix-like systems this is a ma
Hello guys,
Django is positioned as a tool for perfectionists. So there is a
few questions which are very valuable for guys making the best web-sites:
* Case-sensitive urls.
Take a look:
http://www.coastalbeat.com/news/2007/jul/30/simpsons/
http://www.coastalbeat.com/news/2007/jul/30/
24 matches
Mail list logo