Re: [Django] #22380: Error in GeoDjango tests example. Missing SECRET_KEY

[Django]

#22380: Error in GeoDjango tests example. Missing SECRET_KEY
-+-
 Reporter:  vlal |Owner:  vlal
 Type:   |   Status:  assigned
  Cleanup/optimization   |  Version:  master
Component:  Documentation|   Resolution:
 Severity:  Normal   | Triage Stage:
 Keywords:   |  Unreviewed
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-
Changes (by vlal):

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


Comment:

 Issued [https://github.com/django/django/pull/2514 Pull Request #2514].
 Verified documentation builds.

-- 
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/062.1e30d699a915be2a39c261febc55e8f8%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

[Django] #22380: Error in GeoDjango tests example. Missing SECRET_KEY

[Django]

#22380: Error in GeoDjango tests example. Missing SECRET_KEY
--+
 Reporter:  vlal  |  Owner:  nobody
 Type:  Cleanup/optimization  | Status:  new
Component:  Documentation |Version:  master
 Severity:  Normal|   Keywords:
 Triage Stage:  Unreviewed|  Has patch:  0
Easy pickings:  1 |  UI/UX:  0
--+
 In the documentation
 [https://docs.djangoproject.com/en/dev/ref/contrib/gis/testing/#example
 here] it outlines a barebones settings file for gis. This file fails to
 work due to the missing SECRET_KEY variable.

-- 
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/047.d99695fe09f86d81e5fe3cee6c2e3c49%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

[Django] #22379: Escaping needed during lazy reversing of non-ascii URLs

[Django]

#22379: Escaping needed during lazy reversing of non-ascii URLs
-+
 Reporter:  jnns |  Owner:  nobody
 Type:  Bug  | Status:  new
Component:  Core (URLs)  |Version:  1.6
 Severity:  Normal   |   Keywords:
 Triage Stage:  Unreviewed   |  Has patch:  0
Easy pickings:  0|  UI/UX:  0
-+
 {{{
 # urls.py
 url(ur'^umläute_in_der_url/', include('my_app.urls')),
 }}}

 Reversing the above URL with non-ascii characters returns a properly
 percent-encoded string (i.e. 'uml%C3%A4ute_in_der_url').

 But a problem occurs while passing the named URL to `reverse_lazy` because
 around line 164 in `django.utils.functional.lazy.__mod__` a string
 formatting takes place which leads to a ValueError due to the unescaped
 percent-encoding.

 > ValueError: unsupported format character 'C' (0x43)

 {{{
  return bytes(self) % rhs
 }}}

-- 
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/047.ce2db8692b17903b99ab98f99bc74d74%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

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:  Accepted
 Keywords:  oracle   |  Needs documentation:  0
Has patch:  0|  Patch needs improvement:  1
  Needs tests:  1|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by benth):

 * cc: benth (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/064.a3740b11979ca75899ba03b7c5d3ebc1%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #56: Primary key columns should be UNSIGNED

[Django]

#56: Primary key columns should be UNSIGNED
-+-
 Reporter:  Manuzhai |Owner:
 Type:  New feature  |   Status:  new
Component:  Database layer   |  Version:  master
  (models, ORM)  |   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:  mysql|  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-

Comment (by kbcmdba@…):

 MySQL 5.5.29 and up (plus other versions in other releases of MySQL) now
 require AUTO_INCREMENT columns to be UNSIGNED. The return value of
 LAST_INSERT_ID() had to change to BIGINT UNSIGNED because users who had
 BIGINT UNSIGNED column types were unable to get the ID value when the ID
 was greater than 9,223,372,036,554,775,807 (BIGINT MAX / 2 - 1 or about 9
 quintillion) but still less than the highest possible BIGINT VALUE
 (18,446,744,023,709,551,615 or about 18 quintillion).

 It no longer makes sense to allow negative AUTO_INCREMENT values by
 default in MySQL persistence layers. I strongly recommend changing the
 default data type on auto_increment columns to explicitly become UNSIGNED,
 especially when the persistence layer is known to be MySQL.

 Here's the specific MySQL 5.5.29 release note:

 * Incompatible Change: LAST_INSERT_ID(expr) did not work for expr values
 greater than the largest signed BIGINT value. Such arguments now are
 accepted, with some consequences for compatibility with previous versions:
 LAST_INSERT_ID() now returns a BIGINT UNSIGNED value, not a BIGINT
 (signed) value.
 LAST_INSERT_ID(expr) now returns an unsigned integer value, not a
 signed integer value.
 '''For AUTO_INCREMENT columns, negative values are no longer
 supported.'''
(Bug #20964, Bug #11745891)

-- 
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/085.957551c43723186119ffba90035ab377%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #20161: save errors with multiproccesing

[Django]

#20161: save errors with multiproccesing
-+-
 Reporter:  oddghost@…   |Owner:  nobody
 Type:  Uncategorized|   Status:  closed
Component:  Database layer   |  Version:  1.5
  (models, ORM)  |   Resolution:  invalid
 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
-+-

Comment (by anonymous):

 Was there a valid work around for this? I can get my code working with 2
 to 3 workers but with 3 I see the django.db.utils.DatabaseError: error
 with no message from the libpq error.   How do you close the connection
 before forking?

 I am doing something like this.  I am assuming that the update is the
 culprit because when removed it works:

 locations = Location.objects.all()

 from multiprocessing import Pool
 p = Pool(3)
 p.map(process_location, locations)

 def process_location(location):
... some processing
Location.objects.filter(pk=location_id).update(is_online=True)
 Location.objects.filter(pk=location.id).update(last_ping=loc_reporting_date)
... other processing

-- 
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/074.75b79094e80a8704f31f73b8e82d8626%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #21649: Add session signing based on the value of the user's password

[Django]

#21649: Add session signing based on the value of the user's password
-+-
 Reporter:  timo |Owner:  timo
 Type:  New feature  |   Status:  new
Component:  contrib.auth |  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Ready for
Has patch:  1|  checkin
  Needs tests:  0|  Needs documentation:  0
Easy pickings:  0|  Patch needs improvement:  0
 |UI/UX:  0
-+-
Changes (by aaugustin):

 * stage:  Accepted => 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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/062.49e0b8d7e8aa4a09c38c4e773bd3c265%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

[django/django] c28beb: Refactored and commented strip_tags utility

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: c28beb429107956f8bde8053936502124c964bec
  
https://github.com/django/django/commit/c28beb429107956f8bde8053936502124c964bec
  Author: Tomasz Wysocki 
  Date:   2014-04-03 (Thu, 03 Apr 2014)

  Changed paths:
M django/utils/html.py

  Log Message:
  ---
  Refactored and commented strip_tags utility


-- 
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/533db58abff63_42d1661d40124328%40hookshot-fe2-cp1-prd.iad.github.net.mail.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #22377: SQL Logging throws an exception when fields have utf-8 characters

[Django]

#22377: SQL Logging throws an exception when fields have utf-8 characters
-+-
 Reporter:  rolanvc@…|Owner:  nobody
 Type:  Uncategorized|   Status:  new
Component:  Database layer   |  Version:  1.6
  (models, ORM)  |   Resolution:
 Severity:  Normal   | Triage Stage:
 Keywords:  sql logging for  |  Unreviewed
  utf-8  |  Needs documentation:  0
Has patch:  0|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by claudep):

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


Comment:

 Could you please provide the full traceback? It would also be useful to
 know the values of duration, sql and params variables just before the
 crash.

-- 
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/075.61a3407fe65d5134f3acdcad4094a89b%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #22363: User provided one-off default date and datetime are not correctly serialized

[Django]

#22363: User provided one-off default date and datetime are not correctly
serialized
-+-
 Reporter:  linovia  |Owner:  charettes
 Type:  Bug  |   Status:  closed
Component:  Migrations   |  Version:
 Severity:  Release blocker  |  1.7-beta-1
 Keywords:   |   Resolution:  fixed
Has patch:  1| Triage Stage:  Ready for
  Needs tests:  0|  checkin
Easy pickings:  0|  Needs documentation:  0
 |  Patch needs improvement:  0
 |UI/UX:  0
-+-
Changes (by Simon Charette ):

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


Comment:

 In [changeset:"074d3183d92cd5ed5da8f51e7048b12a96f55e0a"]:
 {{{
 #!CommitTicketReference repository=""
 revision="074d3183d92cd5ed5da8f51e7048b12a96f55e0a"
 Fixed #22363 -- Correctly serialize `django.utils.datetime_safe` objects.

 Thanks to linovia 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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/065.9e914759b4f720c5f5ec6a504f4727e8%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

[django/django] 7b3a22: [1.7.x] Fixed #22363 -- Correctly serialize `djang...

[GitHub]

  Branch: refs/heads/stable/1.7.x
  Home:   https://github.com/django/django
  Commit: 7b3a221ad674ce74afd5db2a7dd0a0a3beb354ed
  
https://github.com/django/django/commit/7b3a221ad674ce74afd5db2a7dd0a0a3beb354ed
  Author: Simon Charette 
  Date:   2014-04-03 (Thu, 03 Apr 2014)

  Changed paths:
M django/db/migrations/writer.py
M tests/migrations/test_writer.py

  Log Message:
  ---
  [1.7.x] Fixed #22363 -- Correctly serialize `django.utils.datetime_safe` 
objects.

Thanks to linovia for the report.

Backport of 074d3183d9 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/533daf1c9abb9_490ecf1d40492af%40hookshot-fe2-cp1-prd.iad.github.net.mail.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #22363: User provided one-off default date and datetime are not correctly serialized

[Django]

#22363: User provided one-off default date and datetime are not correctly
serialized
-+-
 Reporter:  linovia  |Owner:  charettes
 Type:  Bug  |   Status:  closed
Component:  Migrations   |  Version:
 Severity:  Release blocker  |  1.7-beta-1
 Keywords:   |   Resolution:  fixed
Has patch:  1| Triage Stage:  Ready for
  Needs tests:  0|  checkin
Easy pickings:  0|  Needs documentation:  0
 |  Patch needs improvement:  0
 |UI/UX:  0
-+-

Comment (by Simon Charette ):

 In [changeset:"7b3a221ad674ce74afd5db2a7dd0a0a3beb354ed"]:
 {{{
 #!CommitTicketReference repository=""
 revision="7b3a221ad674ce74afd5db2a7dd0a0a3beb354ed"
 [1.7.x] Fixed #22363 -- Correctly serialize `django.utils.datetime_safe`
 objects.

 Thanks to linovia for the report.

 Backport of 074d3183d9 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/065.7588cd77830e33fda5931acf2e1518b3%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

[django/django] 074d31: Fixed #22363 -- Correctly serialize `django.utils....

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 074d3183d92cd5ed5da8f51e7048b12a96f55e0a
  
https://github.com/django/django/commit/074d3183d92cd5ed5da8f51e7048b12a96f55e0a
  Author: Simon Charette 
  Date:   2014-04-03 (Thu, 03 Apr 2014)

  Changed paths:
M django/db/migrations/writer.py
M tests/migrations/test_writer.py

  Log Message:
  ---
  Fixed #22363 -- Correctly serialize `django.utils.datetime_safe` objects.

Thanks to linovia 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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/533daea56b476_40d5143bd44759cf%40hookshot-fe1-cp1-prd.iad.github.net.mail.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #22378: \d in urls examples in documentation is missleading.

[Django]

#22378: \d in urls examples in documentation is missleading.
--+
 Reporter:  tomwys|Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  Documentation |  Version:  1.6
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+
Changes (by timo):

 * type:  Uncategorized => Cleanup/optimization
 * 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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/064.ea2c3b38c85dda01ff7e92b2201c6fb8%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #22378: \d in urls examples in documentation is missleading.

[Django]

#22378: \d in urls examples in documentation is missleading.
---+--
 Reporter:  tomwys |Owner:  nobody
 Type:  Uncategorized  |   Status:  new
Component:  Documentation  |  Version:  1.6
 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
---+--

Comment (by tomwys):

 Yes, using `[0-9]` is fine. It would be great to change all `\d` to
 `[0-9]` in documentation and tests related to urls.

 ie. developer without knowledge about `\d` and `re.UNICODE` used in urls
 can expect that following code ensures that digit is written to
 `/tmp/otuput`.

 {{{
 from django.conf.urls import patterns, include, url

 from django.contrib import admin
 from django.http import HttpResponse

 def view(request, arg):
 open("/tmp/output", 'w').write(arg.encode('utf-8'))
 return HttpResponse(arg)

 urlpatterns = patterns('',
 url(r'^(\d)/$', view),
 )
 }}}

 This is not true for `localhost:8000/१/` (tested on cPython 2.7.5 and
 Django master). If developer assume that file (or other storage like
 radius, cache etc.) contains digit, but this is not true, it could cause
 errors (or even security issues in extreme cases) in the future.

 Also, even if it is passed to `int(...)` and converted to integer that
 way, it creates multiple valid urls for single resource, without developer
 knowing about it. This is minor, but unwanted behavior.


  (and it is not easy to discover, most of Django developers are puzzled
 when I talk with them about this problem

-- 
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.629b12f973ae142acac035ceb1e842c4%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

[django/django] 0f6ea6: Cleaned up string detection for a deprecation warn...

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 0f6ea69e275fe5ed75479d69b0a233be9ae4fd76
  
https://github.com/django/django/commit/0f6ea69e275fe5ed75479d69b0a233be9ae4fd76
  Author: Tim Graham 
  Date:   2014-04-03 (Thu, 03 Apr 2014)

  Changed paths:
M django/conf/urls/i18n.py

  Log Message:
  ---
  Cleaned up string detection for a deprecation warning by using 
six.string_types.


-- 
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/533d78bf8c1eb_422d5c9d3894743%40hookshot-fe2-cp1-prd.iad.github.net.mail.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #22378: \d in urls examples in documentation is missleading.

[Django]

#22378: \d in urls examples in documentation is missleading.
---+--
 Reporter:  tomwys |Owner:  nobody
 Type:  Uncategorized  |   Status:  new
Component:  Documentation  |  Version:  1.6
 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
---+--

Comment (by aaugustin):

 I think the suggestion is simply to use `[0-9]` which is unambiguous even
 in an unicode world.

-- 
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.f05749f7c5845f9273b1f430b1f48911%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

[django/django] 8f6384: Fixed typo in 1.8 release notes.

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 8f63849df28449e916336a11cbbe7abf8ca03d42
  
https://github.com/django/django/commit/8f63849df28449e916336a11cbbe7abf8ca03d42
  Author: Tim Graham 
  Date:   2014-04-03 (Thu, 03 Apr 2014)

  Changed paths:
M docs/releases/1.8.txt

  Log Message:
  ---
  Fixed typo in 1.8 release notes.


-- 
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/533d6087b74b6_41c4567d4063190%40hookshot-fe2-cp1-prd.iad.github.net.mail.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #22378: \d in urls examples in documentation is missleading.

[Django]

#22378: \d in urls examples in documentation is missleading.
---+--
 Reporter:  tomwys |Owner:  nobody
 Type:  Uncategorized  |   Status:  new
Component:  Documentation  |  Version:  1.6
 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 timo):

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


Comment:

 Could you elaborate a bit on the problem and what change you think we
 should make? When I try your example with something like `articles/१/`,
 the value passed to the view is "1". If there are security implications
 you should report them privately per
 https://docs.djangoproject.com/en/1.6/internals/security/#reporting-
 security-issues. Thanks.

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To 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.56eaf800aa457b931b2859c353c556b0%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #22363: User provided one-off default date and datetime are not correctly serialized

[Django]

#22363: User provided one-off default date and datetime are not correctly
serialized
-+-
 Reporter:  linovia  |Owner:  charettes
 Type:  Bug  |   Status:  assigned
Component:  Migrations   |  Version:
 Severity:  Release blocker  |  1.7-beta-1
 Keywords:   |   Resolution:
Has patch:  1| Triage Stage:  Ready for
  Needs tests:  0|  checkin
Easy pickings:  0|  Needs documentation:  0
 |  Patch needs improvement:  0
 |UI/UX:  0
-+-
Changes (by timo):

 * stage:  Accepted => 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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/065.32a1eb77bda4d9f39753c36ebf04fe91%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #22372: Incorrect docstring in wizard views

[Django]

#22372: Incorrect docstring in wizard views
--+
 Reporter:  simon29   |Owner:  vlal
 Type:  Cleanup/optimization  |   Status:  closed
Component:  Forms |  Version:  1.6
 Severity:  Normal|   Resolution:  fixed
 Keywords:| Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  1 |UI/UX:  0
--+

Comment (by Tim Graham ):

 In [changeset:"1cce00a7620f1882b3b1999e799eb1d3cc65c1ca"]:
 {{{
 #!CommitTicketReference repository=""
 revision="1cce00a7620f1882b3b1999e799eb1d3cc65c1ca"
 [1.6.x] Fixed #22372 -- Improved description of
 WizardView.get_context_data().

 Thanks simon29 for the report.

 Backport of a8e2ec0e82 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/065.64b9dfb28a17e457d75adf3dc1ff8373%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

[django/django] 1cce00: [1.6.x] Fixed #22372 -- Improved description of Wi...

[GitHub]

  Branch: refs/heads/stable/1.6.x
  Home:   https://github.com/django/django
  Commit: 1cce00a7620f1882b3b1999e799eb1d3cc65c1ca
  
https://github.com/django/django/commit/1cce00a7620f1882b3b1999e799eb1d3cc65c1ca
  Author: Vishal Lal 
  Date:   2014-04-03 (Thu, 03 Apr 2014)

  Changed paths:
M django/contrib/formtools/wizard/views.py
M docs/ref/contrib/formtools/form-wizard.txt

  Log Message:
  ---
  [1.6.x] Fixed #22372 -- Improved description of WizardView.get_context_data().

Thanks simon29 for the report.

Backport of a8e2ec0e82 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/533d53d7e6db7_4b9b6d3d3c60963%40hookshot-fe1-cp1-prd.iad.github.net.mail.
For more options, visit https://groups.google.com/d/optout.

[django/django] a8e2ec: Fixed #22372 -- Improved description of WizardView...

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: a8e2ec0e82aaebfa53a8074581b22849896537df
  
https://github.com/django/django/commit/a8e2ec0e82aaebfa53a8074581b22849896537df
  Author: Vishal Lal 
  Date:   2014-04-03 (Thu, 03 Apr 2014)

  Changed paths:
M django/contrib/formtools/wizard/views.py
M docs/ref/contrib/formtools/form-wizard.txt

  Log Message:
  ---
  Fixed #22372 -- Improved description of WizardView.get_context_data().

Thanks simon29 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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/533d53c3e1bd9_4c581203d38528af%40hookshot-fe1-cp1-prd.iad.github.net.mail.
For more options, visit https://groups.google.com/d/optout.

[django/django] 28a686: [1.7.x] Fixed #22372 -- Improved description of Wi...

[GitHub]

  Branch: refs/heads/stable/1.7.x
  Home:   https://github.com/django/django
  Commit: 28a686a0b75e118a4a24462f3b3d31c8231f010a
  
https://github.com/django/django/commit/28a686a0b75e118a4a24462f3b3d31c8231f010a
  Author: Vishal Lal 
  Date:   2014-04-03 (Thu, 03 Apr 2014)

  Changed paths:
M django/contrib/formtools/wizard/views.py
M docs/ref/contrib/formtools/form-wizard.txt

  Log Message:
  ---
  [1.7.x] Fixed #22372 -- Improved description of WizardView.get_context_data().

Thanks simon29 for the report.

Backport of a8e2ec0e82 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/533d53d7cd500_51c411d3d40471de%40hookshot-fe1-cp1-prd.iad.github.net.mail.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #22372: Incorrect docstring in wizard views

[Django]

#22372: Incorrect docstring in wizard views
--+
 Reporter:  simon29   |Owner:  vlal
 Type:  Cleanup/optimization  |   Status:  closed
Component:  Forms |  Version:  1.6
 Severity:  Normal|   Resolution:  fixed
 Keywords:| Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  1 |UI/UX:  0
--+
Changes (by Tim Graham ):

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


Comment:

 In [changeset:"a8e2ec0e82aaebfa53a8074581b22849896537df"]:
 {{{
 #!CommitTicketReference repository=""
 revision="a8e2ec0e82aaebfa53a8074581b22849896537df"
 Fixed #22372 -- Improved description of WizardView.get_context_data().

 Thanks simon29 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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/065.709258cbc03de09771683c0bbc5f7d18%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

[django/django] d73d0e: Fixed #22218 -- Deprecated django.conf.urls.patter...

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: d73d0e071c1b4c86d57994a0ab55a74cfe80cdf5
  
https://github.com/django/django/commit/d73d0e071c1b4c86d57994a0ab55a74cfe80cdf5
  Author: Tim Graham 
  Date:   2014-04-03 (Thu, 03 Apr 2014)

  Changed paths:
M django/conf/project_template/project_name/urls.py
M django/conf/urls/__init__.py
M django/conf/urls/i18n.py
M django/conf/urls/static.py
M django/contrib/admin/options.py
M django/contrib/admin/sites.py
M django/contrib/admindocs/urls.py
M django/contrib/auth/admin.py
M django/contrib/auth/tests/urls.py
M django/contrib/auth/tests/urls_admin.py
M django/contrib/auth/urls.py
M django/contrib/flatpages/tests/urls.py
M django/contrib/flatpages/urls.py
M django/contrib/formtools/tests/urls.py
M django/contrib/formtools/tests/wizard/namedwizardtests/urls.py
M django/contrib/formtools/tests/wizard/wizardtests/urls.py
M django/contrib/gis/tests/geoadmin/urls.py
M django/contrib/gis/tests/geoapp/urls.py
M django/contrib/messages/tests/urls.py
M django/contrib/sitemaps/tests/urls/http.py
M django/contrib/sitemaps/tests/urls/https.py
M docs/howto/static-files/index.txt
M docs/internals/deprecation.txt
M docs/intro/overview.txt
M docs/intro/tutorial03.txt
M docs/intro/tutorial04.txt
M docs/ref/class-based-views/base.txt
M docs/ref/class-based-views/generic-date-based.txt
M docs/ref/class-based-views/generic-display.txt
M docs/ref/class-based-views/index.txt
M docs/ref/contrib/admin/index.txt
M docs/ref/contrib/flatpages.txt
M docs/ref/contrib/formtools/form-wizard.txt
M docs/ref/contrib/gis/tutorial.txt
M docs/ref/contrib/sitemaps.txt
M docs/ref/contrib/staticfiles.txt
M docs/ref/contrib/syndication.txt
M docs/ref/urls.txt
M docs/ref/views.txt
M docs/releases/1.8.txt
M docs/spelling_wordlist
M docs/topics/cache.txt
M docs/topics/class-based-views/generic-display.txt
M docs/topics/class-based-views/generic-editing.txt
M docs/topics/class-based-views/index.txt
M docs/topics/class-based-views/intro.txt
M docs/topics/class-based-views/mixins.txt
M docs/topics/http/urls.txt
M docs/topics/i18n/translation.txt
M tests/admin_changelist/urls.py
M tests/admin_custom_urls/models.py
M tests/admin_custom_urls/urls.py
M tests/admin_docs/urls.py
M tests/admin_inlines/urls.py
M tests/admin_scripts/urls.py
M tests/admin_views/admin.py
M tests/admin_views/customadmin.py
M tests/admin_views/urls.py
M tests/admin_widgets/urls.py
M tests/conditional_processing/urls.py
M tests/contenttypes_tests/urls.py
M tests/context_processors/urls.py
M tests/file_storage/urls.py
M tests/file_uploads/urls.py
M tests/forms_tests/urls.py
M tests/generic_inline_admin/urls.py
M tests/generic_views/urls.py
M tests/handlers/urls.py
M tests/i18n/patterns/urls/default.py
M tests/i18n/patterns/urls/disabled.py
M tests/i18n/patterns/urls/included.py
M tests/i18n/patterns/urls/namespace.py
M tests/i18n/patterns/urls/path_unused.py
M tests/i18n/patterns/urls/wrong.py
M tests/i18n/patterns/urls/wrong_namespace.py
M tests/i18n/urls.py
M tests/logging_tests/urls.py
M tests/middleware/cond_get_urls.py
M tests/middleware/extra_urls.py
M tests/middleware/urls.py
M tests/middleware_exceptions/urls.py
M tests/model_permalink/urls.py
M tests/proxy_models/urls.py
M tests/resolve_url/urls.py
M tests/servers/urls.py
M tests/staticfiles_tests/urls/default.py
M tests/syndication_tests/urls.py
M tests/template_tests/alternate_urls.py
M tests/template_tests/urls.py
M tests/test_client/urls.py
M tests/test_client_regress/urls.py
M tests/test_utils/tests.py
M tests/test_utils/urls.py
M tests/timezones/urls.py
M tests/urlpatterns_reverse/erroneous_urls.py
M tests/urlpatterns_reverse/extra_urls.py
M tests/urlpatterns_reverse/included_named_urls.py
M tests/urlpatterns_reverse/included_named_urls2.py
M tests/urlpatterns_reverse/included_namespace_urls.py
M tests/urlpatterns_reverse/included_no_kwargs_urls.py
M tests/urlpatterns_reverse/included_urls.py
M tests/urlpatterns_reverse/included_urls2.py
M tests/urlpatterns_reverse/named_urls.py
M tests/urlpatterns_reverse/namespace_urls.py
M tests/urlpatterns_reverse/reverse_lazy_urls.py
M tests/urlpatterns_reverse/urlconf_inner.py
M tests/urlpatterns_reverse/urlconf_outer.py
M tests/urlpatterns_reverse/urls.py
M tests/urlpatterns_reverse/urls_error_handlers.py
M tests/urlpatterns_reverse/urls_error_handlers_callables.py
M tests/urlpatterns_reverse/urls_without_full_import.py
M tests/urls.py
M tests/view_tests/default_urls.py
M tests/view_tests/generic_urls.py
M tests/view_tests/regression_21530_urls.py

Re: [Django] #22218: Deprecate 'prefix' arg to django.conf.urls.patterns

[Django]

#22218: Deprecate 'prefix' arg to django.conf.urls.patterns
--+
 Reporter:  carljm|Owner:  timo
 Type:  Cleanup/optimization  |   Status:  closed
Component:  Core (URLs)   |  Version:  master
 Severity:  Normal|   Resolution:  fixed
 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 Tim Graham ):

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


Comment:

 In [changeset:"d73d0e071c1b4c86d57994a0ab55a74cfe80cdf5"]:
 {{{
 #!CommitTicketReference repository=""
 revision="d73d0e071c1b4c86d57994a0ab55a74cfe80cdf5"
 Fixed #22218 -- Deprecated django.conf.urls.patterns.

 Thanks Carl Meyer for the suggestion and Alex Gaynor and Carl for reviews.
 }}}

-- 
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.f88d1afd8cf6eb9342ee4fd07f5f83c4%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

[Django] #22378: \d in urls examples in documentation is missleading.

[Django]

#22378: \d in urls examples in documentation is missleading.
---+
 Reporter:  tomwys |  Owner:  nobody
 Type:  Uncategorized  | Status:  new
Component:  Documentation  |Version:  1.6
 Severity:  Normal |   Keywords:
 Triage Stage:  Unreviewed |  Has patch:  0
Easy pickings:  0  |  UI/UX:  0
---+
 \d with re.UNICODE flag allows to use digits like "१". This flag is used
 when parsing Django urls.

 For example, regexp like that
 (https://docs.djangoproject.com/en/dev/topics/http/urls/#example):

 {{{
  url(r'^articles/(\d{4})/$', 'news.views.year_archive'),
 }}}

 will accept "articles//". This is missleading for developer. It could
 also be harmful. If developer will use string parsed like that in other
 way than parsing to int(), it could lead to error or even security 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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/049.bd937d722c6dd445b7a96c7ef4b8181c%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

[Django] #22377: SQL Logging throws an exception when fields have utf-8 characters

[Django]

#22377: SQL Logging throws an exception when fields have utf-8 characters
--+
 Reporter:  rolanvc@… |  Owner:  nobody
 Type:  Uncategorized | Status:  new
Component:  Database layer (models, ORM)  |Version:  1.6
 Severity:  Normal|   Keywords:  sql logging
 Triage Stage:  Unreviewed|  for utf-8
Easy pickings:  0 |  Has patch:  0
  |  UI/UX:  0
--+
 In django/db/backends/util.py, in CursorDebugWrapper.execute, the line:

  logger.debug('(%.3f) %s; args=%s' % (duration, sql, params),
 extra={'duration': duration, 'sql': sql, 'params': params}
 )

 throws a "UnicodeDecodeError:ascii codec  " when calling model.save()
 when some fields have utf-8/non-ascii values.  My only workaround is to
 modify it to:

  logger.debug('(%.3f) %s; args=%s' % (duration, sql.decode('utf-8'),
 params),
 extra={'duration': duration, 'sql': sql, 'params': params}
 )

 I'm hoping there's a better and more elegant way that I could use.

 Thanks!
 =)

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To 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/060.4543d56984ad8837057c55386e9beae8%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.