This doesn't need to be fixed, but it's possible to make the tasks app
trigger an impossible branch in the generic django contenttypes code
by by including tasks/urls.py in a site urls.py, e.g.
urlpatterns += patterns('',(r'^groupapp/',
include('groupapp.urls')))
or
urlpatterns += patterns('',(r'^tasks/',
include('groupapp.urls')))
where groupapp is just tasks refactored in name only. Here's the
relevant django error message:
Exception at /tasks/add/
Impossible arguments to GFK.get_content_type!
* /home/hobs/srcsite/../srcsite/groupapp/views.py in add_task
147. task.group = group ...
...
* /home/hobs/srcsite-env/lib/python2.6/site-packages/django/
contrib/contenttypes/generic.py in get_content_type
57. # This should never happen. I love comments like this,
don't you?
58. raise Exception("Impossible arguments to
GFK.get_content_type!") ...
I'll sort it out by unrefactoring and double checking that tasks can
still work independently of the projects app if urlpatterned properly.
Incidentally, if anyone has read this far, I'd be happy to send them
the bash scripts that automatically install, refactor, and runs a
"groupapp" derived from pinax.apps.tasks from the pinax/pinax/master
branch on github. A pull request for shell scripts didn't seem
appropriate, especially considering this remaining "feature" of the
autocode that the script spits out. But it might be helpful in
generating documentation and example code.
--
You received this message because you are subscribed to the Google Groups
"Pinax Core Development" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/pinax-core-dev?hl=en.
