$ python manage.py syncdb
Creating table auth_message
Creating table auth_group
Creating table auth_user
Creating table auth_permission
Creating many-to-many tables for Group model
Creating many-to-many tables for User model
Creating table django_content_type
Creating table django_session
Creating table django_site
You just installed Django's auth system, which means you don't have any
superusers defined.
Would you like to create one now? (yes/no): yes
Username (Leave blank to use 'newpers'):
E-mail address: donts...@gmail.com
Password:
Password (again):
Superuser created successfully.
Adding permission 'Group | Can add Group'
Adding permission 'Group | Can change Group'
Adding permission 'Group | Can delete Group'
Adding permission 'User | Can add User'
Adding permission 'User | Can change User'
Adding permission 'User | Can delete User'
Creating example.com Site object
Adding permission 'site | Can add site'
Adding permission 'site | Can change site'
Adding permission 'site | Can delete site'
Exception exceptions.AttributeError: "'NoneType' object has no
attribute 'print_exc'" in <function remove at 0x2aaaac53bf50> ignored
I've been seeing this at the end of every manage.py command. It does
appear to be non-fatal, but it is something that needs to be debugged.
Sorry I haven't taken the time yet to file a formal report. This was on
my Windows development machine. My uninformed guess is it may be
related to the new color output (ie, I see no color output and instead
this exception).
--
--Max Battcher--
http://www.worldmaker.net/
"I'm gonna win, trust in me / I have come to save this world / and in
the end I'll get the grrrl!" --Machinae Supremacy, Hero (Promo Track)
> Go an error running the following:
>
> $ python manage.py syncdb
[snip]
> Exception exceptions.AttributeError: "'NoneType' object has no
> attribute 'print_exc'" in <function remove at 0x2aaaac53bf50>
> ignored
This is related to this recent thread on this list:
http://tinyurl.com/gdzq3
I believe this is a regression in the PyDispatcher_ code that has been
fixed in, at least, the CVS version.
I just tried updating the .py files in django/dispatch with the latest
from the PyDispatcher CVS. All tests passed for me and I no longer
see any such error messages (which I was seeing as well).
.. _PyDispatcher: http://pydispatcher.sourceforge.net/
Cheers,
+ seth
"svn update" your magic-removal code, and the problem will vanish, as
if by magic!
Adrian
--
Adrian Holovaty
holovaty.com | djangoproject.com