Re: [Django] #26470: Checks performed during Permission creation should use the check framework.

[Django]

#26470: Checks performed during Permission creation should use the check 
framework.
-+-
 Reporter:  charettes|Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |
Component:  contrib.auth |  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:
 |  Unreviewed
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by charettes):

 * has_patch:  0 => 1


Comment:

 https://github.com/django/django/pull/6421

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/067.cfa934d20fb2e6db2ffe76f03a70ab3b%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

[Django] #26470: Checks performed during Permission creation should use the check framework.

[Django]

#26470: Checks performed during Permission creation should use the check 
framework.
+
   Reporter:  charettes |  Owner:  nobody
   Type:  Cleanup/optimization  | Status:  new
  Component:  contrib.auth  |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 |
+
 The `django.contrib.auth.management.check_permission` function that is
 connected to the `post_migrate` signal performs static model analysis
 checks that should rely on the check framework. At the moment a
 `ValidationError` or a `CommandError` is raised when a check fails.

 The checks performed are the following:

 1. Check that custom permissions don't clash with built-ins and are not
 duplicated;
 2. Check that models `verbose_name` doesn't exceed a certain length based
 on the `Permission.name.max_length`;
 3. Check that permissions `name` doesn't exceed a certain length based on
 the `Permission.name.max_length`.

 For `2.` and `3.` I suggest we make them issue a `check.Warning` with a
 message noting that the name will be truncated to N characters instead of
 crashing with an `IntegrityError` if the check is ignored/disabled.

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

Re: [Django] #26458: The Avg aggregate should only automatically resolves its output field to FloatField on numeric sources

[Django]

#26458: The Avg aggregate should only automatically resolves its output field to
FloatField on numeric sources
-+-
 Reporter:  charettes|Owner:  nobody
 Type:   |   Status:  closed
  Cleanup/optimization   |
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:  fixed
 Keywords:   | Triage Stage:  Ready for
 |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Simon Charette ):

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


Comment:

 In [changeset:"a6074e8908e36286de7e31f165be801df8ee1eab" a6074e89]:
 {{{
 #!CommitTicketReference repository=""
 revision="a6074e8908e36286de7e31f165be801df8ee1eab"
 Fixed #26458 -- Based Avg's default output_field resolution on its source
 field type.

 Thanks Tim for the review and Josh for the input.
 }}}

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/067.fa3bddf4a92057ad73a6c2c5a2314430%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #26468: Bug in models.functions.ConcatPair for sqlite

[Django]

#26468: Bug in models.functions.ConcatPair for sqlite
-+-
 Reporter:  jerch|Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Database layer   |  Version:  1.8
  (models, ORM)  |
 Severity:  Normal   |   Resolution:  needsinfo
 Keywords:  sqlite concat| Triage Stage:
 |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by charettes):

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


Comment:

 Please reopen if you can provide more details about your Django, Python
 and SQLite3 version (`import sqlite3; sqlite3.version`).

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/063.c36ad8a615d5433fb35d972bb3d8d79c%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #26401: Allow auth machinery to be used without installing auth app

[Django]

#26401: Allow auth machinery to be used without installing auth app
--+
 Reporter:  satchamo  |Owner:  satchamo
 Type:  Bug   |   Status:  assigned
Component:  contrib.auth  |  Version:  1.9
 Severity:  Normal|   Resolution:
 Keywords:  auth  | Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  1 |UI/UX:  0
--+
Changes (by jdufresne):

 * has_patch:  0 => 1


Comment:

 https://github.com/django/django/pull/6420

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/066.687a34b0d69b219a71879192378cb70f%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #26448: Improve docs for running tests using a different database

[Django]

#26448: Improve docs for running tests using a different database
--+
 Reporter:  aschn |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  closed
Component:  Documentation |  Version:  1.9
 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:  new => closed
 * resolution:   => fixed


Comment:

 In [changeset:"361cb7a857f1ca69754c0e3a0038097d09508f2c" 361cb7a]:
 {{{
 #!CommitTicketReference repository=""
 revision="361cb7a857f1ca69754c0e3a0038097d09508f2c"
 Fixed #26448 -- Added details for running tests with a different database
 backend.
 }}}

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/063.90020e368bf3abba5ced56fcd9dbbd10%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #26464: Addition to the "Security in Django": Incremental URLs/Identifiers

[Django]

#26464: Addition to the "Security in Django": Incremental URLs/Identifiers
---+--
 Reporter:  CrazyPython|Owner:  nobody
 Type:  New feature|   Status:  new
Component:  Documentation  |  Version:  1.9
 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 timgraham):

 * easy:  1 => 0


Comment:

 I've raised some ideas about this on the
 [https://groups.google.com/d/topic/django-
 developers/_Z6ZufcOmps/discussion django-developers mailing list].

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

Re: [Django] #26468: Bug in models.functions.ConcatPair for sqlite

[Django]

#26468: Bug in models.functions.ConcatPair for sqlite
-+-
 Reporter:  jerch|Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  1.8
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  sqlite concat| Triage Stage:
 |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by jarshwah):

 Can't reproduce on stable 1.8 or 1.9 either.

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/063.7010edc33da9dc1aadbd71295c9de7eb%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #26468: Bug in models.functions.ConcatPair for sqlite

[Django]

#26468: Bug in models.functions.ConcatPair for sqlite
-+-
 Reporter:  jerch|Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  1.8
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  sqlite concat| Triage Stage:
 |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by jarshwah):

 * cc: josh.smeaton@… (added)


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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/063.602ce016e05ae1099526040b9d715704%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #26468: Bug in models.functions.ConcatPair for sqlite

[Django]

#26468: Bug in models.functions.ConcatPair for sqlite
-+-
 Reporter:  jerch|Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  1.8
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  sqlite concat| Triage Stage:
 |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by jarshwah):

 I can't reproduce:

 {{{
 In [6]: from django.db import connection

 In [7]: connection.vendor
 Out[7]: u'sqlite'

 In [8]: concat = Concat(F('name'), Value('-'), F('motto'),
 output_field=CharField())

 In [9]: Company.objects.annotate(concat=concat).first().concat
 Out[9]: u'HI-'

 In [10]: concat = Concat(F('name'), Value('"-"'), F('motto'),
 output_field=CharField())

 In [11]: Company.objects.annotate(concat=concat).first().concat
 Out[11]: u'HI"-"'

 In [12]: import django

 In [13]: django.get_version()
 Out[13]: '1.10.dev20160401110429'
 }}}

 Note that I tried both Value('"-"') and Value('-'). You shouldn't be
 injecting quotes into Value, it'll take care of itself.

 Can you please post the full queryset you're running that generates the
 error, and also print the underlying query of the queryset, like this:

 {{{
 qs = Model.objects.whatever()
 print(qs.query)
 }}}

 Also, what version of Django are you using? Can you reproduce on 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/063.47753ab73ef7b1987a069641ae0c7a36%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #26448: Improve docs for running tests using a different database

[Django]

#26448: Improve docs for running tests using a different database
--+
 Reporter:  aschn |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  Documentation |  Version:  1.9
 Severity:  Normal|   Resolution:
 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 timgraham):

 * has_patch:  0 => 1


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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/063.8efc54bfdd9fe4581d69e1f6f7e2ad0a%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #26469: FieldFile.open() does not properly set mode when opening file

[Django]

#26469: FieldFile.open() does not properly set mode when opening file
-+-
 Reporter:  george_edison|Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Database layer   |  Version:  1.9
  (models, ORM)  |
 Severity:  Normal   |   Resolution:  duplicate
 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 timgraham):

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


Comment:

 Duplicate of #26398. This should be fixed in 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/071.e05ebfedf37104351e740ba3345df816%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #26465: Contributing to Django:: Link text is not english

[Django]

#26465: Contributing to Django:: Link text is not english
-+-
 Reporter:  kaifeldhoff  |Owner:  nobody
 Type:   |   Status:  closed
  Cleanup/optimization   |
Component:  Documentation|  Version:  1.9
 Severity:  Normal   |   Resolution:  invalid
 Keywords:   | Triage Stage:
 |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by timgraham):

 Our efforts to fix the search results are tracked in
 https://github.com/django/djangoproject.com/issues/621. I just merged
 another commit that may help (adding ``).

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

Re: [Django] #26201: Document the consequences of rotating the CSRF token on login

[Django]

#26201: Document the consequences of rotating the CSRF token on login
--+
 Reporter:  wimfeijen |Owner:  vehrlich
 Type:  Cleanup/optimization  |   Status:  closed
Component:  Documentation |  Version:  1.8
 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
--+

Comment (by Tim Graham ):

 In [changeset:"147f9a0d2a31a90df413158ecaa7778a1f21e281" 147f9a0d]:
 {{{
 #!CommitTicketReference repository=""
 revision="147f9a0d2a31a90df413158ecaa7778a1f21e281"
 [1.9.x] Fixed #26201 -- Documented the consequences of rotating the CSRF
 token on login.

 Backport of 369fa471f46cd517edf5fc82e4ef6138de3cff6 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/067.dc9a677e21f76fd12a506e39c5c7b3b1%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #26467: Broken link on WindowsInstall page of wiki

[Django]

#26467: Broken link on WindowsInstall page of wiki
-+-
 Reporter:  CrazyPython  |Owner:  nobody
 Type:   |   Status:  closed
  Cleanup/optimization   |
Component:  Uncategorized|  Version:  1.9
 Severity:  Normal   |   Resolution:  invalid
 Keywords:   | Triage Stage:
 |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-
Changes (by timgraham):

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


Comment:

 The wiki isn't part of the official documentation but feel free to edit it
 as you see fit.

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

Re: [Django] #26468: Bug in models.functions.ConcatPair for sqlite

[Django]

#26468: Bug in models.functions.ConcatPair for sqlite
-+-
 Reporter:  jerch|Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  1.8
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  sqlite concat| Triage Stage:
 |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by jerch):

 * keywords:   => sqlite concat
 * component:  Uncategorized => Database layer (models, ORM)


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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/063.62a4c83bf892193c2cf23eac9354f737%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

[Django] #26469: FieldFile.open() does not properly set mode when opening file

[Django]

#26469: FieldFile.open() does not properly set mode when opening file
--+
 Reporter:  george_edison |  Owner:  nobody
 Type:  Bug   | Status:  new
Component:  Database layer (models, ORM)  |Version:  1.9
 Severity:  Normal|   Keywords:
 Triage Stage:  Unreviewed|  Has patch:  0
Easy pickings:  0 |  UI/UX:  0
--+
 Consider the following model definition:

 {{{
 class Thing(models.Model):
 file = models.FileField(upload_to="things")
 }}}

 Let's suppose I have an existing model instance and I want to open the
 file for writing:

 {{{
 t = Thing.objects.get(pk=1)
 t.file.open('wb')
 t.file.write(data)
 }}}

 This raises an unexpected exception:

 {{{
 IOError: File not open for writing
 }}}

 Here's the source code for `FieldFile.open()`:

 {{{
 def open(self, mode='rb'):
 self._require_file()
 self.file.open(mode)
 }}}

 The second line in the body accesses `self.file` - a property which is
 defined as follows:

 {{{
 def _get_file(self):
 self._require_file()
 if not hasattr(self, '_file') or self._file is None:
 self._file = self.storage.open(self.name, 'rb')
 return self._file

 # ...

 file = property(_get_file, ...
 }}}

 If `self._file` is `None` (which is the case in my example above), the
 storage backend is then instructed to open the file with mode 'rb' instead
 of the mode that was originally passed to `FieldFile.open()`. The newly
 opened `File` instance is returned and control resumes in
 `FieldFile.open()` which invokes the `open()` method on the `File`
 instance.

 Here are the first few lines of `File.open()`:

 {{{
 def open(self, mode=None):
 if not self.closed:
 self.seek(0)
 elif self.name and os.path.exists(self.name):
 self.file = open(self.name, mode or self.mode)
 # ...
 }}}

 Since the file is already open, `not self.closed` evaluates to `True` and
 the file remains open in read-only mode. It is not possible to write to
 the file.

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

Re: [Django] #26468: Bug in models.functions.ConcatPair for sqlite

[Django]

#26468: Bug in models.functions.ConcatPair for sqlite
---+--
 Reporter:  jerch  |Owner:  nobody
 Type:  Bug|   Status:  new
Component:  Uncategorized  |  Version:  1.8
 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 jerch):

 I tried to concat to db fields into one output column like this:

 {{{
 expr = Concat(models.F('field1'), models.Value('"-"'), models.F('field2'),
 outputfield=models.CharField())
 }}}

 Expected output: 'value_from_field_1-value_from_field_2'

 Instead I just got an invalid syntax sql error.

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/063.eed17c92c27c3c50d39b3ee6293a76c2%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #26468: Bug in models.functions.ConcatPair for sqlite

[Django]

#26468: Bug in models.functions.ConcatPair for sqlite
---+--
 Reporter:  jerch  |Owner:  nobody
 Type:  Bug|   Status:  new
Component:  Uncategorized  |  Version:  1.8
 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 shaib):

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


Comment:

 When you say "not working for me" -- what did you give as inputs, what did
 you expect to happen and what happened instead?

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/063.8c301d671015f583fc46f17d18c22f5e%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

[Django] #26468: Bug in models.functions.ConcatPair for sqlite

[Django]

#26468: Bug in models.functions.ConcatPair for sqlite
---+
 Reporter:  jerch  |  Owner:  nobody
 Type:  Bug| Status:  new
Component:  Uncategorized  |Version:  1.8
 Severity:  Normal |   Keywords:
 Triage Stage:  Unreviewed |  Has patch:  0
Easy pickings:  0  |  UI/UX:  0
---+
 Concat is not working for me due to this line in
 models.functions.ConcatPair.coalesce:

 {{{
 Coalesce(expression, Value('')) for expression in
 c.get_source_expressions()
 }}}

 With a minor change it works as intended:

 {{{
 Coalesce(expression, Value('""')) for expression in
 c.get_source_expressions()
 }}}

 Tested with Django 1.8.12 under Ubuntu with sqlite 3.8.2-1ubuntu2.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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/048.6ea0ba136c7f3d517b777d00338576e1%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #26465: Contributing to Django:: Link text is not english

[Django]

#26465: Contributing to Django:: Link text is not english
-+-
 Reporter:  kaifeldhoff  |Owner:  nobody
 Type:   |   Status:  closed
  Cleanup/optimization   |
Component:  Documentation|  Version:  1.9
 Severity:  Normal   |   Resolution:  invalid
 Keywords:   | Triage Stage:
 |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by aaugustin):

 This is another instance of "we messed up the SEO and Google cannot figure
 out that our doc pages are translations (not always complete) of the same
 content".

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

Re: [Django] #26448: Improve docs for running tests using a different database

[Django]

#26448: Improve docs for running tests using a different database
--+
 Reporter:  aschn |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  Documentation |  Version:  1.9
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  1 |UI/UX:  0
--+

Comment (by krisys):

 Greetings,

 aschn and timgraham, I just updated the documentation to reflect the
 suggestions and I have created a pull request for the same -
 https://github.com/django/django/pull/6418

 Thank you.

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/063.d8a0ccf9b17a48a97030b9fb4f2cc674%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #23422: Cannot add Permission to Group in data migration

[Django]

#23422: Cannot add Permission to Group in data migration
+--
 Reporter:  tjwalch |Owner:  nobody
 Type:  Bug |   Status:  closed
Component:  Migrations  |  Version:  1.7
 Severity:  Normal  |   Resolution:  wontfix
 Keywords:  | Triage Stage:  Unreviewed
Has patch:  0   |  Needs documentation:  1
  Needs tests:  0   |  Patch needs improvement:  0
Easy pickings:  0   |UI/UX:  0
+--

Comment (by charettes):

 FWIW I started to work on this issue (which is related to #24100 to
 #24067) on [https://github.com/django/django/compare/master...charettes
 :migration-signals-refactor a branch].

 The plan here is to make the `pre_migrate` signal dispatch it's plan
 (#24100) and inject `CreatePermision` operations after `CreateContentType`
 operations (that are injected after `CreateModel` operations just like
 `RenameContentType` operations are meant to be injected after
 `RenameModel` operations in order to solve #24067).

 I'll try to get this into 1.10.

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

Re: [Django] #26465: Contributing to Django:: Link text is not english

[Django]

#26465: Contributing to Django:: Link text is not english
-+-
 Reporter:  kaifeldhoff  |Owner:  nobody
 Type:   |   Status:  closed
  Cleanup/optimization   |
Component:  Documentation|  Version:  1.9
 Severity:  Normal   |   Resolution:  invalid
 Keywords:   | Triage Stage:
 |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by kaifeldhoff):

 Ups, yes you are right.

 I quickly searched "contribute django" in Google, and the first hit was
 [https://docs.djangoproject.com/es/1.9/internals/contributing/]. With only
 one obvious Spanish contect I had no idea to check the link.

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

Re: [Django] #26464: Addition to the "Security in Django": Incremental URLs/Identifiers

[Django]

#26464: Addition to the "Security in Django": Incremental URLs/Identifiers
---+--
 Reporter:  CrazyPython|Owner:  nobody
 Type:  New feature|   Status:  new
Component:  Documentation  |  Version:  1.9
 Severity:  Normal |   Resolution:
 Keywords: | Triage Stage:  Unreviewed
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  1  |UI/UX:  0
---+--

Comment (by CrazyPython):

 > It includes advice on securing a Django-powered site.

 Maybe include it in "Additional security Topics"?

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

[Django] #26467: Broken link on WindowsInstall page of wiki

[Django]

#26467: Broken link on WindowsInstall page of wiki
--+
 Reporter:  CrazyPython   |  Owner:  nobody
 Type:  Cleanup/optimization  | Status:  new
Component:  Uncategorized |Version:  1.9
 Severity:  Normal|   Keywords:
 Triage Stage:  Unreviewed|  Has patch:  0
Easy pickings:  1 |  UI/UX:  0
--+
 It needs to be replaced with another guide or maybe a link to the Wayback
 Machine.
 
(https://web.archive.org/web/20130217221333/http://wiki.thinkhole.org/howto:django_on_windows).
 I'm not sure if this is the correct place to post 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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/054.39b6361448a39db7b616cad8abb2b240%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #26466: set_language with next unset and a urlencoded HTTP_REFERER fails redirection

[Django]

#26466: set_language with next unset and a urlencoded HTTP_REFERER fails
redirection
--+
 Reporter:  miikkas   |Owner:  miikkas
 Type:  Bug   |   Status:  assigned
Component:  Internationalization  |  Version:  1.9
 Severity:  Normal|   Resolution:
 Keywords:  set_language  | Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+
Description changed by miikkas:

Old description:

> POSTing to `set_language` when `next` is not set causes Django to user
> HTTP_REFERER instead. If the URL in HTTP_REFERER is urlencoded, the
> resulting redirection will fail.
>
> The bug is caused by the call to `translate_url` function in
> `set_language`. `translate_url` passes the URL on to `reverse`, which
> assumes URLs that are not urlencoding, thus resulting in a double
> urlencoded URL, which obviously will not work. Non-urlencoded URLs in
> HTTP_REFERER work correctly.
>
> An easy way to test this is to have a view with a URL with unicode
> characters in it and use the translation selector widget provided in the
> i18n docs, but with the `redirect_to` context variable undefined, which
> is the way I found the bug.
>
> AFAIK there's no standard about whether the browser should encode the URL
> in HTTP_REFERER, but most of the new browsers do so anyway. The bug
> should be easy to fix, thus, by just decoding the string in HTTP_REFERER
> – if it was encoded, it will now be unencoded, if it was '''not'''
> encoded, it will be unchanged (disregarding a corner case of ambiguous
> URLs with substrings like `%C3%A4` verbatim with browsers that don't
> encode the URLs). I'll make a pull request within a few days.

New description:

 POSTing to `set_language` when `next` is not set causes Django to use
 HTTP_REFERER instead. If the URL in HTTP_REFERER is urlencoded, the
 resulting redirection will fail.

 The bug is caused by the call to `translate_url` function in
 `set_language`. `translate_url` passes the URL on to `reverse`, which
 assumes URLs that are not urlencoded, thus resulting in a double
 urlencoded URL, which obviously will not work. Non-urlencoded URLs in
 HTTP_REFERER work correctly.

 An easy way to test this is to have a view with a URL with unicode
 characters in it and use the translation selector widget provided in the
 i18n docs, but with the `redirect_to` context variable undefined –
 basically the way I found this bug.

 AFAIK there's no standard about whether the browser should encode the URL
 in HTTP_REFERER, but most of the new browsers do so anyway. The bug should
 be easy to fix, thus, by just decoding the string in HTTP_REFERER – if it
 was encoded, it will now be unencoded, if it was '''not''' encoded, it
 will be unchanged (disregarding a corner case of ambiguous URLs with
 substrings like `%C3%A4` verbatim with browsers that don't encode the
 URLs). I'll make a pull request within a few days.

--

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

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

Re: [Django] #26466: set_language with next unset and a urlencoded HTTP_REFERER fails redirection

[Django]

#26466: set_language with next unset and a urlencoded HTTP_REFERER fails
redirection
--+
 Reporter:  miikkas   |Owner:  miikkas
 Type:  Bug   |   Status:  assigned
Component:  Internationalization  |  Version:  1.9
 Severity:  Normal|   Resolution:
 Keywords:  set_language  | Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+
Changes (by timgraham):

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

Re: [Django] #26465: Contributing to Django:: Link text is not english

[Django]

#26465: Contributing to Django:: Link text is not english
-+-
 Reporter:  kaifeldhoff  |Owner:  nobody
 Type:   |   Status:  closed
  Cleanup/optimization   |
Component:  Documentation|  Version:  1.9
 Severity:  Normal   |   Resolution:  invalid
 Keywords:   | Triage Stage:
 |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by timgraham):

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


Comment:

 You're probably looking at the Spanish docs "es" in the URL instead of
 "en".

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

Re: [Django] #26455: Add lookups and database functions to check for valid geometries and repairing them.

[Django]

#26455: Add lookups and database functions to check for valid geometries and
repairing them.
-+-
 Reporter:  yellowcap|Owner:  yellowcap
 Type:  New feature  |   Status:  new
Component:  GIS  |  Version:  1.9
 Severity:  Normal   |   Resolution:
 Keywords:  isvalid, makevalid,  | Triage Stage:  Ready for
  valid, geometry|  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by timgraham):

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

Re: [Django] #26466: set_language with next unset and a urlencoded HTTP_REFERER fails redirection

[Django]

#26466: set_language with next unset and a urlencoded HTTP_REFERER fails
redirection
-+-
 Reporter:  miikkas  |Owner:  miikkas
 Type:  Bug  |   Status:  assigned
Component:   |  Version:  1.9
  Internationalization   |
 Severity:  Normal   |   Resolution:
 Keywords:  set_language | Triage Stage:
 |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by miikkas):

 * status:  new => assigned
 * needs_better_patch:   => 0
 * owner:  nobody => miikkas
 * 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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/065.0df9e3041de66827d6da7d844d60d9f6%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

[Django] #26466: set_language with next unset and a urlencoded HTTP_REFERER fails redirection

[Django]

#26466: set_language with next unset and a urlencoded HTTP_REFERER fails
redirection
--+--
 Reporter:  miikkas   |  Owner:  nobody
 Type:  Bug   | Status:  new
Component:  Internationalization  |Version:  1.9
 Severity:  Normal|   Keywords:  set_language
 Triage Stage:  Unreviewed|  Has patch:  0
Easy pickings:  0 |  UI/UX:  0
--+--
 POSTing to `set_language` when `next` is not set causes Django to user
 HTTP_REFERER instead. If the URL in HTTP_REFERER is urlencoded, the
 resulting redirection will fail.

 The bug is caused by the call to `translate_url` function in
 `set_language`. `translate_url` passes the URL on to `reverse`, which
 assumes URLs that are not urlencoding, thus resulting in a double
 urlencoded URL, which obviously will not work. Non-urlencoded URLs in
 HTTP_REFERER work correctly.

 An easy way to test this is to have a view with a URL with unicode
 characters in it and use the translation selector widget provided in the
 i18n docs, but with the `redirect_to` context variable undefined, which is
 the way I found the bug.

 AFAIK there's no standard about whether the browser should encode the URL
 in HTTP_REFERER, but most of the new browsers do so anyway. The bug should
 be easy to fix, thus, by just decoding the string in HTTP_REFERER – if it
 was encoded, it will now be unencoded, if it was '''not''' encoded, it
 will be unchanged (disregarding a corner case of ambiguous URLs with
 substrings like `%C3%A4` verbatim with browsers that don't encode the
 URLs). I'll make a pull request within a few days.

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/050.a66e8f5a1105e626b169b4d6d333da5f%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

[Django] #26465: Contributing to Django:: Link text is not english

[Django]

#26465: Contributing to Django:: Link text is not english
--+
 Reporter:  kaifeldhoff   |  Owner:  nobody
 Type:  Cleanup/optimization  | Status:  new
Component:  Documentation |Version:  1.9
 Severity:  Normal|   Keywords:
 Triage Stage:  Unreviewed|  Has patch:  0
Easy pickings:  0 |  UI/UX:  0
--+
 The 3rd item in the second list-block:

 Submit patches for new and/or fixed behavior. If you’re looking for an
 easy way to start contributing to Django read the '''Escribiendo tu primer
 parche para Django''' tutorial and have a look at the easy pickings
 tickets. The Patch review checklist will also be helpful.

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

Re: [Django] #26359: explain dual ticket tracking system

[Django]

#26359: explain dual ticket tracking system
-+-
 Reporter:  beckastar|Owner:
 Type:   |  kaifeldhoff
  Cleanup/optimization   |   Status:  assigned
Component:  Documentation|  Version:  1.9
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-

Comment (by kaifeldhoff):

 I additionally noticed, that the Trac-Wiki
 [https://code.djangoproject.com/wiki] also has a bold note for  the use of
 GitHub. It would be perfect if this kind of highlighting also occurs in
 the docs.

 I favor [https://docs.djangoproject.com/en/1.9/internals/contributing/new-
 contributors/#first-steps]. We could add a second point in the first list
 like this:

 '''Learn how to work with Git and GitHub'''
 No matter if code or documentation, everything finds its way into
 Django through GitHub. If you are not familiar with Git start here:
 [https://docs.djangoproject.com/en/1.9/internals/contributing/writing-code
 /working-with-git/]

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/067.27347578ef2adc830b321fc318ce00cd%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #26459: Allow providing DecimalField with a custom context (was: DecimalField float rounding)

[Django]

#26459: Allow providing DecimalField with a custom context
-+-
 Reporter:  yasondinalt  |Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  Database layer   |  Version:  1.9
  (models, ORM)  |
 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 timgraham):

 * has_patch:  1 => 0
 * stage:  Unreviewed => Accepted
 * type:  Bug => New feature


Comment:

 Accepting per Aymeric's proposal on the mailing list:

 Currently `DecimalField` accepts `max_digits` and `decimal_places`
 options. I think it should accept a decimal context and delegate all
 operations to that context.

 I suggest the following behavior:
 - start with the decimal context provided in a kwarg to `DecimalField` or,
 if there is None, the current context returned by `getcontext()`.
 - modify that context to take into account `max_digits` and
 `decimal_places`
 - ask the context to perform whatever operations we need

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

Re: [Django] #26341: Weird comments in PO files (.html.py filenames)

[Django]

#26341: Weird comments in PO files (.html.py filenames)
-+-
 Reporter:  sylvain-garancher|Owner:  veranika-
 |  sab
 Type:  Bug  |   Status:  assigned
Component:   |  Version:  1.9
  Internationalization   |
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Ready for
 |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by timgraham):

 * stage:  Accepted => Ready for checkin


Comment:

 Left a few cosmetic comments. Claude, could you check it too?

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

Re: [Django] #26458: The Avg aggregate should only automatically resolves its output field to FloatField on numeric sources

[Django]

#26458: The Avg aggregate should only automatically resolves its output field to
FloatField on numeric sources
-+-
 Reporter:  charettes|Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Ready for
 |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by timgraham):

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

Re: [Django] #26281: Improve utils.formats.date_format() error message when using time formatting with datetime.date

[Django]

#26281: Improve utils.formats.date_format() error message when using time
formatting with datetime.date
--+
 Reporter:  flesser   |Owner:  benxy
 Type:  Cleanup/optimization  |   Status:  assigned
Component:  Utilities |  Version:  1.9
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  1
Easy pickings:  0 |UI/UX:  0
--+
Changes (by timgraham):

 * needs_better_patch:  0 => 1


Comment:

 Left some comments for improvement.

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

Re: [Django] #26462: UnicodeEncodeError when warning about too long caching keys on Python 2

[Django]

#26462: UnicodeEncodeError when warning about too long caching keys on Python 2
-+
 Reporter:  suligap  |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Core (Cache system)  |  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:  new => closed
 * resolution:   => fixed


Comment:

 In [changeset:"90ce5d46bf62a74d7c78a61c1a7bab64f7cb1735" 90ce5d46]:
 {{{
 #!CommitTicketReference repository=""
 revision="90ce5d46bf62a74d7c78a61c1a7bab64f7cb1735"
 Fixed #26462 -- Fixed Python 2 UnicodeEncodeError when warning about long
 cache keys.
 }}}

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

Re: [Django] #26201: Document the consequences of rotating the CSRF token on login

[Django]

#26201: Document the consequences of rotating the CSRF token on login
--+
 Reporter:  wimfeijen |Owner:  vehrlich
 Type:  Cleanup/optimization  |   Status:  closed
Component:  Documentation |  Version:  1.8
 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:"369fa471f46cd517edf5fc82e4ef6138de3cff6e" 369fa47]:
 {{{
 #!CommitTicketReference repository=""
 revision="369fa471f46cd517edf5fc82e4ef6138de3cff6e"
 Fixed #26201 -- Documented the consequences of rotating the CSRF token on
 login.
 }}}

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/067.18d5253995faf9ae0e11dafec9786dbc%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #26281: Improve utils.formats.date_format() error message when using time formatting with datetime.date

[Django]

#26281: Improve utils.formats.date_format() error message when using time
formatting with datetime.date
--+
 Reporter:  flesser   |Owner:  benxy
 Type:  Cleanup/optimization  |   Status:  assigned
Component:  Utilities |  Version:  1.9
 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 timgraham):

 * has_patch:  0 => 1


Comment:

 [https://github.com/django/django/pull/6407 PR]

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

Re: [Django] #26459: DecimalField float rounding

[Django]

#26459: DecimalField float rounding
-+-
 Reporter:  yasondinalt  |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  1.9
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:
 |  Unreviewed
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by timgraham):

 * needs_tests:  1 => 0


Comment:

 I'm not sure whether or not to accept the ticket so I asked for advice on
 the [https://groups.google.com/d/topic/django-
 developers/bnoVTOx2GFs/discussion django-developers mailing list].

 p.s. You don't need to attach patches on the ticket when you also send a
 [https://github.com/django/django/pull/6410 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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/069.9655de126f4386bcec2cd3ab57839125%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #25850: Migrations ignore inconsistent history silently

[Django]

#25850: Migrations ignore inconsistent history silently
--+
 Reporter:  shaib |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  closed
Component:  Migrations|  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:  new => closed
 * resolution:   => fixed


Comment:

 In [changeset:"02ae5fd31a56ffb42feadb49c1f3870ba0a24869" 02ae5fd]:
 {{{
 #!CommitTicketReference repository=""
 revision="02ae5fd31a56ffb42feadb49c1f3870ba0a24869"
 Fixed #25850 -- Made migrate/makemigrations error on inconsistent history.
 }}}

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/063.c07c15ab1427322efe61209f6c1d7ee4%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #26459: DecimalField float rounding

[Django]

#26459: DecimalField float rounding
-+-
 Reporter:  yasondinalt  |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  1.9
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:
 |  Unreviewed
Has patch:  1|  Needs documentation:  0
  Needs tests:  1|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by yasondinalt):

 * Attachment "0001-DecimalField-rounding-first-cast-to-str-then-use-
 ROU.patch" added.

 Changes

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

Re: [Django] #24080: Sqlite segmentation fault regression when running tests (since 1.7.2)

[Django]

#24080: Sqlite segmentation fault regression when running tests (since 1.7.2)
---+
 Reporter:  stevejalim |Owner:  nobody
 Type:  Bug|   Status:  new
Component:  Testing framework  |  Version:  master
 Severity:  Normal |   Resolution:
 Keywords:  sqlite nose| Triage Stage:  Accepted
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+

Comment (by aaugustin):

 Since Django doesn't contain any C code, a segfault must be a bug in
 Python or in another third-party software. The bug can be caused by the
 software itself or by modifications performed by distributors.

 The purpose of this ticket is to identify the issue more precisely, so it
 can be reported upstream, and to identify workarounds in the meantime.
 It's highly unlikely to result in changes to Django.

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

Re: [Django] #26459: DecimalField float rounding

[Django]

#26459: DecimalField float rounding
-+-
 Reporter:  yasondinalt  |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  1.9
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:
 |  Unreviewed
Has patch:  1|  Needs documentation:  0
  Needs tests:  1|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by yasondinalt):

 Replying to [comment:2 timgraham]:
 > Could you give a snippet of the application code where you run into this
 issue?


 {{{
 class Invoice(models.Model):
 # same as django-paypal use
 mc_gross = models.DecimalField(max_digits=64, decimal_places=2,
 default=0)

 invoice = 10.215 # float
 invoice.save()
 }}}

 In DB will be value 10.21 (or if 10.225 -> 10.22)

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

Re: [Django] #24080: Sqlite segmentation fault regression when running tests (since 1.7.2)

[Django]

#24080: Sqlite segmentation fault regression when running tests (since 1.7.2)
---+
 Reporter:  stevejalim |Owner:  nobody
 Type:  Bug|   Status:  new
Component:  Testing framework  |  Version:  master
 Severity:  Normal |   Resolution:
 Keywords:  sqlite nose| Triage Stage:  Accepted
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+

Comment (by pieterdd):

 As far as I can tell, all the fixes in this thread are workarounds that -
 at least temporarily - keep the segmentation fault from manifesting itself
 while not addressing the root cause.

 Now, I don't have a solution myself. But I just want to point out that
 creating a dummy boolean value to trigger a subtle change in the way
 memory is allocated does not guarantee that the bug won't be triggered
 again and that it does nothing to address the underlying 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/068.8f086019bf87d598a40f8ed9bba95e96%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #23422: Cannot add Permission to Group in data migration

[Django]

#23422: Cannot add Permission to Group in data migration
+--
 Reporter:  tjwalch |Owner:  nobody
 Type:  Bug |   Status:  closed
Component:  Migrations  |  Version:  1.7
 Severity:  Normal  |   Resolution:  wontfix
 Keywords:  | Triage Stage:  Unreviewed
Has patch:  0   |  Needs documentation:  1
  Needs tests:  0   |  Patch needs improvement:  0
Easy pickings:  0   |UI/UX:  0
+--

Comment (by theoden-dd):

 Replying to [comment:20 alanjds]:

 I've failed with Django 1.9, even after adapting emit_post_migrate_signal
 to its new signature:
 {{{
 db_alias = schema_editor.connection.alias
 try:
 # Django 1.9
 emit_post_migrate_signal(2, False, db_alias)
 except TypeError:
 # Django < 1.9
 try:
 # Django 1.8
 emit_post_migrate_signal(2, False, 'default', db_alias)
 except TypeError:  # Django < 1.8
 emit_post_migrate_signal([], 2, False, 'default', db_alias)
 }}}

 This led me to this most significant part of stack trace and error:
 {{{
 ...
   File "/local/lib/python2.7/site-
 packages/django/core/management/sql.py", line 50, in
 emit_post_migrate_signal
 using=db)
   File "/local/lib/python2.7/site-
 packages/django/dispatch/dispatcher.py", line 192, in send
 response = receiver(signal=self, sender=sender, **named)
   File "/olivia/local/lib/python2.7/site-
 packages/django/contrib/sites/management.py", line 20, in
 create_default_site
 if not Site.objects.using(using).exists():
 ...
 django.db.utils.OperationalError: no such table: django_site
 }}}

 Has anyone got the success with 1.9?

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