Re: [Django] #5833: Custom FilterSpecs

[Django]

#5833: Custom FilterSpecs
---+
  Reporter:  Honza_Kral| Owner:  jkocherhans
 
Status:  assigned  | Milestone:  1.2
 
 Component:  django.contrib.admin  |   Version:  SVN
 
Resolution:|  Keywords:  nfa-someday 
list_filter filterspec nfa-changelist ep2008
 Stage:  Accepted  | Has_patch:  1  
 
Needs_docs:  1 |   Needs_tests:  1  
 
Needs_better_patch:  0 |  
---+
Comment (by sciyoshi):

 The validation in the latest patch is broken. Attaching a new version
 against 1.1/SVN which also fixes #11771.

-- 
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] #11771: Support filtering by non-database (queryset) fields in the admin

[Django]

#11771: Support filtering by non-database (queryset) fields in the admin
--+-
 Reporter:  sciyoshi  |   Owner:  
nobody
   Status:  new   |   Milestone:

Component:  django.contrib.admin  | Version:  SVN   

 Keywords:  admin, filtering, filter, filterspec, fields  |   Stage:  
Unreviewed
Has_patch:  1 |  
--+-
 It's currently impossible to filter the admin interface by non-database
 fields, even if the fields are being selected in the queryset.

 The attached patch lets you do something like this:

 {{{
 class Author(models.Model):
 name = models.CharField(max_length=255)

 class Book(models.Model):
 author = models.ForeignKey(Author)

 class AuthorAdmin(admin.ModelAdmin):
 list_display = ['name', 'books']
 list_filter = [models.IntegerField(verbose_name='number of books',
 name='num_books')]

 def books(self, obj):
 return obj.num_books
 books.short_description = 'Number of books'

 def queryset(self, request):
 return super(AuthorAdmin,
 self).queryset(request).annotate(num_books=models.Count('book'))

 admin.site.register(Author, AuthorAdmin)
 admin.site.register(Book)
 }}}

 which would show all of the values for num_books in the available filters.
 (This particular example only works in MySQL, but could be applied to
 fields selected with .extra(select=...) instead of .annotate).

-- 
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] #342: Add a way for fields to be displayed in the admin without being editable

[Django]

#342: Add a way for fields to be displayed in the admin without being editable
---+
  Reporter:  Bless | Owner:  nobody
Status:  reopened  | Milestone:  1.2   
 Component:  django.contrib.admin  |   Version:  newforms-admin
Resolution:|  Keywords:  djangocon 
 Stage:  Accepted  | Has_patch:  0 
Needs_docs:  0 |   Needs_tests:  0 
Needs_better_patch:  0 |  
---+
Changes (by joshuajonah):

 * cc: j...@joshuajonah.com (added)

-- 
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] #5833: Custom FilterSpecs

[Django]

#5833: Custom FilterSpecs
---+
  Reporter:  Honza_Kral| Owner:  jkocherhans
 
Status:  assigned  | Milestone:  1.2
 
 Component:  django.contrib.admin  |   Version:  SVN
 
Resolution:|  Keywords:  nfa-someday 
list_filter filterspec nfa-changelist ep2008
 Stage:  Accepted  | Has_patch:  1  
 
Needs_docs:  1 |   Needs_tests:  1  
 
Needs_better_patch:  0 |  
---+
Changes (by anonymous):

 * cc: sciyo...@gmail.com (added)

-- 
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] #11770: Allow login_required to specify login_url like user_passes_test

[Django]

#11770: Allow login_required to specify login_url like user_passes_test
-+--
  Reporter:  anonymous   | Owner:  nobody
Status:  new | Milestone:
 Component:  Authentication  |   Version:  SVN   
Resolution:  |  Keywords:  login auth
 Stage:  Design decision needed  | Has_patch:  1 
Needs_docs:  0   |   Needs_tests:  0 
Needs_better_patch:  0   |  
-+--
Changes (by Mnewman):

  * needs_better_patch:  => 0
  * component:  Uncategorized => Authentication
  * needs_tests:  => 0
  * summary:  Allow login_required to specify a custom login_url => Allow
  login_required to specify login_url like
  user_passes_test
  * version:  1.1 => SVN
  * needs_docs:  => 0
  * has_patch:  0 => 1
  * stage:  Unreviewed => Design decision needed

Comment:

 This is interesting and pretty trivial IMO. Marking DDN and putting a
 patch up that I think accomplishes this right and changes the docs. Also
 adds the other part of the docs for user_passes_test and changes absolute
 URL to absolute path, both of which should probably be their own tickets.

-- 
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] #11770: Allow login_required to specify a custom login_url

[Django]

#11770: Allow login_required to specify a custom login_url
---+
 Reporter:  anonymous  |   Owner:  nobody
   Status:  new|   Milestone:
Component:  Uncategorized  | Version:  1.1   
 Keywords:  login auth |   Stage:  Unreviewed
Has_patch:  0  |  
---+
 All up to '''login_required''' Django allows one to specify a custom
 '''login_url''' when the user is not actually logged in.

 However, login_required omits this parameter when calling
 '''user_passes_test''' and thus forces me to rewrite that piece of code to
 do that. I think it would be a simple and probably backwards-compatible
 change to add an optional parameter to override the '''login_url''' even
 in '''login_required'''.

-- 
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] #6138: newforms: when accessing directly form.errors, error_class is not used

[Django]

#6138: newforms: when accessing directly form.errors, error_class is not used
---+
  Reporter:  Michal Moroz  | Owner:  peter2108
Status:  new   | Milestone:   
 Component:  Forms |   Version:  SVN  
Resolution:|  Keywords:   
 Stage:  Accepted  | Has_patch:  1
Needs_docs:  0 |   Needs_tests:  0
Needs_better_patch:  0 |  
---+
Comment (by peter2108):

 Replying to [comment:15 Alex]:
 > Please put the tests in the same diff as the patch itself, it is
 possible to use svn add locally.

 I'm afraid I don't understand this. Can you explain or point me to an
 example patch.

-- 
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] #5416: Add assertNumQueries() to testing framework

[Django]

#5416: Add assertNumQueries() to testing framework
+---
  Reporter:  adrian | Owner:  alexkoshelev   
Status:  assigned   | Milestone: 
 Component:  Testing framework  |   Version:  SVN
Resolution: |  Keywords:  feature_request
 Stage:  Accepted   | Has_patch:  1  
Needs_docs:  0  |   Needs_tests:  0  
Needs_better_patch:  0  |  
+---
Changes (by alexkoshelev):

 * cc: alexkoshelev (added)
  * owner:  kkubasik => alexkoshelev
  * status:  new => assigned

-- 
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] #11768: Localflavor for Venezuela

[Django]

#11768: Localflavor for Venezuela
-+--
  Reporter:  marcoslhc   | Owner:  nobody   
Status:  new | Milestone:   
 Component:  django.contrib.localflavor  |   Version:  1.1  
Resolution:  |  Keywords:  Venezuela
 Stage:  Accepted| Has_patch:  1
Needs_docs:  0   |   Needs_tests:  1
Needs_better_patch:  1   |  
-+--
Comment (by marcoslhc):

 Replying to [comment:2 Alex]:
 > Please provide all files as a single diff from the root of the Django
 source tree.  Also, I noticed you forgot to upload the tests.
 Sorry. I'm new to django, and to contribute code at all :). I understand I
 need a Commit access to upload the code. Thanks.

-- 
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] #5416: Add assertNumQueries() to testing framework

[Django]

#5416: Add assertNumQueries() to testing framework
+---
  Reporter:  adrian | Owner:  kkubasik   
Status:  new| Milestone: 
 Component:  Testing framework  |   Version:  SVN
Resolution: |  Keywords:  feature_request
 Stage:  Accepted   | Has_patch:  1  
Needs_docs:  0  |   Needs_tests:  0  
Needs_better_patch:  0  |  
+---
Comment (by russellm):

 @Manoj - thanks for the patch, but I'm not sure this the right way to
 address the problem.

  * Your patch requires enabling settings.DEBUG - an action that can have
 unintended (and potentially query induing) consequences.
  * Your patch only works when wrapping a single callable. It's not
 something you could easily deploy in a test case, where you may want to do
 a query count check at several points in a complex test case. It also
 precludes (or makes impractical) the testing of a function that has side
 effects (so it can't be run twice) but also requires other test
 assertions.

 As noted in the ticket comments, the preferred solution is to introduce a
 signal (vis #5415) and use that signal as the basis for logging the number
 of queries. This would allow logging regardless of the value of
 settings.DEBUG. The query count could be cleared at the test setUp; the
 assertion then validates that the callback has been invoked the right
 number of times. This would allow for checking the query count without the
 need to use callable wrapping.

 There have been some recent Django-dev discussion about query logging, and
 the use of signals for this purpose was raised. It may be worth getting
 involved in this discussion if you're interested in pursuing this idea.

-- 
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] #11627: Allow users to run individual test suites using manage.py

[Django]

#11627: Allow users to run individual test suites using manage.py
-+--
  Reporter:  Manoj Govindan   | Owner:  
gruszczy
Status:  new | Milestone:   
   
 Component:  Testing framework   |   Version:  SVN  
   
Resolution:  |  Keywords:   
   
 Stage:  Accepted| Has_patch:  0
   
Needs_docs:  0   |   Needs_tests:  0
   
Needs_better_patch:  1   |  
-+--
Changes (by gruszczy):

  * needs_better_patch:  0 => 1

Comment:

 I have discussed the case with Russel and I will try to provide a better
 patch in a few days.

-- 
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] #9656: Inherit user's password change link doesn't work

[Django]

#9656: Inherit user's password change link doesn't work
---+
  Reporter:  syabro| Owner:  nobody
Status:  reopened  | Milestone:  1.1   
 Component:  django.contrib.admin  |   Version:  1.0   
Resolution:|  Keywords:
 Stage:  Accepted  | Has_patch:  0 
Needs_docs:  0 |   Needs_tests:  0 
Needs_better_patch:  0 |  
---+
Changes (by AdamTwiss):

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

Comment:

 I keep encountering the same problem as per this original ticket.
 Subclassing from UserAdmin doesn't itself fix it.

 My code is:
 models.py:
 {{{
 class Player( User ):
 # Other stuff snipped
 objects = UserManager()
 }}}

 Using Django 1.1 (or 1.02)

 If I just do this, then the change_password link is broken as described.
 If I then set the admin

 admin.py:
 {{{
 class PlayerAdmin( UserAdmin ):
 pass
 admin.site.register(Player, PlayerAdmin )
 }}}

 Then at this point adding a Player in the admin interface just creates a
 User when added, and shows an error of:
 http://localhost:8000/admin/website/player/4/

 To get it to work I need to extend admin.py to do a minimum of:

 {{{
 from django.contrib.auth.admin import UserAdmin
 from django.contrib.auth.forms import UserCreationForm
 from django.utils.translation import ugettext, ugettext_lazy as _

 class PlayerAddForm( UserCreationForm ):
 class Meta:
 model = Player
 fields = ("username","first_name", "last_name" )
 def __init__(self, *args, **kwargs):
 return super(PlayerAddForm,self).__init__( *args,
 **kwargs)


 class PlayerAdminForm(forms.ModelForm):
 class Meta:
 model = Player
 password = forms.CharField( help_text=_("Use
 '[algo]$[salt]$[hexdigest]' or use the change
 password form."))


 class PlayerAdmin( UserAdmin ):
 form = PlayerAdminForm
 add_form = PlayerAddForm

 admin.site.register(Player, PlayerAdmin )
 }}}

 The fact that this is undocumented and it's taken me a while to figure it
 out is to me a bug in itself.

 If the 'correct' thing to do now is to extend the Auth.User class (rather
 than user user_profile), then I also think this should be made easier in
 some way as it's less than obvious and lacks the djangoesque simplicity.

-- 
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] #11763: Admin Interface - Login - Security Concern

[Django]

#11763: Admin Interface - Login - Security Concern
-+--
  Reporter:  AmirHabibi  | Owner:  nobody
Status:  closed  | Milestone:
 Component:  Authentication  |   Version:  1.1   
Resolution:  invalid |  Keywords:  Login Security
 Stage:  Unreviewed  | Has_patch:  0 
Needs_docs:  0   |   Needs_tests:  0 
Needs_better_patch:  0   |  
-+--
Changes (by ubernostrum):

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

Comment:

 Not a bug.

-- 
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] #11769: Include tag with insert code blocks

[Django]

#11769: Include tag with insert code blocks
--+-
  Reporter:  Stacky   | Owner:  nobody
Status:  closed   | Milestone:  1.2   
 Component:  Template system  |   Version:  1.1   
Resolution:  invalid  |  Keywords:
 Stage:  Unreviewed   | Has_patch:  0 
Needs_docs:  0|   Needs_tests:  0 
Needs_better_patch:  0|  
--+-
Changes (by ubernostrum):

  * status:  new => closed
  * needs_better_patch:  => 0
  * resolution:  => invalid
  * needs_tests:  => 0
  * needs_docs:  => 0

Comment:

 This is a bug tracker, not a how-to forum.

-- 
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] #11763: Admin Interface - Login - Security Concern

[Django]

#11763: Admin Interface - Login - Security Concern
-+--
  Reporter:  AmirHabibi  | Owner:  nobody
Status:  new | Milestone:
 Component:  Authentication  |   Version:  1.1   
Resolution:  |  Keywords:  Login Security
 Stage:  Unreviewed  | Has_patch:  0 
Needs_docs:  0   |   Needs_tests:  0 
Needs_better_patch:  0   |  
-+--
Changes (by JohnDoe):

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

Comment:

 You can just set SESSION_EXPIRE_AT_BROWSER_CLOSE true or change some other
 session related settings? What you want here is to have an additional
 session system for the admin interface.

-- 
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] #11769: Include tag with insert code blocks

[Django]

#11769: Include tag with insert code blocks
-+--
 Reporter:  Stacky   |   Owner:  nobody
   Status:  new  |   Milestone:  1.2   
Component:  Template system  | Version:  1.1   
 Keywords:   |   Stage:  Unreviewed
Has_patch:  0|  
-+--
 What with this usecase? How to implement something like this?

 {{{

 {% template "some/template.htm" %}
{% content top %}some html{% endcontent %}
{% content bottom %}some html{% endcontent %}
 {% endtemplate %}

 some/template.htm>>

 html

 {% content top %}{% endcontent %}

 html

 {% content bottom %}{% endcontent %}

 html
 }}}

-- 
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] #5246: MS SQL Server backend using pyodbc.

[Django]

#5246: MS SQL Server backend using pyodbc.
+---
  Reporter:  Filip Wasilewski   | 
Owner:  nobody   
Status:  closed | 
Milestone:   
 Component:  Database layer (models, ORM)   |   
Version:  SVN  
Resolution:  invalid|  
Keywords:  mssql pyodbc database backend feature
 Stage:  Design decision needed | 
Has_patch:  1
Needs_docs:  0  |   
Needs_tests:  0
Needs_better_patch:  0  |  
+---
Comment (by nikecitycn):

 [http://www.sneakersupplier.com Nike air force ones]
 [http://www.sneakersupplier.com Air Jordan shoes]
 [http://www.sneakersupplier.com Nike Dunks]
 [http://www.sneakersupplier.com Nike Shox]
 [http://www.sneakersupplier.com Nike Shoes]

-- 
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] #4186: [boulder-oracle] Error using "SELECT DISTINCT" with TextFields

[Django]

#4186: [boulder-oracle] Error using "SELECT DISTINCT" with TextFields
---+
  Reporter:  khoo...@westnet.com.au| Owner:  nobody 

Status:  new   | Milestone: 

 Component:  Database layer (models, ORM)  |   Version:  SVN

Resolution:|  Keywords:  oracle 
distinct NCLOB TextField
 Stage:  Accepted  | Has_patch:  0  

Needs_docs:  0 |   Needs_tests:  0  

Needs_better_patch:  0 |  
---+
Comment (by nikecitycn):

 [http://www.sneakersupplier.com Nike air force ones]
 [http://www.sneakersupplier.com Air Jordan shoes]
 [http://www.sneakersupplier.com Nike Dunks]
 [http://www.sneakersupplier.com Nike Shox]
 [http://www.sneakersupplier.com Nike Shoes]

-- 
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] #9806: GeometryField crashes contrib.gis.admin

[Django]

#9806: GeometryField crashes contrib.gis.admin
-+--
  Reporter:  ingenieroariel  | Owner:  jbronn   
Status:  assigned| Milestone:  1.2  
 Component:  GIS |   Version:  1.0  
Resolution:  |  Keywords:  admin, gis, GeometryField
 Stage:  Accepted| Has_patch:  1
Needs_docs:  0   |   Needs_tests:  0
Needs_better_patch:  1   |  
-+--
Comment (by nikecitycn):

 [http://www.sneakersupplier.com Nike air force ones]
 [http://www.sneakersupplier.com Air Jordan shoes]
 [http://www.sneakersupplier.com Nike Dunks]
 [http://www.sneakersupplier.com Nike Shox]
 [http://www.sneakersupplier.com Nike Shoes]

-- 
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] #9022: Allow US armed forces state codes for USStateField

[Django]

#9022: Allow US armed forces state codes for USStateField
+---
  Reporter:  Daniel Pope   | Owner:  
dougvanhorn
Status:  reopened   | Milestone:
 
 Component:  django.contrib.localflavor |   Version:  
1.0
Resolution: |  Keywords:
 
 Stage:  Design decision needed | Has_patch:  1 
 
Needs_docs:  0  |   Needs_tests:  0 
 
Needs_better_patch:  0  |  
+---
Comment (by nikecitycn):

 [http://www.sneakersupplier.com Nike air force ones]
 [http://www.sneakersupplier.com Air Jordan shoes]
 [http://www.sneakersupplier.com Nike Dunks]
 [http://www.sneakersupplier.com Nike Shox]
 [http://www.sneakersupplier.com Nike Shoes]

-- 
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] #10166: Cookie test fails in login() view

[Django]

#10166: Cookie test fails in login() view
-+--
  Reporter:  iakbar  | Owner:  nobody   

Status:  closed  | Milestone:  1.1  

 Component:  Authentication  |   Version:  1.0  

Resolution:  wontfix |  Keywords:  authentication, cookie, 
login
 Stage:  Accepted| Has_patch:  1

Needs_docs:  0   |   Needs_tests:  1

Needs_better_patch:  0   |  
-+--
Comment (by nikecitycn):

 [http://www.sneakersupplier.com Nike air force ones]
 [http://www.sneakersupplier.com Air Jordan shoes]
 [http://www.sneakersupplier.com Nike Dunks]
 [http://www.sneakersupplier.com Nike Shox]
 [http://www.sneakersupplier.com Nike Shoes]

-- 
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] #11194: Saving proxy model with raw=True gives UnboundLocalError 'record_exists'

[Django]

#11194: Saving proxy model with raw=True gives UnboundLocalError 'record_exists'
---+
  Reporter:  wardi | Owner:  nobody 
  
Status:  closed| Milestone:  1.1
  
 Component:  Database layer (models, ORM)  |   Version:  1.1-beta-1 
  
Resolution:  fixed |  Keywords:  proxy 
model serialization
 Stage:  Unreviewed| Has_patch:  1  
  
Needs_docs:  0 |   Needs_tests:  1  
  
Needs_better_patch:  1 |  
---+
Comment (by nikecitycn):

 [http://www.sneakersupplier.com Nike air force ones]
 [http://www.sneakersupplier.com Air Jordan shoes]
 [http://www.sneakersupplier.com Nike Dunks]
 [http://www.sneakersupplier.com Nike Shox]
 [http://www.sneakersupplier.com Nike Shoes]

-- 
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] #7163: Region locales' translation objects get overwritten

[Django]

#7163: Region locales' translation objects get overwritten
---+
  Reporter:  oggy  | Owner:  mtredinnick
  
Status:  closed| Milestone: 
  
 Component:  Internationalization  |   Version:  SVN
  
Resolution:  fixed |  Keywords:  translation 
gettext region locale
 Stage:  Accepted  | Has_patch:  1  
  
Needs_docs:  0 |   Needs_tests:  0  
  
Needs_better_patch:  1 |  
---+
Comment (by nikecitycn):

 [http://www.sneakersupplier.com Nike air force ones]
 [http://www.sneakersupplier.com Air Jordan shoes]
 [http://www.sneakersupplier.com Nike Dunks]
 [http://www.sneakersupplier.com Nike Shox]
 [http://www.sneakersupplier.com Nike Shoes]

-- 
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] #3134: [patch] The archive_year date-based generic view should not override a model's default ordering

[Django]

#3134: [patch] The archive_year date-based generic view should not override a
model's default ordering
-+--
  Reporter:  matt.rigg...@gmail.com  | Owner:  jacob
Status:  closed  | Milestone:   
 Component:  Generic views   |   Version:  SVN  
Resolution:  fixed   |  Keywords:   
 Stage:  Design decision needed  | Has_patch:  1
Needs_docs:  0   |   Needs_tests:  0
Needs_better_patch:  0   |  
-+--
Comment (by nikecitycn):

 [http://www.sneakersupplier.com Nike air force ones]
 [http://www.sneakersupplier.com Air Jordan shoes]
 [http://www.sneakersupplier.com Nike Dunks]
 [http://www.sneakersupplier.com Nike Shox]
 [http://www.sneakersupplier.com Nike Shoes]

-- 
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] #5831: Template Debug highlights wrong {% for %} tag

[Django]

#5831: Template Debug highlights wrong {% for %} tag
--+-
  Reporter:  Charmless   | Owner:  
charmless 
Status:  reopened | Milestone:  
  
 Component:  Template system  |   Version:  SVN 
  
Resolution:   |  Keywords:  debug 
for toplevel nesting
 Stage:  Accepted | Has_patch:  1   
  
Needs_docs:  0|   Needs_tests:  0   
  
Needs_better_patch:  0|  
--+-
Comment (by nikecitycn):

 [http://www.sneakersupplier.com Nike air force ones]
 [http://www.sneakersupplier.com Air Jordan shoes]
 [http://www.sneakersupplier.com Nike Dunks]
 [http://www.sneakersupplier.com Nike Shox]
 [http://www.sneakersupplier.com Nike Shoes]

-- 
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
-~--~~~~--~~--~--~---