On Thu, Nov 19, 2009 at 7:26 PM, Karen Tracey wrote:
>
>
> So I guess you are looking to pull django and satchmo out of
> /var/www/vhosts/hobbygiochi.com/django/, not /var/www/vhosts/
> detectorpoint.com/django/. I'd guess the detectorpoint.com paths are
> already in sys.path when your wsgi scri
On Thu, Nov 19, 2009 at 11:51 AM, Alessandro Ronchi <
alessandro.ron...@soasi.com> wrote:
>
>
> On Thu, Nov 19, 2009 at 5:28 PM, Alessandro Ronchi <
> alessandro.ron...@soasi.com> wrote:
>
>>
>>> Really, you can get both pretty debug pages and emails with mod_wsgi as
>>> well as you can with the d
On Thu, Nov 19, 2009 at 5:28 PM, Alessandro Ronchi <
alessandro.ron...@soasi.com> wrote:
>
>> Really, you can get both pretty debug pages and emails with mod_wsgi as
>> well as you can with the development server or mod_python. I've seen both.
>> The problem with both exception traces you have sh
>
>
> Really, you can get both pretty debug pages and emails with mod_wsgi as
> well as you can with the development server or mod_python. I've seen both.
> The problem with both exception traces you have shown is that the exception
> is occurring too early in the processing -- neither of these ex
On Wed, Nov 18, 2009 at 8:28 PM, Alessandro Ronchi <
alessandro.ron...@soasi.com> wrote:
> I get the same problem also with an Assert False (a typical debug symbol
> I've used with mod_python).
>
> http://dpaste.com/16/
>
> no browser and no email, only logs.
>
>
You seem to have put the asse
On Thu, Nov 19, 2009 at 2:02 AM, Karen Tracey wrote:
> On Wed, Nov 18, 2009 at 7:29 PM, Alessandro Ronchi <
> alessandro.ron...@soasi.com> wrote:
>
>>
>>
>> http://dpaste.com/122205/
>> is my log file.
>>
>>
> Traceback shows it is dying during the load of middleware. You would not
> get a prett
On Wed, Nov 18, 2009 at 7:29 PM, Alessandro Ronchi <
alessandro.ron...@soasi.com> wrote:
>
>
> http://dpaste.com/122205/
> is my log file.
>
>
Traceback shows it is dying during the load of middleware. You would not
get a pretty debug page for this even with DEBUG=True and running the
development
On Thu, Nov 19, 2009 at 1:08 AM, Graham Dumpleton <
graham.dumple...@gmail.com> wrote:
>
>
> On Nov 19, 10:48 am, Alessandro Ronchi
> wrote:
> > With mod_wsgi I only get error logged into apache and not on the
> interactive
> > trackback in the browser, also If i set DEBUG=True in my settings.
>
On Nov 19, 10:48 am, Alessandro Ronchi
wrote:
> With mod_wsgi I only get error logged into apache and not on the interactive
> trackback in the browser, also If i set DEBUG=True in my settings.
>
> Is there any way to handle the django trackback as usual?
Is the error definitely from Django and
On Thu, Nov 19, 2009 at 12:48 AM, Alessandro Ronchi <
alessandro.ron...@soasi.com> wrote:
> With mod_wsgi I only get error logged into apache and not on the
> interactive trackback in the browser, also If i set DEBUG=True in my
> settings.
>
> Is there any way to handle the django trackback as usu
With mod_wsgi I only get error logged into apache and not on the interactive
trackback in the browser, also If i set DEBUG=True in my settings.
Is there any way to handle the django trackback as usual?
--
Alessandro Ronchi
SOASI
Sviluppo Software e Sistemi Open Source
http://www.soasi.com
http:
11 matches
Mail list logo