This sounds like a good idea, and if everyone else is doing it...
It might also make #2407 cleaner (CGI Support)- some of the comments
there are stating that you need to load PATH_INFO etc into the env to
get it running properly.
http://code.djangoproject.com/ticket/2407#comment:14
--Simon
-
On 3/11/07, Max Battcher <[EMAIL PROTECTED]> wrote:
> Anyway, I think my suggestion is that in this particular case maybe
> the better approach is to push for better genericity in the Comments
> app (particularly as it gets rewritten and better documented)...
I've done that, actually :)
Right no
On 3/11/07, James Bennett <[EMAIL PROTECTED]> wrote:
>
> On 3/11/07, Malcolm Tredinnick <[EMAIL PROTECTED]> wrote:
> > [Insert standard rant about components intended to be reusable that do
> > not provide an alternative way to specify the environment. Makes testing
> > kind if hard. Their develop
On 3/11/07, Malcolm Tredinnick <[EMAIL PROTECTED]> wrote:
> [Insert standard rant about components intended to be reusable that do
> not provide an alternative way to specify the environment. Makes testing
> kind if hard. Their developers are probably cruel to small animals as
> well.]
:)
In thi
On Sat, 2007-03-10 at 20:53 -0600, James Bennett wrote:
> While working on a small personal project I've run into a bit of a
> wall because I'd like to use a third-party module which looks for
> information about HTTP requests. It doesn't know (and shouldn't need
> to know) about Django's HttpRequ
While working on a small personal project I've run into a bit of a
wall because I'd like to use a third-party module which looks for
information about HTTP requests. It doesn't know (and shouldn't need
to know) about Django's HttpRequest object, and simply looks for the
things it wants in os.envir
