fwiw, the user error in question was that a developer had added a call to threading outside of any function definition or protected area. as such the manage.py process finished, but the thread was left hanging.
On Jul 21, 6:16 pm, "psgou...@gmail.com" <psgou...@gmail.com> wrote: > I've seen a few references to something like this happening, but > nothing quite right. > > somewhere along the line, I have become unable to run manage.py and > have it exit cleanly. it will appear to do everything that it is > supposed to do. (with exceptions,) and then hang. > > for example, > in mysql, create the database needed, > in the app folder, execute 'python manage.py syncdb --noinput -v 2' > > according to the verbose output, all the tables are created, there is > a section looking for fixtures, ending with the line: > No fixtures found. > > which would seem to indicate that it's getting through almost > everything and dying right at the end of it all. > > however, it will not return. and I am forced to kill the python > process manually. after restarting apache, the app will operate as > expected, indicating (it would seem) that the problem is largely > cosmetic. > > now, at one point this was working. and the command output ended with > the same line, but it would return. > > nothing obvious in the actual app code seems like it would cause this > problem. can anyone suggest anything likely? when syncdb executes is > there anything known that would trip it up based on the contents of > the app being synced? > > cheers -- 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.
