Running unit test based on example tests.py not working

[social@…]

Hello,

I'm pretty new to Django and exploring all the features it provides. Whenever I try to run the example tests.py file distributed with any new app created (e.g. python manage.py startapp polls, s. tutorial for Django 1.3), the process never ends and Python has a CPU load of 99%.

Database connectivity (based on MySQL) is working as I have run python manage.py syncdb successfully.

Here's the output when running the unit test:

tte@arbre:/www/sites/mysite$ python manage.py test
Creating test database for alias 'default'...
.......................................................................................

Although the test database is created and the database user should have all the right permissions, the process never completes.

I'm using Python 2.7 (built with MacPorts).

Is there anything I'm missing?

Tobi

[Russell Keith-Magee]

Hi Tobi,

I'm going to mark this ticket as worksforme for the moment. I can't reproduce this problem, and I haven't seen anything like it in many years of running Django test suites.

If you want help diagnosing this problem, please ask on the django-users mailing list. Trac isn't a help or support forum -- it's a way for us to track known problems with Django and make sure they get fixed. If the discussion on django-users reveals that something is actually wrong with Django (or that we need to document some special condtion), we can reopen this ticket to track the actual problem.

[anonymous]

Hi russellm,

after further testing I found out that tests actually work using OSX Lion's built-in Python and sqlite3; seems I'll have to take a closer look at my MacPorts toolchain. Thanks for your advise regarding Trac - will consider it next time.

Tobi