Re: some trouble with an older bug
Hi Julian, Julian schrieb: >> Ahem ... where's the patch in the ticket? Perhaps I'm being dumb, but I >> honestly don't see one. >> > > Okay, sorry, it should have been this link: > > http://code.djangoproject.com/ticket/285 > > but maybe i am totally wrong and better stop writing. Well, to answer you original question: the patch author wasn't sure whether the solution is correct, and nobody has taken the time to review it and test all the cases. That's why the patch has not been applied. Michael --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-developers@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-developers?hl=en -~--~~~~--~~--~--~---
Re: some trouble with an older bug
> > Ahem ... where's the patch in the ticket? Perhaps I'm being dumb, but I > honestly don't see one. > Okay, sorry, it should have been this link: http://code.djangoproject.com/ticket/285 but maybe i am totally wrong and better stop writing. julian > Michael --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-developers@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-developers?hl=en -~--~~~~--~~--~--~---
Re: some trouble with an older bug
Julian schrieb: > Sorry, i did not want to offend someone, but it was just a lttle bit > frustrating. > > there is a patch wich was postet here: > > http://code.djangoproject.com/ticket/1516 > > but it has not been applied to the yet, maybe i will do it manually > with my own local django-installation. Ahem ... where's the patch in the ticket? Perhaps I'm being dumb, but I honestly don't see one. Michael --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-developers@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-developers?hl=en -~--~~~~--~~--~--~---
Re: some trouble with an older bug
Sorry, i did not want to offend someone, but it was just a lttle bit frustrating. there is a patch wich was postet here: http://code.djangoproject.com/ticket/1516 but it has not been applied to the yet, maybe i will do it manually with my own local django-installation. kind regards julian On 2 Sep., 12:00, Malcolm Tredinnick <[EMAIL PROTECTED]> wrote: > On Sun, 2007-09-02 at 02:49 -0700, Julian wrote: > > hi there, > > > until now i am very happy with django, but something made me spent > > some hours of time with it, i've figured this out: > > >http://code.djangoproject.com/ticket/5320 > > > wich has an underlying issue: > > >http://code.djangoproject.com/ticket/1516 > > > wich is obviously not solved yet. it occurrs in a typically situation > > (django-application in a subfolder with fastcgi) and isn't very well > > documented (not even a little comment in the docs). > > > please tell me why noone has it fixed yet and when do you plan to do? > > Perhaps you could spend a couple of minutes searching the archives -- > search for SCRIPT_NAME for example -- to see where this has been > discussed before (the last time was about a month ago, from memory). > That will show you what the issues are around this. > > It's not completely trivial to come up with a solution that works neatly > in all cases. When somebody comes up with a good patch to do that, it > will be reviewed. > > As a general rule asking "why this hasn't been fixed yet" is a bit of a > pointless question. Everybody is a volunteer. Everybody is welcome to > write a patch to try and fix the root problem. The first patch that > fixes the real problem will be committed. That's how open source > development works. Unsurprisingly, we don't sit around saying "who can > we ignore today." > > Regards, > Malcolm > > -- > Two wrongs are only the beginning.http://www.pointy-stick.com/blog/ --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-developers@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-developers?hl=en -~--~~~~--~~--~--~---
Re: some trouble with an older bug
On Sun, 2007-09-02 at 02:49 -0700, Julian wrote: > hi there, > > until now i am very happy with django, but something made me spent > some hours of time with it, i've figured this out: > > http://code.djangoproject.com/ticket/5320 > > wich has an underlying issue: > > http://code.djangoproject.com/ticket/1516 > > wich is obviously not solved yet. it occurrs in a typically situation > (django-application in a subfolder with fastcgi) and isn't very well > documented (not even a little comment in the docs). > > please tell me why noone has it fixed yet and when do you plan to do? Perhaps you could spend a couple of minutes searching the archives -- search for SCRIPT_NAME for example -- to see where this has been discussed before (the last time was about a month ago, from memory). That will show you what the issues are around this. It's not completely trivial to come up with a solution that works neatly in all cases. When somebody comes up with a good patch to do that, it will be reviewed. As a general rule asking "why this hasn't been fixed yet" is a bit of a pointless question. Everybody is a volunteer. Everybody is welcome to write a patch to try and fix the root problem. The first patch that fixes the real problem will be committed. That's how open source development works. Unsurprisingly, we don't sit around saying "who can we ignore today." Regards, Malcolm -- Two wrongs are only the beginning. http://www.pointy-stick.com/blog/ --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-developers@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-developers?hl=en -~--~~~~--~~--~--~---
some trouble with an older bug
hi there, until now i am very happy with django, but something made me spent some hours of time with it, i've figured this out: http://code.djangoproject.com/ticket/5320 wich has an underlying issue: http://code.djangoproject.com/ticket/1516 wich is obviously not solved yet. it occurrs in a typically situation (django-application in a subfolder with fastcgi) and isn't very well documented (not even a little comment in the docs). please tell me why noone has it fixed yet and when do you plan to do? regards julian --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-developers@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-developers?hl=en -~--~~~~--~~--~--~---
