Re: [Django] #17254: ModelBackend should have a get_anonymous_user method

[Django]

#17254: ModelBackend should have a get_anonymous_user method
+--
 Reporter:  riccardodivirgilio  |Owner:  nobody
 Type:  Bug |   Status:  closed
Component:  contrib.auth|  Version:
 Severity:  Normal  |   Resolution:  duplicate
 Keywords:  | Triage Stage:  Unreviewed
Has patch:  0   |  Needs documentation:  0
  Needs tests:  1   |  Patch needs improvement:  0
Easy pickings:  0   |UI/UX:  0
+--

Comment (by anonymous):

 Avoid damaging your hair by brushing it only when it is dry. It's much
 more likely to break if you brush it when it's wet.
 [http://www.wvweightloss.com/smooth-fitness/smooth-fitness-coupon-code-
 april-2012-where-to-get-them/ Smooth Fitness Coupon Code April] To limit
 damage and maintain the health of your hair, hold off brushing until it is
 dry.

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #17254: ModelBackend should have a get_anonymous_user method

[Django]

#17254: ModelBackend should have a get_anonymous_user method
+--
 Reporter:  riccardodivirgilio  |Owner:  nobody
 Type:  Bug |   Status:  closed
Component:  contrib.auth|  Version:
 Severity:  Normal  |   Resolution:  duplicate
 Keywords:  | Triage Stage:  Unreviewed
Has patch:  0   |  Needs documentation:  0
  Needs tests:  1   |  Patch needs improvement:  0
Easy pickings:  0   |UI/UX:  0
+--

Comment (by anonymous):

 It may take a little more effort and distance, but you can save a great
 deal of money over time by using only the ATMs of your bank, credit union,
 or thrift. [http://www.coupons-exclusifs.com/amazon-coupons/amazon-coupon-
 code-free-shipping-2012/ Amazon Free Shipping 2012] Financial institutions
 have heavy monthly and per-transaction fees if you use other ATMs, and
 those can build up fast.

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #17254: ModelBackend should have a get_anonymous_user method

[Django]

#17254: ModelBackend should have a get_anonymous_user method
+--
 Reporter:  riccardodivirgilio  |Owner:  nobody
 Type:  Bug |   Status:  closed
Component:  contrib.auth|  Version:
 Severity:  Normal  |   Resolution:  duplicate
 Keywords:  | Triage Stage:  Unreviewed
Has patch:  0   |  Needs documentation:  0
  Needs tests:  1   |  Patch needs improvement:  0
Easy pickings:  0   |UI/UX:  0
+--

Comment (by anonymous):

 Buying a home can actually save you a lot of money. Of course, you must
 pay your bills and your mortgage monthly; however, once your home is paid
 for, your payments will be done and you have the home as equity. If you're
 just renting you're just paying for something you'll never actually own.
 [http://www.wvweightloss.com/nutrisystem-coupons/nutrisystem-discount-
 code-2012-here-they-all-are/ nutrisystem discount code]

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #17254: ModelBackend should have a get_anonymous_user method

[Django]

#17254: ModelBackend should have a get_anonymous_user method
+--
 Reporter:  riccardodivirgilio  |Owner:  nobody
 Type:  Bug |   Status:  closed
Component:  contrib.auth|  Version:
 Severity:  Normal  |   Resolution:  duplicate
 Keywords:  | Triage Stage:  Unreviewed
Has patch:  0   |  Needs documentation:  0
  Needs tests:  1   |  Patch needs improvement:  0
Easy pickings:  0   |UI/UX:  0
+--

Comment (by anonymous):

 Offer a sitewide search option at the top of every page.
 [http://www.bestreversephonelookupsearch.com/a-list-of-all-the-top-
 reverse-phone-lookup-providers best reverse phone lookup providers]  This
 ensures that all parts of your carefully designed site are always
 accessible to the people that need them. Coding this search functionality
 isn't difficult, so the increase in usability is definitely worth the time
 spent.

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #17254: ModelBackend should have a get_anonymous_user method

[Django]

#17254: ModelBackend should have a get_anonymous_user method
+--
 Reporter:  riccardodivirgilio  |Owner:  nobody
 Type:  Bug |   Status:  closed
Component:  contrib.auth|  Version:
 Severity:  Normal  |   Resolution:  duplicate
 Keywords:  | Triage Stage:  Unreviewed
Has patch:  0   |  Needs documentation:  0
  Needs tests:  1   |  Patch needs improvement:  0
Easy pickings:  0   |UI/UX:  0
+--

Comment (by anonymous):

 It is always a good idea to make sure not to spend more money than you
 earn. People who spend 100% of their income each pay period, or worse,
 110% of their income, never increase their net worth since they are
 spending everything that comes in. [http://www.wvweightloss.com/smooth-
 fitness/smooth-fitness-elliptical-machines-save-with-these-coupon-codes/
 Smooth Fitness Elliptical Machine coupon] Your income should always exceed
 your expenses.

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #17254: ModelBackend should have a get_anonymous_user method

[Django]

#17254: ModelBackend should have a get_anonymous_user method
+--
 Reporter:  riccardodivirgilio  |Owner:  nobody
 Type:  Bug |   Status:  closed
Component:  contrib.auth|  Version:
 Severity:  Normal  |   Resolution:  duplicate
 Keywords:  | Triage Stage:  Unreviewed
Has patch:  0   |  Needs documentation:  0
  Needs tests:  1   |  Patch needs improvement:  0
Easy pickings:  0   |UI/UX:  0
+--

Comment (by anonymous):

 Slather your feet with petroleum jelly at bedtime, put on a pair of socks,
 and go to sleep. [http://www.bestreversephonelookupsearch.com/how-to-make-
 use-800-reverse-phone-lookup-services 800 reverse phone ] By the time you
 wake up the next day, your feet should already feel softer.

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #17254: ModelBackend should have a get_anonymous_user method

[Django]

#17254: ModelBackend should have a get_anonymous_user method
+--
 Reporter:  riccardodivirgilio  |Owner:  nobody
 Type:  Bug |   Status:  closed
Component:  contrib.auth|  Version:
 Severity:  Normal  |   Resolution:  duplicate
 Keywords:  | Triage Stage:  Unreviewed
Has patch:  0   |  Needs documentation:  0
  Needs tests:  1   |  Patch needs improvement:  0
Easy pickings:  0   |UI/UX:  0
+--

Comment (by anonymous):

 Choose foods from all of the colors of the rainbow! Veggies and fruits
 which are brightly colored are very healthy and low in calories.
 [http://www.weightlosswithsupport.com/nutrisystem-discount-code
 /nutrisystem-discount-code-april-2012-get-yours-now/ nutrisystem discount
 code]  Make sure that you always include a selection of fruits or
 vegetables on your plate. If the skins are edible, make sure to eat those
 too, since many of the antioxidant benefits are in the skins.

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #17254: ModelBackend should have a get_anonymous_user method

[Django]

#17254: ModelBackend should have a get_anonymous_user method
+--
 Reporter:  riccardodivirgilio  |Owner:  nobody
 Type:  Bug |   Status:  closed
Component:  contrib.auth|  Version:
 Severity:  Normal  |   Resolution:  duplicate
 Keywords:  | Triage Stage:  Unreviewed
Has patch:  0   |  Needs documentation:  0
  Needs tests:  1   |  Patch needs improvement:  0
Easy pickings:  0   |UI/UX:  0
+--
Changes (by aaugustin):

 * status:  reopened => closed
 * resolution:   => duplicate


Comment:

 I confirm that introducing a customizable User, Permission, or
 !AnonymousUser model is in the realm of #3011. Some comments on that
 ticket discuss !AnonymousUser specifically.

 The fact that #3011 is still open means that the community agrees that
 Django should let developers use a custom class instead of User and
 !AnonymousUser, and possibly customize other parts of
 `django.contrib.auth`. We just haven't figured out a complete solution
 without unacceptable drawbacks yet.

 On a side note, please upload patches in unified diff format (that's what
 `svn diff` or `diff -u` produces) — it's much easier to read in Trac.

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #17254: ModelBackend should have a get_anonymous_user method

[Django]

#17254: ModelBackend should have a get_anonymous_user method
+--
 Reporter:  riccardodivirgilio  |Owner:  nobody
 Type:  Bug |   Status:  reopened
Component:  contrib.auth|  Version:
 Severity:  Normal  |   Resolution:
 Keywords:  | Triage Stage:  Unreviewed
Has patch:  0   |  Needs documentation:  0
  Needs tests:  1   |  Patch needs improvement:  0
Easy pickings:  0   |UI/UX:  0
+--

Comment (by riccardodivirgilio):

 i've attached a .diff

 the only thing to do then is to change django.contrib.auth.get_user and
 instead of import directly AnonimousUser return the anonymous user class
 defined inside the backend.

 this change have got no compatibility problems for any running django
 application, but can save a lot of problems to django developers in the
 future.

 trust me, because i've got a lot of problems for this small issue. i've to
 write a lot of functions, a lot of getattr, a lot of hasattr, and this is
 not clean and not readable.

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #17254: ModelBackend should have a get_anonymous_user method

[Django]

#17254: ModelBackend should have a get_anonymous_user method
+--
 Reporter:  riccardodivirgilio  |Owner:  nobody
 Type:  Bug |   Status:  reopened
Component:  contrib.auth|  Version:
 Severity:  Normal  |   Resolution:
 Keywords:  | Triage Stage:  Unreviewed
Has patch:  0   |  Needs documentation:  0
  Needs tests:  1   |  Patch needs improvement:  0
Easy pickings:  0   |UI/UX:  0
+--
Changes (by riccardodivirgilio):

 * status:  closed => reopened
 * resolution:  duplicate =>


Comment:

 this is what i have done.

 maybe you have missed the point. this is not about my application, or the
 way i found to hack this lack, you asked me for an example.

 the point is that this is not a real backend.

 the current django behavior is to permit a developer to create a custom
 user class, but the middleware do not pass the same class if the user in
 unauthenticated.

 according to me, in a running application, it's a mess to have to
 different kind of classes, depending if the user is authenticated or not.

 i'm not here to ask django to solve my problems, i'm are to solve django
 problems, because my application is alive and running, i'm only
 contributing for an issue, that (according to me) it's big for deploying a
 custom user backend.

 in an object-driving application, i don't see why i have to write function
 and put a lot of time getattr(user, "foo") or hasattr(user, "foo"),
 because it's my app and in my app user has foo attribute, because i have
 decided that is required, so in this login even the Unauthenticated user
 must have a foo attribute.

 django it's a framework, not an application, developers must be able to
 decide which field user class must have, and with the current backend
 developers cannot do that.

 please read the backend.py i have attached, it's better to have an
 attribute in the class and call it using something like
 "self.user_model.objects.get()" for the same reason inside the ModelAdmin
 you call self.model and not directly the model itself.

 whit this simple approach a developer can set a custom user class and a
 permission backend but it's still able to use all views and urls without
 any hack.

 please, read the code, they are just a few line of code that can save a
 lot of problems.

 my question is why do you want to set AnoninmousUser as request.user,
 instead of let developers choose to use django class or a custom class?
 why?

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #17254: ModelBackend should have a get_anonymous_user method

[Django]

#17254: ModelBackend should have a get_anonymous_user method
+--
 Reporter:  riccardodivirgilio  |Owner:  nobody
 Type:  Bug |   Status:  closed
Component:  contrib.auth|  Version:
 Severity:  Normal  |   Resolution:  duplicate
 Keywords:  | Triage Stage:  Unreviewed
Has patch:  0   |  Needs documentation:  0
  Needs tests:  1   |  Patch needs improvement:  0
Easy pickings:  0   |UI/UX:  0
+--
Changes (by ptone):

 * status:  reopened => closed
 * resolution:   => duplicate


Comment:

 This is basically a dupe of #3011

 see also: http://stackoverflow.com/questions/896421/how-to-change-default-
 django-user-model-to-fit-my-needs

 AnonUsers and AuthUsers are fundamentally different in having a DB
 instance.

 You may find it easier to write a util method that takes a user
 user_has_discount(request.user) then factor all your checking into that

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #17254: ModelBackend should have a get_anonymous_user method

[Django]

#17254: ModelBackend should have a get_anonymous_user method
+--
 Reporter:  riccardodivirgilio  |Owner:  nobody
 Type:  Bug |   Status:  reopened
Component:  contrib.auth|  Version:
 Severity:  Normal  |   Resolution:
 Keywords:  | Triage Stage:  Unreviewed
Has patch:  0   |  Needs documentation:  0
  Needs tests:  1   |  Patch needs improvement:  0
Easy pickings:  0   |UI/UX:  0
+--
Changes (by ptone):

 * status:  closed => reopened
 * resolution:  needsinfo =>


Comment:

 reopening to change resolution

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #17254: ModelBackend should have a get_anonymous_user method

[Django]

#17254: ModelBackend should have a get_anonymous_user method
+--
 Reporter:  riccardodivirgilio  |Owner:  nobody
 Type:  Bug |   Status:  closed
Component:  contrib.auth|  Version:
 Severity:  Normal  |   Resolution:  needsinfo
 Keywords:  | Triage Stage:  Unreviewed
Has patch:  0   |  Needs documentation:  0
  Needs tests:  1   |  Patch needs improvement:  0
Easy pickings:  0   |UI/UX:  0
+--
Changes (by anonymous):

 * needs_tests:  0 => 1


-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #17254: ModelBackend should have a get_anonymous_user method

[Django]

#17254: ModelBackend should have a get_anonymous_user method
+--
 Reporter:  riccardodivirgilio  |Owner:  nobody
 Type:  Bug |   Status:  closed
Component:  contrib.auth|  Version:
 Severity:  Normal  |   Resolution:  needsinfo
 Keywords:  | Triage Stage:  Unreviewed
Has patch:  0   |  Needs documentation:  0
  Needs tests:  0   |  Patch needs improvement:  0
Easy pickings:  0   |UI/UX:  0
+--

Comment (by anonymous):

 with this implementation of backend i can do something like this
 do not use "django.contrib.auth" in the INSTALLED_APP, but use
 "myapp.auth" to define User class and Permission class (with duck type mot
 hod of django class) and still use django.contrib.auth.urls and
 django.contrib.middleware.AuthenticationMiddleware, and everything works
 (with a different user and permission db_table)

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #17254: ModelBackend should have a get_anonymous_user method

[Django]

#17254: ModelBackend should have a get_anonymous_user method
+--
 Reporter:  riccardodivirgilio  |Owner:  nobody
 Type:  Bug |   Status:  closed
Component:  contrib.auth|  Version:
 Severity:  Normal  |   Resolution:  needsinfo
 Keywords:  | Triage Stage:  Unreviewed
Has patch:  0   |  Needs documentation:  0
  Needs tests:  0   |  Patch needs improvement:  0
Easy pickings:  0   |UI/UX:  0
+--

Comment (by riccardodivirgilio):

 sorry for my english, i'm italian and i just woke up... yesterday i was
 drunk so sorry

 but read the backends.py for me it's much more customizable in the way i
 wrote...
 the methods inside the backend use self.user_class.objects.get to get an
 user, instead of doing User.objects.get
 i added a get_anonymous_user to get a fresh instance of AnonymousUser,
 this method must be used by the middleware
 for me doing an import such "from django.contrib.auth.models import
 AnonymousUser" and then call directly AnonymousUser(), it'wrong, because
 if you do something like this, i have to rewrite more code to make
 login/logout and middleware work the way i need.

 the way i wrote the backend, to subclass it you simply need to hook your
 user model and your anonimoususer class, and django will do the dirty of
 work of login, logout, password change and so on.

 bye bye, my django friends!

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #17254: ModelBackend should have a get_anonymous_user method

[Django]

#17254: ModelBackend should have a get_anonymous_user method
+--
 Reporter:  riccardodivirgilio  |Owner:  nobody
 Type:  Bug |   Status:  closed
Component:  contrib.auth|  Version:
 Severity:  Normal  |   Resolution:  needsinfo
 Keywords:  | Triage Stage:  Unreviewed
Has patch:  0   |  Needs documentation:  0
  Needs tests:  0   |  Patch needs improvement:  0
Easy pickings:  0   |UI/UX:  0
+--

Comment (by anonymous):

 when you subclass the user, i would like to subclass even the
 AnonymousUser in request to check the user attributes without using
 getattr, or define custom methods, even for an AnonymousUser user.

 for example, i have got a field that is called "user_discount" and i have
 got a method that return the final price of the user.

 i use this method a lot of time in the site, because it's an commerce, and
 it's useful to do request.user.dicounted_price("120") without doing a mess
 like this get_discounted_price_from_user(user, 120), and using a function
 and not a class, and in every part of my code i have to check if user
 is_authenticated before using custom method of my user class.

 for me an AnonymousUser, should be a subclass of the user class, but it
 must be declared importing the user class from the backend and then
 subclassing it.

 i've a attached a new backend file,

 this is an easy way to allow developers to completely use another User and
 Permission backend using 3 line of code (read the backends.py i've
 attached)

 class MyModelBackend(ModelBackend):

 user_class = MyUser
 permission_class = MyPermission
 anonymoususer_class = MyAnonymousUser

 with this class i can set my own model table for existing legacy user and
 permission, without rewrite login, logout, password_change and so on...

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #17254: ModelBackend should have a get_anonymous_user method

[Django]

#17254: ModelBackend should have a get_anonymous_user method
+--
 Reporter:  riccardodivirgilio  |Owner:  nobody
 Type:  Bug |   Status:  closed
Component:  contrib.auth|  Version:
 Severity:  Normal  |   Resolution:  needsinfo
 Keywords:  | Triage Stage:  Unreviewed
Has patch:  0   |  Needs documentation:  0
  Needs tests:  0   |  Patch needs improvement:  0
Easy pickings:  0   |UI/UX:  0
+--
Changes (by ptone):

 * status:  new => closed
 * resolution:   => needsinfo


Comment:

 Please provide a use case, or argument about how the current
 implementation is problematic.

 Are you attaching stuff to the user instead of just the session?

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #17254: ModelBackend should have a get_anonymous_user method

[Django]

#17254: ModelBackend should have a get_anonymous_user method
+--
 Reporter:  riccardodivirgilio  |Owner:  nobody
 Type:  Bug |   Status:  new
Component:  contrib.auth|  Version:
 Severity:  Normal  |   Resolution:
 Keywords:  | Triage Stage:  Unreviewed
Has patch:  0   |  Needs documentation:  0
  Needs tests:  0   |  Patch needs improvement:  0
Easy pickings:  0   |UI/UX:  0
+--
Changes (by David Danier ):

 * needs_better_patch:   => 0
 * needs_tests:   => 0
 * needs_docs:   => 0


Comment:

 Why do you want this? Guest accounts in the database?

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

[Django] #17254: ModelBackend should have a get_anonymous_user method

[Django]

#17254: ModelBackend should have a get_anonymous_user method
+
 Reporter:  riccardodivirgilio  |  Owner:  nobody
 Type:  Bug | Status:  new
Component:  contrib.auth|Version:
 Severity:  Normal  |   Keywords:
 Triage Stage:  Unreviewed  |  Has patch:  0
Easy pickings:  0   |  UI/UX:  0
+
 ModelBackend should provide a method to get a fresh instance of
 AnonymousUser, and use this method to set a new instance of AnonymousUser
 in

 django.contrib.auth.get_user and django.contrib.auth.logout

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.