Changes between Initial Version and Version 1 of Ticket #15019


Ignore:
Timestamp:
Jan 5, 2011, 7:55:58 AM (14 years ago)
Author:
Russell Keith-Magee
Comment:

There isn't anywhere near enough detail here to work out if what you're describing is a Django problem, or a problem with your own codebase.

A valid test report gives the triager enough data to reproduce your problem on their own. This report has a stack trace, and a vague description that says you've written your own authentication backend.

Please reopen if you can provide enough detail to reproduce the problem. This means a detailed set of instructions, or a sample project (a *minimal* sample project) that exhibits the problem. Don't just dump your entire codebase on our lap -- do some pruning and cut out anything that isn't *directly* related to the problem at hand.

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #15019

    • Property Resolution → invalid
    • Property Status new → closed

  • Ticket #15019 – Description

    initial v1  
    11I am not using django's built in auth models. Instead I wrote a auth app with a user model of my choice. I wrote my own Authentication middleware and it works fine. However when I run django test suite, django is registering models Permission, Message, Group from django.contrib.auth even though "django.contrib.auth" is not mentioned in INSTALLED_APPS. Here is a indetail trace of the test suite
    22
    3 
     3{{{
    44  /Users/yashh/Desktop/costell/manage.py(11)<module>()
    55-> execute_manager(settings)
    … …  
    6363-> register_models(new_class._meta.app_label, new_class)
    6464> /Library/Python/2.6/site-packages/django/db/models/loading.py(197)register_models()
     65}}}
    6566
    6667The traceback ends when Permission model is passed to register_models
Back to Top