On Wed, Jan 6, 2010 at 6:12 PM, Pascal Vincent wrote:
> I'm reposting this question here, since I didn't get any answer the
> first time, and I'm struck there.
> Where can I find help with this, should I rather post the problem to
> another group?
>
> ---
> I'm new to django, and was going through the tutorial (on Mac Os X
> 10.4.11, installed latest stable version from tarball).
> All seems to go well, and I can access the local site until I enter
> the damin login and passwd and submit.
> After that the development server program just exits without notice.
> (and the client browser then obviously can't get any connection to
> it).
>
> I've traced this back to autoreload.py line 96
> which reads: sys.exit(restart_with_reloader())
> Any idea what is going (or what I am doing) wrong here?
>
>
I've never seen this nor recall hearing of it being reported before so have
no idea what is going on. You've not tracked it down far enough to point to
where the problem is. That line is not the problem. Note it calls, before
exiting, restart_with_reloader(). The question that needs to be answered now
is why does restart_with_reloader() return when you login? Something weird
is apparently happening that is causing the process to terminate with an
unexpected return code (not the one that signals code has changed and causes
restart_with_reloader() to just start a new process).
I suspect you might have more success tracking down what is going on by
tracing through in a debugger the processing that happens during login. I'm
not sure you're going to be able to get much more out of the code you're
looking at now than "hmm, the dev server process terminated with an
unexpected exit code".
You might try running the dev server with the --noreload option and seeing
if you get any better indication of the failure that way, though I don't
know why you would get more output from that case. But maybe it'll be
easier to track down without the code that does the
auto-reload-on-code-change.
I do recall that some Pythons on Macs seem to behave relatively badly for
error situations such as infinite recursion. Instead of a traceback
identifying the problem you might get a process termination with core dump
on Macs. You might be running into some sort of problem like that, where
the Python interpreter is just terminating unexpectedly.
Karen
--
You received this message because you are subscribed to the Google Groups "Django users" group.
To post to this group, send email to django-us...@googlegroups.com.
To unsubscribe from this group, send email to django-users+unsubscr...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/django-users?hl=en.
