[Django] #19696: Collectstatic management command: unicodeerror

[Django]

#19696: Collectstatic management command: unicodeerror
-+-
 Reporter:   |  Owner:  nobody
  arn.breton@…   | Status:  new
 Type:  Bug  |Version:  1.4
Component:   |   Keywords:  unicodeerror, collectstatic, css,
  contrib.staticfiles|  assets
 Severity:  Normal   |  Has patch:  0
 Triage Stage:   |  UI/UX:  0
  Unreviewed |
Easy pickings:  0|
-+-
 Hi,

 I experienced an issue today while using the collectstatic command.

 One of my CSS files contains some comments with accent marks (I'm french).
 When the command passes on this file, it crashes with a standard
 unicodeerror ("character not in range").

 The error occured here:
 
https://github.com/django/django/blob/master/django/contrib/staticfiles/storage.py#L226

 When I deleted these comments, it works again.

-- 
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.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #19527: bulk_create() can set the primary key

[Django]

#19527: bulk_create() can set the primary key
-+-
 Reporter:  Tuttle   |Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  Database layer   |  Version:  master
  (models, ORM)  |   Resolution:
 Severity:  Normal   | Triage Stage:  Design
 Keywords:   |  decision needed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by gwahl@…):

 * cc: gwahl@… (added)


Comment:

 Whether it's implemented as bulk_save() or bulk_create(), I love it.

-- 
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.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #19160: Make ungettext_lazy really usable

[Django]

#19160: Make ungettext_lazy really usable
--+
 Reporter:  claudep   |Owner:  nobody
 Type:  New feature   |   Status:  new
Component:  Internationalization  |  Version:  master
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+

Comment (by aaugustin):

 This looks way better than the previous attempts. It's probably RFC — it
 just needs running the tests on Python 2 and 3 and proof-reading
 carefully.

-- 
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.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #17797: Added PATCH request functionality to django.test.client.Client

[Django]

#17797: Added PATCH request functionality to django.test.client.Client
---+
 Reporter:  pfarmer|Owner:  nobody
 Type:  New feature|   Status:  new
Component:  Testing framework  |  Version:  master
 Severity:  Normal |   Resolution:
 Keywords:  Test   | Triage Stage:  Accepted
Has patch:  1  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+

Comment (by tim.dawborn@…):

 +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 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.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #19160: Make ungettext_lazy really usable

[Django]

#19160: Make ungettext_lazy really usable
--+
 Reporter:  claudep   |Owner:  nobody
 Type:  New feature   |   Status:  new
Component:  Internationalization  |  Version:  master
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+

Comment (by void):

 I've sent a pull request with code cleaned up a bit:
 https://github.com/django/django/pull/684

-- 
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.
For more options, visit https://groups.google.com/groups/opt_out.

[django/django] 47ddd6: Fixed #19552 -- Enhanced makemessages handling of ...

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 47ddd6a4082d55d8856b7e6beac553485dd627f7
  
https://github.com/django/django/commit/47ddd6a4082d55d8856b7e6beac553485dd627f7
  Author: Ramiro Morales 
  Date:   2013-01-29 (Tue, 29 Jan 2013)

  Changed paths:
M django/utils/translation/__init__.py
M django/utils/translation/trans_real.py
M docs/releases/1.6.txt
M docs/topics/i18n/translation.txt
M docs/topics/templates.txt
M tests/regressiontests/i18n/commands/extraction.py
A tests/regressiontests/i18n/commands/templates/comments.thtml

  Log Message:
  ---
  Fixed #19552 -- Enhanced makemessages handling of ``{# #}``-style template 
comments.

They are simply ignored now. This allows for a more correct behavior when
they are placed before translatable constructs on the same line.

Previously, the latter were wrongly ignored because the former were
preserved when converting template code to the internal Python-syntax
form later fed to xgettext but Python has no ``/* ... */``-style
comments.

Also, special comments directed to translators are now only taken in
account when they are located at the end of a line. e.g.::

  {# Translators: ignored #}{% trans "Literal A" %}{# Translators: valid, 
associated with "Literal B" below #}
  {% trans "Literal B" %}

Behavior of ``{% comment %}...{% endcomment %}``tags remains unchanged.

Thanks juneih at redpill-linpro dot com for the report and Claude for
his work on the issue.



-- 
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.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #18648: ConditionalGetMiddleware does not work with Internet Explorer

[Django]

#18648: ConditionalGetMiddleware does not work with Internet Explorer
---+--
 Reporter:  KyleMac|Owner:  nobody
 Type:  Bug|   Status:  closed
Component:  HTTP handling  |  Version:  1.4
 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 ramiro):

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


Comment:

 Replying to [comment:4 harm]:
 > more info provided in comment:3 -> reopen

 Can you perform the tests and provide  the information that comment
 suggests should be done?

-- 
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.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #19126: runserver versus model validation

[Django]

#19126: runserver versus model validation
-+-
 Reporter:  direvus  |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Core (Management |  Version:  1.3
  commands)  |   Resolution:
 Severity:  Normal   | Triage Stage:  Design
 Keywords:   |  decision needed
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by anonymous):

 This bug effectively kills using Celery's django integration
 http://pypi.python.org/pypi/django-celery since it uses `manage.py` to
 start the Celery workers.

-- 
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.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #19552: makemessages ignores translations in templates with inline comment tags

[Django]

#19552: makemessages ignores translations in templates with inline comment tags
-+-
 Reporter:  juneih@… |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:   |  Version:  1.4
  Internationalization   |   Resolution:  fixed
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:  makemessages,|  Needs documentation:  0
  template, gettext, xgettext|  Patch needs improvement:  0
Has patch:  1|UI/UX:  0
  Needs tests:  0|
Easy pickings:  1|
-+-
Changes (by Ramiro Morales ):

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


Comment:

 In [changeset:"47ddd6a4082d55d8856b7e6beac553485dd627f7"]:
 {{{
 #!CommitTicketReference repository=""
 revision="47ddd6a4082d55d8856b7e6beac553485dd627f7"
 Fixed #19552 -- Enhanced makemessages handling of ``{# #}``-style template
 comments.

 They are simply ignored now. This allows for a more correct behavior when
 they are placed before translatable constructs on the same line.

 Previously, the latter were wrongly ignored because the former were
 preserved when converting template code to the internal Python-syntax
 form later fed to xgettext but Python has no ``/* ... */``-style
 comments.

 Also, special comments directed to translators are now only taken in
 account when they are located at the end of a line. e.g.::

   {# Translators: ignored #}{% trans "Literal A" %}{# Translators: valid,
 associated with "Literal B" below #}
   {% trans "Literal B" %}

 Behavior of ``{% comment %}...{% endcomment %}``tags remains unchanged.

 Thanks juneih at redpill-linpro dot com for the report and Claude for
 his work on the issue.
 }}}

-- 
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.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #19142: accept_language_re rejects languages which include numeric UN region codes

[Django]

#19142: accept_language_re rejects languages which include numeric UN region 
codes
-+-
 Reporter:  DrMeers  |Owner:  Architekt
 Type:  Bug  |   Status:  closed
Component:   |  Version:  1.4
  Internationalization   |   Resolution:  fixed
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:   |  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  1|
-+-

Comment (by esevece):

 Thank you charettes!
 I didn't know that I could install a tar.gz directly from pip.

-- 
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.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #18648: ConditionalGetMiddleware does not work with Internet Explorer

[Django]

#18648: ConditionalGetMiddleware does not work with Internet Explorer
---+--
 Reporter:  KyleMac|Owner:  nobody
 Type:  Bug|   Status:  new
Component:  HTTP handling  |  Version:  1.4
 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 harm):

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


Comment:

 more info provided in comment:3 -> reopen

-- 
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.
For more options, visit https://groups.google.com/groups/opt_out.

[Django] #19695: Static files for forms described as "Form Media"

[Django]

#19695: Static files for forms described as "Form Media"
--+
   Reporter:  aaugustin   |  Owner:  nobody
   Type:  Bug | Status:  new
  Component:  Forms   |Version:  master
   Severity:  Normal  |   Keywords:
   Triage Stage:  Unreviewed  |  Has patch:  0
Needs documentation:  0   |Needs tests:  0
Patch needs improvement:  0   |  Easy pickings:  0
  UI/UX:  0   |
--+
 https://docs.djangoproject.com/en/dev/topics/forms/media/

 This is confusing. In Django, "media" == "user-uploaded files".

 The code be docs should be refactored to call them something else: "form
 static files", "form static assets", "form assets" -- anything but "form
 media"!

-- 
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.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #19692: Replace HttpResponse.mimetype (deprecated) with content_type in doc examples

[Django]

#19692: Replace HttpResponse.mimetype (deprecated) with content_type in doc
examples
--+
 Reporter:  timo  |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  Documentation |  Version:  master
 Severity:  Release blocker   |   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+
Changes (by aaugustin):

 * severity:  Normal => Release blocker


Comment:

 We should at least make a decision before the release!

-- 
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.
For more options, visit https://groups.google.com/groups/opt_out.

[Django] #19694: python manage.py syncdb fails if no locale is set

[Django]

#19694: python manage.py syncdb fails if no locale is set
+
 Reporter:  gunther.stengl@…|  Owner:  nobody
 Type:  Uncategorized   | Status:  new
Component:  Core (Management commands)  |Version:  1.4
 Severity:  Normal  |   Keywords:
 Triage Stage:  Unreviewed  |  Has patch:  0
Easy pickings:  0   |  UI/UX:  0
+
 I already filed a FreeBSD Problem Report under
 http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/175178

 - Django (py27-django-1.4.3) fails to create the db-superuser when doing a
 "python mange.py syncdb" AND "LC_ALL" is unset.
 - "LC_ALL=" causes the locale.getdefaultlocale() to return "(None, None)"
 which is not a String, as needed by decode().
 - If LC_ALL is set correctly, the scripts runs as expected.

 I posted a porposal for a patch, but on the other hand there's the
 question if django should run "manage.py syncdb" o  a system where
 locale.getdefaultlocale() returns 'None' instead of string. As far as I
 have seen, there's a lot of decoding done with locales, etc.

 Thanks in advance.
 Gunther

-- 
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.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #13794: Django does not respect to_field's model on an inline model admin

[Django]

#13794: Django does not respect to_field's model on an inline model admin
-+-
 Reporter:  sebastien@…  |Owner:  gautier
 Type:  Bug  |   Status:  new
Component:  Forms|  Version:
 Severity:  Normal   |  1.5-beta-1
 Keywords:  admin inline |   Resolution:
  to_field formset   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by anonymous):

 After further investigation it seems that main functional difference
 between the two is that not setting the fk value on form construction
 (fix_inline_model_with_to_field.diff) results in the relationship field
 not being available on a new instance until after full_clean, specifically
 construct_instance, is called on the formset. Setting the fk value on
 construction (to_field_formsets.patch), means that the fk value and
 subsequently the relationship is available when dealing with a new item.

 Adding this line to the test in to_field_formsets.path will make the test
 pass for that patch but fail for fix_inline_model_with_to_field.diff:

 {{{
 self.assertEqual(formset[1].instance.user_id, "guido")
 }}}

 So there is a slight chance of fix_inline_model_with_to_field.diff
 breaking currently working code while to_field_formsets.patch will not.
 But as far as I can tell this undocumented so it's really your call either
 way.

 The problem is that right now, this does have potential to create invalid
 relationships, leading to data corruption. If the value set in
 _construct_form happens to be the same as a valid pk value of that same
 table, then the save happens silently resetting all your relationships to
 point to the wrong record.

-- 
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.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #19692: Replace HttpResponse.mimetype (deprecated) with content_type in doc examples

[Django]

#19692: Replace HttpResponse.mimetype (deprecated) with content_type in doc
examples
--+
 Reporter:  timo  |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  Documentation |  Version:  master
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+

Comment (by charettes):

 Should we mark this as a ''Release Blocker''?

-- 
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.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #19692: Replace HttpResponse.mimetype (deprecated) with content_type in doc examples

[Django]

#19692: Replace HttpResponse.mimetype (deprecated) with content_type in doc
examples
--+
 Reporter:  timo  |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  Documentation |  Version:  master
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+
Changes (by aaugustin):

 * needs_better_patch:   => 0
 * needs_docs:   => 0
 * needs_tests:   => 0
 * stage:  Unreviewed => Accepted


Comment:

 I noticed that inconsistency a few days ago too. It isn't ideal to add a
 deprecation after RC1, but for the sake of consistency, +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 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.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #19693: trancatewords_html closes tags (was: trancatewords_html duplicates tags)

[Django]

#19693: trancatewords_html closes   tags
-+--
 Reporter:  sneawo   |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Template system  |  Version:  1.4
 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
-+--

-- 
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.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #19693: trancatewords_html duplicates tags

[Django]

#19693: trancatewords_html duplicates   tags
-+--
 Reporter:  sneawo   |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Template system  |  Version:  1.4
 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 sneawo):

 * cc: sneawo (added)
 * needs_better_patch:   => 0
 * needs_tests:   => 0
 * needs_docs:   => 0


-- 
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.
For more options, visit https://groups.google.com/groups/opt_out.

[Django] #19693: trancatewords_html duplicates tags

[Django]

#19693: trancatewords_html duplicates   tags
-+
 Reporter:  sneawo   |  Owner:  nobody
 Type:  Bug  | Status:  new
Component:  Template system  |Version:  1.4
 Severity:  Normal   |   Keywords:
 Triage Stage:  Unreviewed   |  Has patch:  0
Easy pickings:  0|  UI/UX:  0
-+
 In [9]: ts = 'testtest test'
 In [10]: struncatewords_html(s, 2)
 Out[10]: u'testtest ...'

-- 
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.
For more options, visit https://groups.google.com/groups/opt_out.

[django/django] eb9430: Implemented some SpatiaLiteOperations as cached pr...

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: eb9430fc4be16f2256f8ff4d8ee90577fb0a8f5a
  
https://github.com/django/django/commit/eb9430fc4be16f2256f8ff4d8ee90577fb0a8f5a
  Author: Claude Paroz 
  Date:   2013-01-29 (Tue, 29 Jan 2013)

  Changed paths:
M django/contrib/gis/db/backends/spatialite/creation.py
M django/contrib/gis/db/backends/spatialite/operations.py

  Log Message:
  ---
  Implemented some SpatiaLiteOperations as cached properties

Previously, some properties weren't set unless
confirm_spatial_components_versions() was explicitely called.



-- 
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.
For more options, visit https://groups.google.com/groups/opt_out.

[Django] #19692: Replace HttpResponse.mimetype (deprecated) with content_type in doc examples

[Django]

#19692: Replace HttpResponse.mimetype (deprecated) with content_type in doc
examples
--+
 Reporter:  timo  |  Owner:  nobody
 Type:  Cleanup/optimization  | Status:  new
Component:  Documentation |Version:  master
 Severity:  Normal|   Keywords:
 Triage Stage:  Unreviewed|  Has patch:  1
Easy pickings:  0 |  UI/UX:  0
--+
 I'm assuming we're also deprecating the `mimetype` argument on
 `TemplateResponse` and `SimpleTemplateResponse`? Alternatively, we'd have
 to add a shim to continue supporting `mimetype` for these classes once
 `mimetype` is removed from `HttpResponse.__init__`.

-- 
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.
For more options, visit https://groups.google.com/groups/opt_out.

[django/django] 5da6ce: [1.5.x] Fixed typos in docs and comments

[GitHub]

  Branch: refs/heads/stable/1.5.x
  Home:   https://github.com/django/django
  Commit: 5da6ce11edb60319c014c07c40b03674ea89de4c
  
https://github.com/django/django/commit/5da6ce11edb60319c014c07c40b03674ea89de4c
  Author: Tim Graham 
  Date:   2013-01-29 (Tue, 29 Jan 2013)

  Changed paths:
M django/contrib/gis/gdal/geometries.py
M django/contrib/gis/geos/prototypes/geom.py
M django/contrib/gis/utils/srs.py
M django/contrib/staticfiles/views.py
M django/db/models/query.py
M django/middleware/csrf.py
M docs/internals/contributing/committing-code.txt
M docs/internals/contributing/writing-code/working-with-git.txt
M docs/intro/overview.txt
M docs/misc/api-stability.txt
M docs/ref/contrib/admin/index.txt
M docs/ref/contrib/gis/install/index.txt
M docs/topics/auth/default.txt
M tests/regressiontests/admin_views/tests.py
M tests/regressiontests/builtin_server/tests.py

  Log Message:
  ---
  [1.5.x] Fixed typos in docs and comments

Backport of ee26797cff 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.
For more options, visit https://groups.google.com/groups/opt_out.

[django/django] ee2679: Fixed typos in docs and comments

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: ee26797cff6ef17817c58e6a2f86db81c21f9800
  
https://github.com/django/django/commit/ee26797cff6ef17817c58e6a2f86db81c21f9800
  Author: Tim Graham 
  Date:   2013-01-29 (Tue, 29 Jan 2013)

  Changed paths:
M django/contrib/gis/gdal/geometries.py
M django/contrib/gis/geos/prototypes/geom.py
M django/contrib/gis/utils/srs.py
M django/contrib/staticfiles/views.py
M django/db/models/query.py
M django/middleware/csrf.py
M docs/internals/contributing/committing-code.txt
M docs/internals/contributing/writing-code/working-with-git.txt
M docs/intro/overview.txt
M docs/misc/api-stability.txt
M docs/ref/contrib/admin/index.txt
M docs/ref/contrib/gis/install/index.txt
M docs/topics/auth/default.txt
M tests/regressiontests/admin_views/tests.py
M tests/regressiontests/builtin_server/tests.py

  Log Message:
  ---
  Fixed typos in docs and comments



-- 
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.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #19690: Class in ajax example doesn't inherit from imported SingleObjectTemplateResponseMixin

[Django]

#19690: Class in ajax example doesn't inherit from imported
SingleObjectTemplateResponseMixin
-+-
 Reporter:  lucianu  |Owner:  lucianu
 Type:  Bug  |   Status:  new
Component:  Documentation|  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Ready for
Has patch:  0|  checkin
  Needs tests:  0|  Needs documentation:  0
Easy pickings:  0|  Patch needs improvement:  0
 |UI/UX:  0
-+-
Changes (by mjtamlyn):

 * stage:  Unreviewed => Ready for checkin


-- 
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.
For more options, visit https://groups.google.com/groups/opt_out.

[Django] #19691: Inconsistency in instantiating/validating ModelForms: CharFields vs. with ImageField only.

[Django]

#19691: Inconsistency in instantiating/validating ModelForms:  CharFields vs. 
with
ImageField only.
--+
 Reporter:  pfeiffersimon@…   |  Owner:  nobody
 Type:  Cleanup/optimization  | Status:  new
Component:  Forms |Version:  1.4
 Severity:  Normal|   Keywords:
 Triage Stage:  Unreviewed|  Has patch:  0
Easy pickings:  0 |  UI/UX:  0
--+
 Hi I found a sligth inconsistency in the instantiation/validation of the
 different field types. Its kinda hard to describe so here some code:

 Consider the following models:
 {{{
 class Text(models.Model):
 """Just a basic model to store some text"""
 create_date = models.DateTimeField(auto_now_add=True)
 content = models.TextField()


 class Picture(models.Model):
 """Just a basic model to store a picture"""
 create_date = models.DateTimeField(auto_now_add=True)
 picture=models.ImageField(upload_to="pics")

 }}}

 And the following forms:


 {{{
 from django.forms import ModelForm
 from notebook.models import *

 class TextForm(ModelForm):
 class Meta:
 model=Text

 class PictureForm(ModelForm):
 class Meta:
 model=Picture
 }}}

 When you now instantiate PictureForm and a TextForm with a bound instance,
 but empty request.POST / request.FILES likes this:


 {{{
 #get_or_none() returns a valid model instance in both cases below
 #req.POST and req.FILES are both empty QueryDict instances

 form_text = TextForm(req.POST,instance=get_or_none(Text,pk=primary_key))
 form_pic = PictureForm(req.POST,req.FILES
 ,instance=get_or_none(Picture,pk=primary_key))

 #The validation of form_text
 form_text.is_valid()
 # >>> FALSE
 form_pic.is_valid()
 # >>> True
 }}}

 So basically, the PictureForm ignores that it gets handed an empty
 req.FILES & req.POST and just uses the instance that is bound.

 Whereas, the TextModel throws errors which get rendered although it has a
 bound a instance:

 {{{
 # found with pdb
 >>> form_text.is_valid()
 FALSE
 >>>form_text.initial
 {'content': u'Some content from the database', 'id': 15}

 }}}

 So as you can see its just a little inconsistency. I do not even know I
 should have reported it. If you are wondering how I came about doing
 something like that:


 {{{
 # Compact way of writing a create/edit form
 def picture_edit(req,primary_keyk=None):

 form = PictureForm(req.POST,req.FILES
 ,instance=get_or_none(Picture,pk=primary_key))
 # Works for req.POST={} & req.FILES={}  and
 instance == Model()

 if req.method == 'POST':
 if form.is_valid():
 form.save()
 return redirect("notebook_dashboard")

 return render(req, 'notebook/picture_edit.html', {'form': form, })

 def text_edit(req,pk=None):

 form = TextForm(req.POST,instance=get_or_none(Text,pk=pk))
 # this does not     when
 req.POST={} and instance == Model()
 if req.method == 'POST': # If the form has been submitted...
 if form.is_valid():
 form.save()
 return redirect("notebook_dashboard") #Redirect to dash
 #Optional else clause not explicitly used
 import pdb; pdb.set_trace()
 return render(req, 'notebook/text_edit.html', {'form': form, })


 }}}

-- 
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.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #19678: Test failure with spatialite

[Django]

#19678: Test failure with spatialite
-+
 Reporter:  julien   |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  GIS  |  Version:  1.4
 Severity:  Release blocker  |   Resolution:
 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 claudep):

 I've just compiled libspatialite 4.0.0 and ran the gis tests without
 errors. I have really no clue what your failure comes from.

-- 
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.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #19414: Add a "register" class decorator for admin.

[Django]

#19414: Add a "register" class decorator for admin.
---+
 Reporter:  stavros|Owner:  BHold
 Type:  New feature|   Status:  new
Component:  contrib.admin  |  Version:  1.4
 Severity:  Normal |   Resolution:
 Keywords: | Triage Stage:  Accepted
Has patch:  1  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+

Comment (by BHold):

 Replying to [comment:8 stavros]:
 > Much better! I would not have added the "Unsupported arguments" check if
 I wrote it, just because someone might want to construct a dict with extra
 stuff and pass it (plus, ignoring kwargs isn't bad for you), but otherwise
 it looks great to me.
 >
 > Can someone official chime in? This pull request looks very good.

 Yeah, perhaps that Unsupported Arguments check was unneeded, I removed it.

-- 
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.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #19690: Class in ajax example doesn't inherit from imported SingleObjectTemplateResponseMixin

[Django]

#19690: Class in ajax example doesn't inherit from imported
SingleObjectTemplateResponseMixin
---+--
 Reporter:  lucianu|Owner:  lucianu
 Type:  Bug|   Status:  new
Component:  Documentation  |  Version:  master
 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 lucianu):

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


Comment:

 Pull request sent https://github.com/django/django/pull/682

-- 
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.
For more options, visit https://groups.google.com/groups/opt_out.

[Django] #19690: Class in ajax example doesn't inherit from imported SingleObjectTemplateResponseMixin

[Django]

#19690: Class in ajax example doesn't inherit from imported
SingleObjectTemplateResponseMixin
---+-
 Reporter:  lucianu|  Owner:  lucianu
 Type:  Bug| Status:  new
Component:  Documentation  |Version:  master
 Severity:  Normal |   Keywords:
 Triage Stage:  Unreviewed |  Has patch:  0
Easy pickings:  0  |  UI/UX:  0
---+-
 The code sample found here https://docs.djangoproject.com/en/dev/topics
 /class-based-views/generic-editing/#ajax-example displays the issue.
 Basically, SingleObjectTemplateResponseMixin is imported but
 AjaxableResponseMixin doesn't inherit from it.

-- 
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.
For more options, visit https://groups.google.com/groups/opt_out.

[django/django] b99a4e: Updated metrics on the documentation.

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: b99a4e1073e5504ec8f40447a8e9fd1066c76b7f
  
https://github.com/django/django/commit/b99a4e1073e5504ec8f40447a8e9fd1066c76b7f
  Author: Aymeric Augustin 
  Date:   2013-01-29 (Tue, 29 Jan 2013)

  Changed paths:
M docs/intro/whatsnext.txt

  Log Message:
  ---
  Updated metrics on the documentation.



-- 
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.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #9249: Google Analytics' Cookies break CacheMiddleware when SessionMiddleware turns on Vary: Cookie

[Django]

#9249: Google Analytics' Cookies break CacheMiddleware when SessionMiddleware
turns on Vary: Cookie
---+
 Reporter:  pixelcort  |Owner:  vvd
 Type:  New feature|   Status:  assigned
Component:  HTTP handling  |  Version:  1.0
 Severity:  Normal |   Resolution:
 Keywords:  cache cookies  | Triage Stage:  Accepted
Has patch:  1  |  Needs documentation:  1
  Needs tests:  0  |  Patch needs improvement:  1
Easy pickings:  0  |UI/UX:  0
---+
Changes (by aaugustin):

 * version:  1.4-rc-2 => 1.0
 * type:  Bug => New feature


Old description:

> When using Google Analytics on a Django project with CacheMiddleware and
> SessionMiddleware turned on, the Cookies that Google Analytics apparently
> change on each reload, invalidating the Vary: Cookie parameter that
> SessionMiddleware is setting.
>
> There should be a way to define cookie prefixes, such as '__utm', to
> ignore for cookie variation for caching.

New description:

 When using Google Analytics on a Django project with CacheMiddleware and
 SessionMiddleware turned on, the Cookies that Google Analytics apparently
 change on each reload, invalidating the Vary: Cookie parameter that
 SessionMiddleware is setting.

 There should be a way to define cookie prefixes, such as ``'__utm'``, to
 ignore for cookie variation for caching.

--

Comment:

 If you look at the discussion, this isn't a bug; it's really a new
 feature.

 The version field tracks the version the bug was reported in.

 Related: #15201. Caching is hard.

-- 
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.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #9249: Google Analytics' Cookies break CacheMiddleware when SessionMiddleware turns on Vary: Cookie

[Django]

#9249: Google Analytics' Cookies break CacheMiddleware when SessionMiddleware
turns on Vary: Cookie
---+
 Reporter:  pixelcort  |Owner:  vvd
 Type:  Bug|   Status:  assigned
Component:  HTTP handling  |  Version:  1.4-rc-2
 Severity:  Normal |   Resolution:
 Keywords:  cache cookies  | Triage Stage:  Accepted
Has patch:  1  |  Needs documentation:  1
  Needs tests:  0  |  Patch needs improvement:  1
Easy pickings:  0  |UI/UX:  0
---+
Changes (by anonymous):

 * needs_docs:  0 => 1
 * version:  1.0 => 1.4-rc-2
 * type:  New feature => 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 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.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #5622: Empty ipaddress raises an error (invalid input syntax for type inet: "")

[Django]

#5622: Empty ipaddress raises an error (invalid input syntax for type inet: "")
-+-
 Reporter:  anonymous|Owner:  aashu_dwivedi
 Type:  Bug  |   Status:  assigned
Component:  Forms|  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:  sprintdec01  | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+-

Comment (by antonagestam):

 Replying to [comment:54 kace]:
 > For users facing this irritating issue, there is a quick, effective
 work-around (based on one of toke's patches (thank you)).  Put this into
 "models.py":
 > {{{
 > class IPAddressFieldNullable(models.IPAddressField) :
 > def get_db_prep_save(self, value):
 > return value or None
 > }}}
 > Then change your IP attribute to use this modified field.  E.g.:
 > {{{
 > -   someip = models.IPAddressField(blank=True, null=True )
 > +   someip = IPAddressFieldNullable(blank=True, null=True )
 > }}}

 Thanks for quick fix, confirmed working. Will this ever be fixed?

-- 
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.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #19683: A minor mistake?

[Django]

#19683: A minor mistake?
---+
 Reporter:  sunsongxp@…|Owner:  nobody
 Type:  Bug|   Status:  closed
Component:  Documentation  |  Version:  1.4
 Severity:  Normal |   Resolution:  fixed
 Keywords:  signing| Triage Stage:  Accepted
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+

Comment (by Tim Graham ):

 In [changeset:"f6075b0596e20951bd8232f09d97fb7fac08308c"]:
 {{{
 #!CommitTicketReference repository=""
 revision="f6075b0596e20951bd8232f09d97fb7fac08308c"
 [1.5.x] Fixed #19683 - Added a missing import in signing example.

 Thanks sunsongxp@ for the report.

 Backport of 537d44b1b9 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.
For more options, visit https://groups.google.com/groups/opt_out.

[django/django] f6075b: [1.5.x] Fixed #19683 - Added a missing import in s...

[GitHub]

  Branch: refs/heads/stable/1.5.x
  Home:   https://github.com/django/django
  Commit: f6075b0596e20951bd8232f09d97fb7fac08308c
  
https://github.com/django/django/commit/f6075b0596e20951bd8232f09d97fb7fac08308c
  Author: Tim Graham 
  Date:   2013-01-29 (Tue, 29 Jan 2013)

  Changed paths:
M docs/topics/signing.txt

  Log Message:
  ---
  [1.5.x] Fixed #19683 - Added a missing import in signing example.

Thanks sunsongxp@ for the report.

Backport of 537d44b1b9 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.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #19683: A minor mistake?

[Django]

#19683: A minor mistake?
---+
 Reporter:  sunsongxp@…|Owner:  nobody
 Type:  Bug|   Status:  closed
Component:  Documentation  |  Version:  1.4
 Severity:  Normal |   Resolution:  fixed
 Keywords:  signing| Triage Stage:  Accepted
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+
Changes (by Tim Graham ):

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


Comment:

 In [changeset:"537d44b1b937c6857ded0a2dc5703c61c5e980b4"]:
 {{{
 #!CommitTicketReference repository=""
 revision="537d44b1b937c6857ded0a2dc5703c61c5e980b4"
 Fixed #19683 - Added a missing import in signing example.

 Thanks sunsongxp@ for the report.
 }}}

-- 
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.
For more options, visit https://groups.google.com/groups/opt_out.

[django/django] 537d44: Fixed #19683 - Added a missing import in signing e...

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 537d44b1b937c6857ded0a2dc5703c61c5e980b4
  
https://github.com/django/django/commit/537d44b1b937c6857ded0a2dc5703c61c5e980b4
  Author: Tim Graham 
  Date:   2013-01-29 (Tue, 29 Jan 2013)

  Changed paths:
M docs/topics/signing.txt

  Log Message:
  ---
  Fixed #19683 - Added a missing import in signing example.

Thanks sunsongxp@ for the report.



-- 
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.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #19689: Use `Options.module_name` instead of `object_name.lower()`

[Django]

#19689: Use `Options.module_name` instead of `object_name.lower()`
-+-
 Reporter:  charettes|Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |  Version:  master
Component:  Database layer   |   Resolution:
  (models, ORM)  | Triage Stage:  Ready for
 Severity:  Normal   |  checkin
 Keywords:   |  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by claudep):

 * component:  ORM aggregation => Database layer (models, ORM)
 * stage:  Unreviewed => Ready for checkin


-- 
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.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #18144: MD5PasswordHasher: broken backwards compatibility with empty salt

[Django]

#18144: MD5PasswordHasher: broken backwards compatibility with empty salt
-+-
 Reporter:  apreobrazhensky@…|Owner:  nobody
 Type:  Bug  |   Status:  reopened
Component:  contrib.auth |  Version:  1.4
 Severity:  Normal   |   Resolution:
 Keywords:  MD5PasswordHasher| Triage Stage:  Accepted
  check_password salt|  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-

Comment (by claudep):

 #19687 is a duplicate.

-- 
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.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #19414: Add a "register" class decorator for admin.

[Django]

#19414: Add a "register" class decorator for admin.
---+
 Reporter:  stavros|Owner:  BHold
 Type:  New feature|   Status:  new
Component:  contrib.admin  |  Version:  1.4
 Severity:  Normal |   Resolution:
 Keywords: | Triage Stage:  Accepted
Has patch:  1  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+

Comment (by stavros):

 Much better! I would not have added the "Unsupported arguments" check if I
 wrote it, just because someone might want to construct a dict with extra
 stuff and pass it (plus, ignoring kwargs isn't bad for you), but otherwise
 it looks great to me.

 Can someone official chime in? This looks like a very good pull request.

-- 
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.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #19687: UnsaltedMD5PasswordHasher throws exception on verify() with md5$$SALT

[Django]

#19687: UnsaltedMD5PasswordHasher throws exception on verify() with md5$$SALT
--+--
 Reporter:  twig@…|Owner:  nobody
 Type:  Bug   |   Status:  closed
Component:  contrib.auth  |  Version:  1.4
 Severity:  Normal|   Resolution:  duplicate
 Keywords:  login | Triage Stage:  Unreviewed
Has patch:  1 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  1 |UI/UX:  0
--+--
Changes (by claudep):

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


Comment:

 Duplicate of #18144

-- 
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.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #19679: Default "settings.py" does not adequately describe "SECRET_KEY"

[Django]

#19679: Default "settings.py" does not adequately describe "SECRET_KEY"
-+-
 Reporter:  retail79174@…|Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |  Version:  1.4
Component:  Core (Management |   Resolution:
  commands)  | Triage Stage:  Accepted
 Severity:  Normal   |  Needs documentation:  0
 Keywords:  settings secret key  |  Patch needs improvement:  0
Has patch:  1|UI/UX:  0
  Needs tests:  0|
Easy pickings:  1|
-+-
Changes (by aaugustin):

 * needs_better_patch:   => 0
 * needs_docs:   => 0
 * type:  Uncategorized => Cleanup/optimization
 * needs_tests:   => 0
 * stage:  Unreviewed => Accepted


Comment:

 This is fixed in my branch: https://github.com/aaugustin/django/compare
 /simplify-project-template

-- 
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.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #19688: It's not possible to use `six.with_metaclass` to subclass `models.Model` with a custom metaclass.

[Django]

#19688: It's not possible to use `six.with_metaclass` to subclass `models.Model`
with a custom metaclass.
---+-
 Reporter:  charettes  |Owner:  charettes
 Type:  Bug|   Status:  assigned
Component:  Python 3   |  Version:  master
 Severity:  Normal |   Resolution:
 Keywords: | Triage Stage:  Accepted
Has patch:  1  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+-
Changes (by aaugustin):

 * stage:  Unreviewed => Accepted


-- 
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.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #19689: Use `Options.module_name` instead of `object_name.lower()`

[Django]

#19689: Use `Options.module_name` instead of `object_name.lower()`
-+-
 Reporter:  charettes|Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |  Version:  master
Component:  ORM aggregation  |   Resolution:
 Severity:  Normal   | Triage Stage:
 Keywords:   |  Unreviewed
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by charettes):

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


Comment:

 All tests pass on Python 2.7.3 SQLite.

-- 
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.
For more options, visit https://groups.google.com/groups/opt_out.