[Django] #22097: IntegerField with given choices leads to wrong has_changed() work

[Django]

#22097: IntegerField with given choices leads to wrong has_changed() work
-+-
 Reporter:  igor.mitrenko@…  |  Owner:  nobody
 Type:  Bug  | Status:  new
Component:  Forms|Version:  1.7-alpha-1
 Severity:  Normal   |   Keywords:
 Triage Stage:  Unreviewed   |  Has patch:  0
Easy pickings:  0|  UI/UX:  0
-+-
 It seems that providing choices to IntegerField makes ModelForm (created
 by admin, for example) to use ChoiceField and call it's to_python method,
 which return string. Finally, _has_changed method compares initial value
 (of type int) to new value (of type unicode), and always returns True.
 My code sending "object created" signals on each inline object change, so
 it leads to creation of unnecessary "changed" events logging.

 Snippet:
 {{{
 ...
 class PhoneNumber(models.Model):
 """
 Phone number set for workers
 """
 MOBILE_PHONE = 0
 WORK_PHONE = 1
 HOME_PHONE = 2
 KIND_CHOICES = (
 (MOBILE_PHONE, _('Mobile')),
 (WORK_PHONE, _('Work')),
 (HOME_PHONE, pgettext('kind of phone number', 'Home')),
 )
 worker = models.ForeignKey(Worker)
 phone_number = models.CharField(_('phone number'), max_length=12)
 kind = models.SmallIntegerField(_('kind of number'),
 choices=KIND_CHOICES, default=MOBILE_PHONE)
 ...
 }}}
 ModelForm derived from such a model created ChoiceField for kind, but it's
 has_changed method return True always, cause it's (as example) always 1 !=
 u'1'

 Removing choices argument is a workaround, but it breaks desired
 behaviour.
 Another workaround is to use CharField, but the problem still remains.
 Django version 1.7.dev20131210091409

-- 
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 unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/066.57988ff4f124cebcfefa87991b82bf89%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #7220: django.contrib.auth.models.AbstractBaseUser.last_login should allow null=True

[Django]

#7220: django.contrib.auth.models.AbstractBaseUser.last_login should allow
null=True
-+-
 Reporter:  veena|Owner:  anonymous
 Type:   |   Status:  assigned
  Cleanup/optimization   |  Version:  master
Component:  contrib.auth |   Resolution:
 Severity:  Normal   | Triage Stage:
 Keywords:  schemamigration  |  Someday/Maybe
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by simon29):

 * cc: simon@… (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 unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/063.199a3b6fefded50bb357adbfd8de9419%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #22096: Incorrect JOIN when using annotate and multiple filters

[Django]

#22096: Incorrect JOIN when using annotate and multiple filters
-+-
 Reporter:  tomo.otsuka@…|Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  1.6
  (models, ORM)  |   Resolution:
 Severity:  Normal   | Triage Stage:
 Keywords:   |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by tomo.otsuka@…):

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


Comment:

 I should have mentioned that I used the models from the django docs for
 aggregation
 ([https://docs.djangoproject.com/en/dev/topics/db/aggregation/])

-- 
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 unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/079.efa957f1d5341b8d109e5be51e421ebd%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

[Django] #22096: Incorrect JOIN when using annotate and multiple filters

[Django]

#22096: Incorrect JOIN when using annotate and multiple filters
--+
 Reporter:  tomo.otsuka@… |  Owner:  nobody
 Type:  Bug   | Status:  new
Component:  Database layer (models, ORM)  |Version:  1.6
 Severity:  Normal|   Keywords:
 Triage Stage:  Unreviewed|  Has patch:  0
Easy pickings:  0 |  UI/UX:  0
--+
 When using chained filters with annotate, the emitted SQL has an
 extraneous and incorrect join causing the result to be a cross-product of
 itself.

 Please see the following two QuerySets. They are logically the same, but
 first QuerySet uses one filter, and the second QuerySet uses two filters.

 {{{
 # good example with using only one filter
 pubs_one_filter = Publisher.objects.filter(book__pages__gt=100,
 book__price__lt=10)
 print pubs_one_filter.query
 # SELECT "tester_publisher"."id", "tester_publisher"."name",
 "tester_publisher"."num_awards" FROM "tester_publisher" INNER JOIN
 "tester_book" ON ( "tester_publisher"."id" = "tester_book"."publisher_id"
 ) WHERE ("tester_book"."price" < 10  AND "tester_book"."pages" > 100 )

 # bad example with using two chained filters
 pubs_two_filter =
 Publisher.objects.filter(book__pages__gt=100).filter(book__price__lt=10)
 print pubs_two_filter.query
 # SELECT "tester_publisher"."id", "tester_publisher"."name",
 "tester_publisher"."num_awards" FROM "tester_publisher" INNER JOIN
 "tester_book" ON ( "tester_publisher"."id" = "tester_book"."publisher_id"
 ) INNER JOIN "tester_book" T3 ON ( "tester_publisher"."id" =
 T3."publisher_id" ) WHERE ("tester_book"."pages" > 100  AND T3."price" <
 10 )
 }}}

 The JOIN with T3 and the JOIN immediately preceding it is the same JOIN.
 It effectively is a cross-product.

-- 
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 unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/064.8de77a5f4119c20e49842c672a302647%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #22095: Migrations containing RunPython operations cannot be reversed regardless of reverse_code

[Django]

#22095: Migrations containing RunPython operations cannot be reversed 
regardless of
reverse_code
+--
 Reporter:  andrewsg|Owner:  andrewsg
 Type:  Bug |   Status:  assigned
Component:  Migrations  |  Version:  master
 Severity:  Normal  |   Resolution:
 Keywords:  | Triage Stage:  Unreviewed
Has patch:  1   |  Needs documentation:  0
  Needs tests:  0   |  Patch needs improvement:  0
Easy pickings:  0   |UI/UX:  0
+--
Changes (by andrewsg):

 * status:  new => assigned
 * needs_better_patch:   => 0
 * needs_tests:   => 0
 * owner:   => andrewsg
 * needs_docs:   => 0
 * has_patch:  0 => 1


Comment:

 Fix supplied in PR: https://github.com/django/django/pull/2329

-- 
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 unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/066.7a7110b6053926d7d4ee18da6b924815%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #20856: Error with admin popups: expected a character buffer object

[Django]

#20856: Error with admin popups: expected a character buffer object
-+-
 Reporter:  heppner.mark@…   |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  contrib.admin|  Version:  1.6
 Severity:  Normal   |   Resolution:  needsinfo
 Keywords:  admin, str,  | Triage Stage:
  character, inline, popup   |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by undergroundrob):

 Replying to [comment:19 claudep]:
 > The above example is not usable as is (missing self.aspect_ratio /
 self.aspect_ratio_minimised in AspectRatio).
 > Did you try returning unicode in `MobileDeviceDisplaySize.__unicode__`
 (`return u"%8.2f mm" % (self.diagonal)`)?

 You're quite right; I made a hash of decluttering it. Take 2:
 {{{
 class AspectRatio(models.Model):
 x = models.PositiveIntegerField()
 y = models.PositiveIntegerField()

 def __unicode__(self):
 return "%d:%d" % (self.x, self.y)

 class MobileDeviceDisplaySize(models.Model):
 diagonal = models.FloatField()
 aspect_ratio = models.ForeignKey(AspectRatio)

 @property
 def x(self):
  return '%8.2f mm' % (self.diagonal *
 math.sin(math.atan(self.aspect_ratio.x / self.aspect_ratio.y )))
 @property
 def y(self):
  return '%8.2f mm' % (self.diagonal *
 math.cos(math.atan(self.aspect_ratio.x / self.aspect_ratio.y)))

 def __unicode__(self):
 return "%8.2f mm" % (self.diagonal)

 #Admin.py
 class MobileDeviceDisplaySizeAdmin(admin.ModelAdmin):
 list_display = ('diagonal', 'aspect_ratio', 'x', 'y')
 admin.site.register(MobileDeviceDisplaySize, MobileDeviceDisplaySizeAdmin)

 class AspectRatioAdmin(admin.ModelAdmin):
 list_display = ('x', 'y')
 admin.site.register(AspectRatio, AspectRatioAdmin)
 }}}

 To answer your question, no, wrapping MobileDeviceDisplaySize.__unicode__
 in unicode does not help, nor does it have a detrimental effect.

 Only returning unicode from AspectRatio.__unicode__ works, either by:

 {{{
 return unicode(("%d:%d") % (self.x, self.y))
 }}}

 or

 {{{
 return "%s:%s" % (unicode(self.x), unicode(self.y))
 }}}

-- 
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 unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/080.a269dd308c12d96862323a006d5ef9d3%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

[Django] #22095: Migrations containing RunPython operations cannot be reversed regardless of reverse_code

[Django]

#22095: Migrations containing RunPython operations cannot be reversed 
regardless of
reverse_code
+
 Reporter:  andrewsg|  Owner:
 Type:  Bug | Status:  new
Component:  Migrations  |Version:  master
 Severity:  Normal  |   Keywords:
 Triage Stage:  Unreviewed  |  Has patch:  0
Easy pickings:  0   |  UI/UX:  0
+
 Migrations including RunPython cannot be reversed, regardless of whether
 reverse_code is supplied to RunPython.  Code appears to be in place to
 make the reverse operation function if reverse_code is supplied, but the
 "reversible" attribute on the RunPython class is set to False.

 RunSQL is analogous to RunPython and solves this problem by making
 reversible a property that returns True if reverse_sql is supplied to that
 constructor, so presumably the same would work for RunPython.

-- 
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 unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/051.888421ba2227af26e9dfc2cd038afaa2%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #1292: [patch] Template loader caching can cause circular imports

[Django]

#1292: [patch] Template loader caching can cause circular imports
-+--
 Reporter:  django@… |Owner:  adrian
 Type:  defect   |   Status:  closed
Component:  Template system  |  Version:
 Severity:  normal   |   Resolution:  fixed
 Keywords:   | Triage Stage:  Unreviewed
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+--

Comment (by anonymous):

 I looked in the .py file and the for loop is still global. Honestly this
 is annoying.

-- 
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 unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/082.d523d8c1a1369b3fcc81fa28915f7786%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #1292: [patch] Template loader caching can cause circular imports

[Django]

#1292: [patch] Template loader caching can cause circular imports
-+--
 Reporter:  django@… |Owner:  adrian
 Type:  defect   |   Status:  closed
Component:  Template system  |  Version:
 Severity:  normal   |   Resolution:  fixed
 Keywords:   | Triage Stage:  Unreviewed
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+--
Changes (by anonymous):

 * ui_ux:   => 0
 * easy:   => 0


Comment:

 I am using Django release 1.5 and I have this error... 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 unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/082.2549c7d561f47c1bd64e43e132e2df8d%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #21093: regressiontests.mail.tests.MailTests.test_dont_base64_encode() fails with Python >=3.3.3

[Django]

#21093: regressiontests.mail.tests.MailTests.test_dont_base64_encode() fails 
with
Python >=3.3.3
---+
 Reporter:  Arfrever   |Owner:  nobody
 Type:  Bug|   Status:  closed
Component:  Testing framework  |  Version:  master
 Severity:  Release blocker|   Resolution:  fixed
 Keywords: | Triage Stage:  Accepted
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+

Comment (by apollo13):

 See
 
https://github.com/django/django/blob/280c1a65ccacd679bf298bf2b169ff01e7266b8e/django/core/mail/message.py#L26
 -- we purposely don't want to change anything globally. also are you
 talking about the 3.3.3 fix, or the 3.3.3+ fix and how exactly would your
 patch look like (and why would it be better than what we have now and
 would the tests pass ;))?

-- 
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 unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/066.e2e993bc7041dfed373611370269dcac%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #14549: Disambiguation of target/source fields for intermediary models when using ManyToManyField

[Django]

#14549: Disambiguation of target/source fields for intermediary models when 
using
ManyToManyField
-+-
 Reporter:  Kronuz   |Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  Database layer   |  Version:  master
  (models, ORM)  |   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:   |  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by dfunckt):

 * cc: akiskesoglou@… (added)
 * needs_tests:  1 => 0


Comment:

 Added tests, documentation and cleaned up the code a bit. Just made a pull
 request: https://github.com/django/django/pull/2327

-- 
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 unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/064.3d025dfeda576b990508871be6cd7ab2%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #22094: Following tutorial on website but in testing section app "polls" is not recognized

[Django]

#22094: Following tutorial on website but in testing section app "polls" is not
recognized
---+--
 Reporter:  croscht@…  |Owner:  nobody
 Type:  Uncategorized  |   Status:  closed
Component:  Testing framework  |  Version:  1.6
 Severity:  Normal |   Resolution:  invalid
 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 anonymous):

 * version:  1.5 => 1.6


-- 
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 unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/080.045fc99b1d4020cfce30e4a84f43c9a0%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #22093: Topic: Customizing Auth. Form-Meta once Tuple, once List

[Django]

#22093: Topic: Customizing Auth. Form-Meta once Tuple, once List
--+
 Reporter:  david-schultz@…   |  Owner:  nobody
 Type:  Cleanup/optimization  | Status:  closed
Component:  Documentation |Version:  1.6
 Severity:  Normal| Resolution:  fixed
 Keywords:|   Triage Stage:  Unreviewed
Has patch:  0 |  Easy pickings:  0
UI/UX:  0 |
--+
Changes (by Tim Graham ):

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


Comment:

 In [changeset:"821fc925f0e384966d0b06d03fc1dd0d14cd8ec0"]:
 {{{
 #!CommitTicketReference repository=""
 revision="821fc925f0e384966d0b06d03fc1dd0d14cd8ec0"
 Fixed #22093 -- Made Form.Meta.fields examples consistent.

 Thanks david-schultz at gmx.net for the suggestion.
 }}}

-- 
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 unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/079.7a096d1e836a3f3562b799a43631dfbf%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #22093: Topic: Customizing Auth. Form-Meta once Tuple, once List

[Django]

#22093: Topic: Customizing Auth. Form-Meta once Tuple, once List
--+
 Reporter:  david-schultz@…   |  Owner:  nobody
 Type:  Cleanup/optimization  | Status:  closed
Component:  Documentation |Version:  1.6
 Severity:  Normal| Resolution:  fixed
 Keywords:|   Triage Stage:  Unreviewed
Has patch:  0 |  Easy pickings:  0
UI/UX:  0 |
--+

Comment (by Tim Graham ):

 In [changeset:"e56ce87bd8cb85a14d34e7bdfac4b55fac95faea"]:
 {{{
 #!CommitTicketReference repository=""
 revision="e56ce87bd8cb85a14d34e7bdfac4b55fac95faea"
 [1.6.x] Fixed #22093 -- Made Form.Meta.fields examples consistent.

 Thanks david-schultz at gmx.net for the suggestion.

 Backport of 821fc925f0 from master
 }}}

-- 
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 unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/079.286bdbb2763ea0d6ce893b2a4eb24b20%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

[django/django] e56ce8: [1.6.x] Fixed #22093 -- Made Form.Meta.fields exam...

[GitHub]

  Branch: refs/heads/stable/1.6.x
  Home:   https://github.com/django/django
  Commit: e56ce87bd8cb85a14d34e7bdfac4b55fac95faea
  
https://github.com/django/django/commit/e56ce87bd8cb85a14d34e7bdfac4b55fac95faea
  Author: Tim Graham 
  Date:   2014-02-19 (Wed, 19 Feb 2014)

  Changed paths:
M docs/topics/auth/customizing.txt

  Log Message:
  ---
  [1.6.x] Fixed #22093 -- Made Form.Meta.fields examples consistent.

Thanks david-schultz at gmx.net for the suggestion.

Backport of 821fc925f0 from master


-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/5304eaf34fa13_498a1281d3c526be%40hookshot-fe1-cp1-prd.iad.github.net.mail.
For more options, visit https://groups.google.com/groups/opt_out.

[django/django] 821fc9: Fixed #22093 -- Made Form.Meta.fields examples con...

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 821fc925f0e384966d0b06d03fc1dd0d14cd8ec0
  
https://github.com/django/django/commit/821fc925f0e384966d0b06d03fc1dd0d14cd8ec0
  Author: Tim Graham 
  Date:   2014-02-19 (Wed, 19 Feb 2014)

  Changed paths:
M docs/topics/auth/customizing.txt

  Log Message:
  ---
  Fixed #22093 -- Made Form.Meta.fields examples consistent.

Thanks david-schultz at gmx.net for the suggestion.


-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/5304eae06b6c6_40c710e9d44316d5%40hookshot-fe1-cp1-prd.iad.github.net.mail.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #22094: Following tutorial on website but in testing section app "polls" is not recognized

[Django]

#22094: Following tutorial on website but in testing section app "polls" is not
recognized
---+--
 Reporter:  croscht@…  |Owner:  nobody
 Type:  Uncategorized  |   Status:  closed
Component:  Testing framework  |  Version:  1.5
 Severity:  Normal |   Resolution:  invalid
 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 timo):

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


Comment:

 This ticket tracker isn't a support channel, please see
 https://code.djangoproject.com/wiki/TicketClosingReasons/UseSupportChannels

-- 
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 unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/080.a49267a749d5320db54aa2c7017e200b%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #21093: regressiontests.mail.tests.MailTests.test_dont_base64_encode() fails with Python >=3.3.3

[Django]

#21093: regressiontests.mail.tests.MailTests.test_dont_base64_encode() fails 
with
Python >=3.3.3
---+
 Reporter:  Arfrever   |Owner:  nobody
 Type:  Bug|   Status:  closed
Component:  Testing framework  |  Version:  master
 Severity:  Release blocker|   Resolution:  fixed
 Keywords: | Triage Stage:  Accepted
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+

Comment (by cainmatt@…):

 regarding message.py:

 I think that rather than re-encoding the message in SafeMimeText you
 should set the encoding globally for python using:

 Charset.add_charset('utf-8', Charset.SHORTEST, None, 'utf-8')

 Note:

 u1 = Charset.Charset('utf-8')
 u1.body_encoding = None
 u2 = Charset.Charset('utf-8')

 u2.body_encoding != u1.body_encoding

-- 
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 unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/066.00c4cf9c4ba87d76112ead2a4357d578%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

[Django] #22094: Following tutorial on website but in testing section app "polls" is not recognized

[Django]

#22094: Following tutorial on website but in testing section app "polls" is not
recognized
---+
 Reporter:  croscht@…  |  Owner:  nobody
 Type:  Uncategorized  | Status:  new
Component:  Testing framework  |Version:  1.5
 Severity:  Normal |   Keywords:
 Triage Stage:  Unreviewed |  Has patch:  0
Easy pickings:  0  |  UI/UX:  0
---+
 Hello,

 I am following the tutorial for Django 1.5 with Pytohon 3.3.3 word by word
 and somehow I am getting an Error in the testing section. I am using ERIC5
 as IDE.
 The result is: [http://hastebin.com/nawihopiqo.tex]
 My settings looks like this: [https://dpaste.de/fxjo]
 My tests.py: [https://dpaste.de/Fqy5]
 My manage.py: [https://dpaste.de/rHc3]

 I already did some research and also tried to get some advice on IRC. I
 have no clue what went wrong or if I missed something in the docs. I hope
 for help.

 Additionally I added my complete project.

 Regards,

 Christian

-- 
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 unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/065.9b75c842e26a8bc1ea1d12ee7319f9a0%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

[Django] #22093: Topic: Customizing Auth. Form-Meta once Tuple, once List

[Django]

#22093: Topic: Customizing Auth. Form-Meta once Tuple, once List
--+
 Reporter:  david-schultz@…   |  Owner:  nobody
 Type:  Cleanup/optimization  | Status:  new
Component:  Documentation |Version:  1.6
 Severity:  Normal|   Keywords:
 Triage Stage:  Unreviewed|  Has patch:  0
Easy pickings:  0 |  UI/UX:  0
--+
 https://docs.djangoproject.com/en/1.6/topics/auth/customizing/

 I am referring to the very last (big) green box at the bottom of this
 page. There the admin is customized by specifying a UserCreationForm and a
 UserChangeForm.
 Within each of these classes, the class Meta is defined. Its property
 'fields', however, is set a tuple in the CreationForm, but a list in the
 ChangeForm.

 I guess only one of them is considered the way it should be.

 Best regards
 David

-- 
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 unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/064.45c07efd1a59a6dfefc18ac3a7832cb7%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #22032: Document settings.MIGRATION_MODULES

[Django]

#22032: Document settings.MIGRATION_MODULES
--+
 Reporter:  bmispelon |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  Documentation |  Version:  master
 Severity:  Release blocker   |   Resolution:
 Keywords:  migrations| Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  1 |UI/UX:  0
--+

Comment (by bmispelon):

 At the very least, it should be present in the full list of settings [1].

 A mention in the migrations documentation itself would be a good idea too
 though I'm not sure which section is the most appropriate for that.

 The second section ("Two commands") says that "the migration files for
 each app live in a “migrations” directory inside of that app [...]" so
 maybe a quick mention of the setting at this point would be best.

 What do you think?

 [1] https://docs.djangoproject.com/en/dev/ref/settings/

-- 
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 unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/067.cfb58e4c71a8730d7926d7be618489fb%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #22032: Document settings.MIGRATION_MODULES

[Django]

#22032: Document settings.MIGRATION_MODULES
--+
 Reporter:  bmispelon |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  Documentation |  Version:  master
 Severity:  Release blocker   |   Resolution:
 Keywords:  migrations| Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  1 |UI/UX:  0
--+

Comment (by vedran):

 Should this should reside
 https://docs.djangoproject.com/en/dev/topics/migrations/#adding-
 migrations-to-apps ?

-- 
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 unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/067.8fabf826e2e02e1e808ff571ecb8f6ed%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

[Django] #22092: Docs don't mention ResolverMatch.view_name

[Django]

#22092: Docs don't mention ResolverMatch.view_name
-+-
   Reporter:  EvilDMP|  Owner:  nobody
   Type: | Status:  new
  Uncategorized  |Version:  1.6
  Component: |   Keywords:  afraid-to-commit
  Documentation  |  Has patch:  0
   Severity:  Normal |Needs tests:  0
   Triage Stage: |  Easy pickings:  1
  Unreviewed |
Needs documentation:  0  |
Patch needs improvement:  0  |
  UI/UX:  0  |
-+-
 
https://docs.djangoproject.com/en/dev/ref/urlresolvers/#django.core.urlresolvers.ResolverMatch

 `view_name` is another property available `resolve('/some/url/path')` when
 it successfully returns a `ResolverMatch`.

 It should be listed here.

-- 
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 unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/050.ed4b50ccab50eaca00db92885b5d2211%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

[django/django] 99416c: Added an example to the release notes for custom r...

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 99416c7ad061f9316089ee490ea721f79141bdf3
  
https://github.com/django/django/commit/99416c7ad061f9316089ee490ea721f79141bdf3
  Author: Loic Bistuer 
  Date:   2014-02-19 (Wed, 19 Feb 2014)

  Changed paths:
M docs/releases/1.7.txt
M docs/topics/db/queries.txt

  Log Message:
  ---
  Added an example to the release notes for custom reverse managers.


-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/5304a7713ef55_928130dd3c641c%40hookshot-fe1-cp1-prd.iad.github.net.mail.
For more options, visit https://groups.google.com/groups/opt_out.

[django/django] b4f21d: Fixed #19647 -- Added formats.py for Esperanto.

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: b4f21d1807e0faf709ee5ae3a1518d6db8983581
  
https://github.com/django/django/commit/b4f21d1807e0faf709ee5ae3a1518d6db8983581
  Author: Baptiste Darthenay 
  Date:   2014-02-19 (Wed, 19 Feb 2014)

  Changed paths:
A django/conf/locale/eo/__init__.py
A django/conf/locale/eo/formats.py
M docs/releases/1.7.txt

  Log Message:
  ---
  Fixed #19647 -- Added formats.py for Esperanto.

Thanks to Objectivesea and Guttorm Flatabø (dittaeva)!


-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/53048f53396b8_77d0aa3d40725b3%40hookshot-fe2-cp1-prd.iad.github.net.mail.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #19647: esperanto formats.py

[Django]

#19647: esperanto formats.py
--+
 Reporter:  post@…|Owner:  batisteo
 Type:  New feature   |   Status:  closed
Component:  Translations  |  Version:  1.4
 Severity:  Normal|   Resolution:  fixed
 Keywords:  esperanto | Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+
Changes (by Baptiste Mispelon ):

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


Comment:

 In [changeset:"b4f21d1807e0faf709ee5ae3a1518d6db8983581"]:
 {{{
 #!CommitTicketReference repository=""
 revision="b4f21d1807e0faf709ee5ae3a1518d6db8983581"
 Fixed #19647 -- Added formats.py for Esperanto.

 Thanks to Objectivesea and Guttorm Flatabø (dittaeva)!
 }}}

-- 
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 unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/081.b02be73bb6d3176ea98b6c74dc1d6d7e%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #19647: esperanto formats.py

[Django]

#19647: esperanto formats.py
--+
 Reporter:  post@…|Owner:  batisteo
 Type:  New feature   |   Status:  new
Component:  Translations  |  Version:  1.4
 Severity:  Normal|   Resolution:
 Keywords:  esperanto | Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+
Changes (by batisteo):

 * has_patch:  0 => 1


Comment:

 Pull request here: https://github.com/django/django/pull/2326

-- 
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 unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/081.a2163a208c223c62306d5bb88e81b9a3%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #22086: Building of template nodelist inside cache blocks

[Django]

#22086: Building of template nodelist inside cache blocks
--+
 Reporter:  HenrikOssipoff|Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  Template system   |  Version:  1.6
 Severity:  Normal|   Resolution:
 Keywords:  template, cache   | Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+

Comment (by HenrikOssipoff):

 You are absolutely right - at some point the cached node will need to be
 rendered, at which point the nodelist inside the cached block will become
 irrelevant - it will just load whatever is cached instead and ignore the
 underlying tree.
 But the tree still exists under the cached block until that point, and
 that seems to be the performance bottleneck we're experiencing, the fact
 that the tree needs to be built.

 I've attached two of our template files to perhaps give a better
 understanding. `menu_dk.html` is being included from our `base.html`
 template, which forms the basis of all of our other templates. If you look
 at that template, it's mostly just a cache block with other files included
 within that cache block. So far so good.
 Then comes one of the included files, `games.html`. If you look through a
 bit of that, you see that nearly everything in it is custom template tags,
 namely `url-translate` and `facet-translate`. We know this is an ugly way
 to do it, but it's needed for our application at the moment - each of
 these tags generates a node that will, in their `render()`, do a look-up
 in our product catalogue to find the correct translation for whatever
 language we're showing. No code of value is in the nodes' `__init__`.

 From my findings, it is the sheer number of nodes in the sub-tree of nodes
 inside the cache block that makes the template slow, even when the whole
 block is in fact cached. Sure, the nodes aren't rendered, but they still
 exist in the tree, causing up to 100ms to 200ms of extra time for our
 application.

 In our particular case, it seems it would be an optimization if we could
 somehow tell the cache block to only built its inside nodelist if there
 didn't exist a valid cache for the block. In most cases, this check would
 likely take up more time than just building the tree, while in extreme
 cases of alot of nodes inside the cache block, it would be an
 optimization.

 Hope this made it more clear, otherwise I'll be happy to provide more code
 if need be.

-- 
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 unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/072.271f9614c57dcb93560d16944f617078%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

[Django] #22091: skin care neat

[Django]

#22091: skin care neat 
---+-
 Reporter:  anonymous  |  Owner:  nobody
 Type:  New feature| Status:  new
Component:  Uncategorized  |Version:  1.6
 Severity:  Normal |   Keywords:  Super Cleanse Total
 Triage Stage:  Unreviewed |  Has patch:  0
Easy pickings:  0  |  UI/UX:  0
---+-
 not only did she put it together a showstopper but she put the number 1
 selling products within the entire line these are allRCMP skincare send
 chills vitamin C rapid [http://supercleansetotalfacts.com/ Super Cleanse
 Total]  transport see that actually delivers that vitamin C into your skin
 at a faster pace today it's forty nine dollars and ninety-five cents to
 flex payment twenty four dollars and ninety eight cents just these
 capsules right here we've sold over one 100 and did teen million are
 wrapping transplant is highly it’s not all your girls not available
 anyplace else that's here on hen a hundred and fifteen thousand hours have
 been ordered suggest that one product and it's so effective you don't even
 need to use it every single day now what you are looking at here is
 complete vitamin C kids this is what I use these from my basics clan share
 the every other day anti-wrinkle capsule the everyday wrinkle filling I
 like me which means it's instinct wrinkle fell long-term benefits a
 vitamin C the day cream which has in it ob this is this is list tiny
 fillers hyaluronic acid that still the wrinkles temporarily on your face
 and then you have long-term benefits now need to stand that what you're
 looking at here then you have your night cream full-size by your day cream
 is 1 it's usually one ounce gold ounce ago well you're getting one point 8
 pounds forty to fifty at we've sold one million 46,000 rise at that green
 here at this stage shell a bigger size near Lincoln filled a queen small
 size of your night going full-size have your eye on of well full container
 and your every other dainty-wrinkle caps and bat foaled size I love the
 cleanser at $49.95 that is over 50 percent of the price approx art tears I
 me think about this just for wannabes right forty two dollars and fifty
 cents I'm going to go over seven dollars an hour we’re giving you
 everything else said this one product which is consistently a top-rated
 customer pack this is your day cream it does provide yes sun protection
 factor so it's your day cream pitcher hydrator charm which riser feature
 sunscreen but you know what else is on product as it also goes in and
 pills in and plump up the lines and wrinkles when Adrian shows that you
 are going to be back all just for that alone at $49.95 a great night here
 115 million at those capsules wire their customer pick because they worked
 there so potent that they put him on a strain on your skin even to
 Washington it penetrates under the skin and one thing about your moose
 cleanser here I ointment and her nighttime cream you get it all full size
 or bigger than full-size that’s larger than poolside that's our forty to
 fifty billion rising day cream it’s my gosh what is that I’ll figure out
 the value we're going to go over Adrian own she's going to show you why
 these products have always been our number one seller says the value Isa
 158 50 think I said it showed that fifty percent a question comes to
 embarrassing it on the it's a third the price and is our biggest selling
 kit at anything we sell why am I giving it to you $49.95 I’ll tell you
 simply you try you will be mine her after show what I tried to do in
 February is one crazy by a vitamin C and you’re looking at it today Shaw
 what I want you to see when she take aloof at Pour Paul is 56 years old
 you're going to take a look at polls before and after and I think you will
 see motion picture sat Perry we just put to the same pictures and sure
 you'll be able to see the actual real be 4i was now watch what we're
 dealing with this and you will see an amazing difference first thing we're
 going to go when combined wrinkle line by line and put on vitamin Captains
 I do not make these captains they are made by a giant pharmaceutical
 company and the pharmaceutical company that makes them came to hen years
 ago and said we have breakthrough for over 40s get we have women that we
 have we have a product that women over 40 have never seen before it's a
 vitamin C weak men that's made just for them too powerful if you’re under
 forty is on and if you smoke each issued directly into the lines around
 the map few that this map shell wrinkle my winkle line
 http://supercleansetotalfacts.com/

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

Re: [Django] #20856: Error with admin popups: expected a character buffer object

[Django]

#20856: Error with admin popups: expected a character buffer object
-+-
 Reporter:  heppner.mark@…   |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  contrib.admin|  Version:  1.6
 Severity:  Normal   |   Resolution:  needsinfo
 Keywords:  admin, str,  | Triage Stage:
  character, inline, popup   |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by claudep):

 The above example is not usable as is (missing self.aspect_ratio /
 self.aspect_ratio_minimised in AspectRatio).
 Did you try returning unicode in `MobileDeviceDisplaySize.__unicode__`
 (`return u"%8.2f mm" % (self.diagonal)`)?

-- 
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 unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/080.79314f90c2624861a480fa78218f1dd1%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.