date:20160603

Re: [Django] #12810: Add validation for clashing ManyToManyField.db_table names

2016-06-03 Thread Django

#12810: Add validation for clashing ManyToManyField.db_table names
-+-
 Reporter:  strelnikovdmitrij|Owner:
 |  berkerpeksag
 Type:  Bug  |   Status:  assigned
Component:  Core (System |  Version:  master
  checks)|
 Severity:  Normal   |   Resolution:
 Keywords:  ManyToManyField  | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+-
Changes (by charettes):

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

Re: [Django] #26706: Reverse many to one and forward many to many managers's prefetch object cache should be cleared on clear(). (was: "ManyToMany with prefetch_related" clear function doesn't clear t

2016-06-03 Thread Django

#26706: Reverse many to one and forward many to many managers's prefetch object
cache should be cleared on clear().
-+-
 Reporter:  cosmosgenius |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  1.8
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  manytomany, m2m, | Triage Stage:  Accepted
  clear  |
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by charettes):

 * stage:  Unreviewed => Accepted


Comment:

 From a quick look at the code this looks like a legitimate issue.

 The manager classes returned by `create_forward_many_to_many_manager` and
 `create_reverse_many_to_one_manager` factories are both affected.

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

Re: [Django] #25920: Add number formatting support for locales that use non-uniform digit grouping (e.g. India)

2016-06-03 Thread Django

#25920: Add number formatting support for locales that use non-uniform digit
grouping (e.g. India)
--+
 Reporter:  dbinoj|Owner:  jasisz
 Type:  New feature   |   Status:  assigned
Component:  Internationalization  |  Version:  1.9
 Severity:  Normal|   Resolution:
 Keywords:  en-IN | 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):

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

Re: [Django] #16614: Support server-side cursors for queryset iteration in database backends

2016-06-03 Thread Django

#16614: Support server-side cursors for queryset iteration in database backends
-+-
 Reporter:  toofishes|Owner:
 Type:  New feature  |   Status:  new
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  memory cursors   | Triage Stage:  Accepted
  database   |
Has patch:  1|  Needs documentation:  1
  Needs tests:  1|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by keturn):

 Okay, I've added
 
[https://github.com/keturn/django/commit/dd1c959eb817a7502c2e5f6405938301d05c277f
 #diff-db5fb8fdfbba5c6ac7595dd636d9b558R93 a test], which is better than no
 tests, but still leaves some to be desired. That is, this test makes sure
 that a call to `chunked()` does not fail horribly, but it doesn't test the
 salient difference between `chunked` and `iterator`, that `chunked` uses a
 server-side cursor and doesn't load large result sets in to memory all at
 once.

 Other things that it seems like might be valuable to test:

 * what if you have two `chunked()` queries at once, and alternate taking
 objects from each of them, do they successfully not get in each other's
 way?
 * that may be the same as: if you took the `_named_cursor_idx` out of the
 chunked_cursor name, what would break?

 Considering the API, is it necessary to add a new `QuerySet.chunked()`, or
 can we change `QuerySet.iterator()` to have this behaviour by default?
 (because it's what I always ''assumed'' that `iterator` did until I ran
 out of RAM.)

 It does change the run-time characteristics to some degree, but I'm having
 a hard time coming up with a situation where it would really break an
 existing use case.

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

Re: [Django] #8936: admin databrowse (read-only view-only permissions)

2016-06-03 Thread Django

* needs_better_patch: 1 => 0

Comment:

Hi,

I fixed the merge conflicts on the patch today :

https://github.com/olivierdalang/django/commit/42b289dc0827f7a52d8d91eef46300f0d77d8e6f
See discussion on the PR :
https://github.com/django/django/pull/5297#issuecomment-223714731

It shoud apply to master now.

I think we need a core dev to review this now, so I unset the "patch needs
improvement" tag. Sorry if this is not the right process (I'm new to
contributing to django).

Please let me know if there's anything else I can do to help getting those
merged into core.

Bests

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

Re: [Django] #26688: Inconsistent logging of 5xx and 4xx requests to django.request

2016-06-03 Thread Django

#26688: Inconsistent logging of 5xx and 4xx requests to django.request
---+
 Reporter:  solarissmoke   |Owner:  seocam
 Type:  Bug|   Status:  assigned
Component:  HTTP handling  |  Version:  master
 Severity:  Normal |   Resolution:
 Keywords: | Triage Stage:  Accepted
Has patch:  1  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+
Changes (by seocam):

 * has_patch:  0 => 1


Comment:

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

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

Re: [Django] #26028: Improve instructions for overriding Django templates

2016-06-03 Thread Django

#26028: Improve instructions for overriding Django templates
---+
 Reporter:  pydanny|Owner:  phildini
 Type:  New feature|   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:  0  |UI/UX:  0
---+
Changes (by phildini):

 * owner:  nobody => phildini
 * status:  new => assigned


Comment:

 I'm very interested in making this better as I use this pattern all the
 time. Any tips on where this doc should live would be helpful, I'll also
 make a best guess in a PR soon, hopefully.

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

Re: [Django] #16614: Support server-side cursors for queryset iteration in database backends

2016-06-03 Thread Django

Comment (by carljm):

Technically that's not public API and we can change it if we need to, but
it does cause problems for third-party database backends (and I think
we've said that we'll mention such changes in the release notes?). So we
should only change it if it's really valuable to do so. I'm not
immediately seeing a gain in clarity from that change that would justify
it, but maybe I'm missing some subtle reason why the new name is more
accurate? Unless that's so, I'd lean towards leaving it unchanged.

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

Re: [Django] #26707: QueryDict.fromkeys fails in mysterious ways

2016-06-03 Thread Django

#26707: QueryDict.fromkeys fails in mysterious ways
+
 Reporter:  wimglenn|Owner:  nobody
 Type:  Bug |   Status:  new
Component:  HTTP handling   |  Version:  master
 Severity:  Normal  |   Resolution:
 Keywords:  http querydict  | Triage Stage:  Accepted
Has patch:  1   |  Needs documentation:  0
  Needs tests:  0   |  Patch needs improvement:  0
Easy pickings:  0   |UI/UX:  0
+
Changes (by wimglenn):

 * has_patch:  0 => 1
 * component:  Utilities => HTTP handling


Comment:

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

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

Re: [Django] #16614: Support server-side cursors for queryset iteration in database backends

2016-06-03 Thread Django

#16614: Support server-side cursors for queryset iteration in database backends
-+-
 Reporter:  toofishes|Owner:
 Type:  New feature  |   Status:  new
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  memory cursors   | Triage Stage:  Accepted
  database   |
Has patch:  1|  Needs documentation:  1
  Needs tests:  1|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by keturn):

 also, it renames the DatabaseFeatures `can_use_chunked_reads` to
 `has_safe_chunked_reads`, is that a private interface that can be renamed
 freely, or is it a public interface we need to cautious around?

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

Re: [Django] #16614: Support server-side cursors for queryset iteration in database backends

2016-06-03 Thread Django

#16614: Support server-side cursors for queryset iteration in database backends
-+-
 Reporter:  toofishes|Owner:
 Type:  New feature  |   Status:  new
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  memory cursors   | Triage Stage:  Accepted
  database   |
Has patch:  1|  Needs documentation:  1
  Needs tests:  1|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by keturn):

 I've updated akaariai's patch from 2012 to
 [https://github.com/keturn/django/tree/server_side_cursor_16614
 server_side_cursor_16614].

 (not yet ready to submit, still wants docs and tests)

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

Re: [Django] #26707: QueryDict.fromkeys fails in mysterious ways

2016-06-03 Thread Django

#26707: QueryDict.fromkeys fails in mysterious ways
+
 Reporter:  wimglenn|Owner:  nobody
 Type:  Bug |   Status:  new
Component:  Utilities   |  Version:  master
 Severity:  Normal  |   Resolution:
 Keywords:  http querydict  | Triage Stage:  Accepted
Has patch:  0   |  Needs documentation:  0
  Needs tests:  0   |  Patch needs improvement:  0
Easy pickings:  0   |UI/UX:  0
+
Changes (by carljm):

 * needs_better_patch:   => 0
 * needs_docs:   => 0
 * needs_tests:   => 0
 * 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/066.3e2f5bb8059ea2099c283036c0701901%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

[Django] #26707: QueryDict.fromkeys fails in mysterious ways

2016-06-03 Thread Django

#26707: QueryDict.fromkeys fails in mysterious ways
+
 Reporter:  wimglenn|  Owner:  nobody
 Type:  Bug | Status:  new
Component:  Utilities   |Version:  master
 Severity:  Normal  |   Keywords:  http querydict
 Triage Stage:  Unreviewed  |  Has patch:  0
Easy pickings:  0   |  UI/UX:  0
+
 In django.http.QueryDict, we currently have the following weird behaviour
 and misleading error messages:

 {{{
 >>> QueryDict.fromkeys(['k1', 'k2'])
 AttributeError: This QueryDict instance is immutable
 }}}

 It is not possible to pass the mutable kwarg to the initialise in this
 way, either:

 {{{
 >>> QueryDict.fromkeys(['k1', 'k2'], mutable=True)
 TypeError: fromkeys() takes no keyword arguments
 }}}

 Django's querydict is-a dict, so the classmethod factory "fromkeys" should
 either
 a) work, or
 b) be explicitly disabled in the subclass, and documented as such

 The relevant section in the docs (
 https://docs.djangoproject.com/en/dev/ref/request-
 response/#django.http.QueryDict ) says that:

   > QueryDict implements all the standard dictionary methods because it’s
 a subclass of dictionary. Exceptions are outlined here: ...

 However, there is no mention about the fromkeys method.

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

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

Re: [Django] #26666: assertRedirects gives unhelpful error message expected URL is external

2016-06-03 Thread Django

#2: assertRedirects gives unhelpful error message expected URL is external
-+-
 Reporter:  inglesp  |Owner:
 Type:   |  tobiasmcnulty
  Cleanup/optimization   |   Status:  new
Component:  Testing framework|  Version:  master
 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
-+-

Comment (by tobiasmcnulty):

 * The original fix to this ticket
 (https://github.com/django/django/pull/6696) broke unit testing of custom
 hostnames in non-core Django projects when the hostname was passed as part
 of the path to client.get()
 * A new proposed change (https://github.com/django/django/pull/6713)
 leverages ALLOWED_HOSTS to facilitate support for custom domain testing in
 3rd party packages while increasing the rigor which with we validate
 ALLOWED_HOSTS (now also in tests)

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

Re: [Django] #22406: Inconsistent way to parse boolean value from posted data

2016-06-03 Thread Django

Comment (by cirosantilli):

I am doing something like this:

- a single AJAX view creates or deletes user up or down votes for posts.
If the vote already exists, it is deleted or modified.
- there are two types of vote differentiated by a Booleanfield
(application specific, difficult to explain), let's call them typeTrue and
typeFalse
- each user can do a single vote of each type (typeTrue and typeFalse)
either up or down

Now the view works as follows:

- check if the vote of a given type already exists for a given user. This
is an unique triple:
`Vote.filter(booleanfield=request.POST['booleanfield'])`
- if yes, delete it
- else, get the existing vote `vote`, and create or update it. This means
a form validation: `form = Vote(request.POST, instance=vote)`

So now, what should my AJAX send?

If nothing, as a form submission checkbox would on `False`, the existing
vote is not found as it should to be deleted.

If `'0'`, the form always gives me `True`.

I think `'false'` would work because it works for both, but it feels
inconsistent. Why `'0'` does not work as well?

Actual code: https://github.com/cirosantilli/free-books-django-
raw/blob/d4cb03d61a6f0c19ac7333ee1099e679e0acef21/free_books/views.py#L280

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

Re: [Django] #26702: Document custom field subclass change requires new custom field class

2016-06-03 Thread Django

#26702: Document custom field subclass change requires new custom field class
--+
 Reporter:  baylee|Owner:  baylee
 Type:  Cleanup/optimization  |   Status:  assigned
Component:  Documentation |  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
--+

Comment (by baylee):

 That makes sense. I've updated the PR to use a simplified example.

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

Re: [Django] #26706: "ManyToMany with prefetch_related" clear function doesn't clear the items from the object but deletes from db (was: ManyToMany clear doesn't clear the items from the object but de

2016-06-03 Thread Django

#26706: "ManyToMany with prefetch_related" clear function doesn't clear the 
items
from the object but deletes from db
-+-
 Reporter:  cosmosgenius |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  1.8
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  manytomany, m2m, | Triage Stage:
  clear  |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

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

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

Re: [Django] #26706: ManyToMany clear doesn't clear the items from the object but deletes from db

2016-06-03 Thread Django

#26706: ManyToMany clear doesn't clear the items from the object but deletes 
from
db
-+-
 Reporter:  cosmosgenius |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  1.8
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  manytomany, m2m, | Triage Stage:
  clear  |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by cosmosgenius):

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


Old description:

> {{{
>
> class Media(models.Model):
> name = models.CharField(max_length=100)
>

> class Tag(models.Model):
> tag = models.CharField(max_length=100)
> medias = models.ManyToManyField(Media)
>
> def __unicode__(self):
> return self.tag
> }}}
>
> Assume tag object below already has three items of Media model in medias
> which are saved in db. [m1, m2, m3].
>
> {{{
> tag = Tag.objects.get(id=1)
> tag.medias.clear()
> print(tag.medias.all())
> }}}
>
> The above code prints all the three [m1, m2, m3]. Fetching the tag again
> using get and printing givens an empty list "[ ]"

New description:

 {{{

 class Media(models.Model):
 name = models.CharField(max_length=100)


 class Tag(models.Model):
 tag = models.CharField(max_length=100)
 medias = models.ManyToManyField(Media)

 def __unicode__(self):
 return self.tag
 }}}

 Assume tag object below already has three items of Media model in medias
 which are saved in db. [m1, m2, m3].

 {{{
 tag = Tag.objects.get(id=1)
 tag.medias.clear()
 print(tag.medias.all())
 }}}

 The above code prints all the three [m1, m2, m3]. Fetching the tag again
 using get and printing givens an empty list "[ ]"

 Failing Testcase

 {{{
 class Test(TestCase):
 def test(self):
 tag = Tag.objects.create(tag='Tag')
 tag.medias.create(name='A')
 tag.medias.create(name='B')
 tag.medias.create(name='C')
 tag = Tag.objects.prefetch_related('medias').get(id=1)
 tag.medias.clear()
 print(tag.medias.all())
 }}}

 I guess its related to prefetch_related function.

--

Comment:

 {{{
 class Test(TestCase):
 def test(self):
 tag = Tag.objects.create(tag='Tag')
 tag.medias.create(name='A')
 tag.medias.create(name='B')
 tag.medias.create(name='C')
 tag = Tag.objects.prefetch_related('medias').get(id=1)
 tag.medias.clear()
 print(tag.medias.all())
 }}}

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

Re: [Django] #12810: Add validation for clashing ManyToManyField.db_table names

2016-06-03 Thread Django

#12810: Add validation for clashing ManyToManyField.db_table names
-+-
 Reporter:  strelnikovdmitrij|Owner:
 |  berkerpeksag
 Type:  Bug  |   Status:  assigned
Component:  Core (System |  Version:  master
  checks)|
 Severity:  Normal   |   Resolution:
 Keywords:  ManyToManyField  | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by berkerpeksag):

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

Re: [Django] #26604: Add example of simple multiple file upload in documentation

2016-06-03 Thread Django

#26604: Add example of simple multiple file upload in documentation
-+-
 Reporter:  zxcq544  |Owner:
 |  berkerpeksag
 Type:  New feature  |   Status:  closed
Component:  Documentation|  Version:  1.9
 Severity:  Normal   |   Resolution:  fixed
 Keywords:  doumentation,| Triage Stage:  Accepted
  multiple file upload, upload many  |
  files  |
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:"7407440885f1777abb88f18832ecedc3460f2506" 7407440]:
 {{{
 #!CommitTicketReference repository=""
 revision="7407440885f1777abb88f18832ecedc3460f2506"
 [1.9.x] Fixed #26604 -- Added a multiple file upload example to
 topics/http/file-uploads.txt.

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

Re: [Django] #26604: Add example of simple multiple file upload in documentation

2016-06-03 Thread Django

#26604: Add example of simple multiple file upload in documentation
-+-
 Reporter:  zxcq544  |Owner:
 |  berkerpeksag
 Type:  New feature  |   Status:  closed
Component:  Documentation|  Version:  1.9
 Severity:  Normal   |   Resolution:  fixed
 Keywords:  doumentation,| Triage Stage:  Accepted
  multiple file upload, upload many  |
  files  |
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:"27983d82c2415f02d962649b6623a20493b1790b" 27983d82]:
 {{{
 #!CommitTicketReference repository=""
 revision="27983d82c2415f02d962649b6623a20493b1790b"
 [1.10.x] Fixed #26604 -- Added a multiple file upload example to
 topics/http/file-uploads.txt.

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

Re: [Django] #26604: Add example of simple multiple file upload in documentation

2016-06-03 Thread Django

#26604: Add example of simple multiple file upload in documentation
-+-
 Reporter:  zxcq544  |Owner:
 |  berkerpeksag
 Type:  New feature  |   Status:  closed
Component:  Documentation|  Version:  1.9
 Severity:  Normal   |   Resolution:  fixed
 Keywords:  doumentation,| Triage Stage:  Accepted
  multiple file upload, upload many  |
  files  |
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:"54febdb8be7c9793caae9c781f4d6b7cbbdcd900" 54febdb8]:
 {{{
 #!CommitTicketReference repository=""
 revision="54febdb8be7c9793caae9c781f4d6b7cbbdcd900"
 Fixed #26604 -- Added a multiple file upload example to topics/http/file-
 uploads.txt.
 }}}

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

Re: [Django] #25127: document how to define models in multiple modules

2016-06-03 Thread Django

#25127: document how to define models in multiple modules
--+
 Reporter:  keturn|Owner:  palmerev
 Type:  Cleanup/optimization  |   Status:  assigned
Component:  Documentation |  Version:  1.8
 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
--+

Comment (by timgraham):

 You must import the models in `models/__init__.py` for Django to work
 properly. As with normal Python, you can use either import path in your
 own code.

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

Re: [Django] #25127: document how to define models in multiple modules

2016-06-03 Thread Django

#25127: document how to define models in multiple modules
--+
 Reporter:  keturn|Owner:  palmerev
 Type:  Cleanup/optimization  |   Status:  assigned
Component:  Documentation |  Version:  1.8
 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
--+

Comment (by keturn):

 > You can then import classes directly from the `models` module as you
 normally would.

 Yes, if you import them to `models/__init__.py`, you can import them
 elsewhere as `.models.Robot`, but `.models.robot.Robot` also works if you
 want to take advantage of that structure you created when you split things
 out into multiple models files.

 (which for `robot.Robot` sounds redundant but maybe `from
 .models.synthetics import Robot, Android` would be useful.)

 This is the part I feel most unsure about what to include in the
 documentation, because one hand I think the "There Should Be One Obvious
 Way To Do" it principle applies here, so it seems disadvantageous to go in
 to a lot of "you could import it this way **or** this way **or**..."

 On the other hand, I can also imagine myself coming to this and thinking,
 "wait, if I have to import things as if they were in `myapp.models`
 anyway, then doesn't that sort of defeat the purpose of splitting them
 up?"

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

Re: [Django] #25127: document how to define models in multiple modules

2016-06-03 Thread Django

#25127: document how to define models in multiple modules
--+
 Reporter:  keturn|Owner:  palmerev
 Type:  Cleanup/optimization  |   Status:  assigned
Component:  Documentation |  Version:  1.8
 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
 * has_patch:  0 => 1


Comment:

 [https://github.com/django/django/pull/6708 PR] with 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/064.7689e84629bacdae8b22f7659ed5dda8%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #26706: ManyToMany clear doesn't clear the items from the object but deletes from db

2016-06-03 Thread Django

#26706: ManyToMany clear doesn't clear the items from the object but deletes 
from
db
-+-
 Reporter:  cosmosgenius |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Database layer   |  Version:  1.8
  (models, ORM)  |   Resolution:
 Severity:  Normal   |  worksforme
 Keywords:  manytomany, m2m, | Triage Stage:
  clear  |  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:   => worksforme
 * needs_tests:   => 0
 * needs_docs:   => 0


Comment:

 I can't reproduce that. Here's my complete test case:
 {{{
 from django.test import TestCase

 from .models import Tag


 class Test(TestCase):
 def test(self):
 tag = Tag.objects.create(tag='Tag')
 tag.medias.create(name='A')
 tag.medias.create(name='B')
 tag.medias.create(name='C')
 tag = Tag.objects.get(id=1)
 tag.medias.clear()
 print(tag.medias.all())
 }}}
 Also, Django's test suite
 
[https://github.com/django/django/blob/9c53facc45908bc0593de194a60bc75e5d34a48e/tests/many_to_many/tests.py#L507-L509
 tests the behavior].

 Please reopen if you can provide a failing test case.

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

Re: [Django] #12810: Add validation for clashing ManyToManyField.db_table names

2016-06-03 Thread Django

#12810: Add validation for clashing ManyToManyField.db_table names
-+-
 Reporter:  strelnikovdmitrij|Owner:
 |  berkerpeksag
 Type:  Bug  |   Status:  assigned
Component:  Core (System |  Version:  master
  checks)|
 Severity:  Normal   |   Resolution:
 Keywords:  ManyToManyField  | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+-
Changes (by charettes):

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

Re: [Django] #25920: Add number formatting support for locales that use non-uniform digit grouping (e.g. India)

2016-06-03 Thread Django

#25920: Add number formatting support for locales that use non-uniform digit
grouping (e.g. India)
--+
 Reporter:  dbinoj|Owner:  jasisz
 Type:  New feature   |   Status:  assigned
Component:  Internationalization  |  Version:  1.9
 Severity:  Normal|   Resolution:
 Keywords:  en-IN | 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
 * stage:  Ready for checkin => Accepted


Comment:

 A bit of documentation is missing as noted on the 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/064.2ef9e640901b152ba0df0c4d693ed309%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #12810: Add validation for clashing ManyToManyField.db_table names

2016-06-03 Thread Django

#12810: Add validation for clashing ManyToManyField.db_table names
-+-
 Reporter:  strelnikovdmitrij|Owner:
 |  berkerpeksag
 Type:  Bug  |   Status:  assigned
Component:  Core (System |  Version:  master
  checks)|
 Severity:  Normal   |   Resolution:
 Keywords:  ManyToManyField  | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by berkerpeksag):

 * owner:  christopherdcunha => berkerpeksag
 * cc: berker.peksag@… (added)
 * needs_better_patch:  1 => 0


Comment:

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

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

Re: [Django] #24781: lazy() may need a repr for Python 2

2016-06-03 Thread Django

#24781: lazy() may need a __repr__ for Python 2
---+-
 Reporter:  jdh13  |Owner:  chescales
 Type:  Bug|   Status:  assigned
Component:  Utilities  |  Version:  1.7
 Severity:  Normal |   Resolution:
 Keywords:  py2| Triage Stage:  Accepted
Has patch:  1  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  1  |UI/UX:  0
---+-
Changes (by chescales):

 * cc: chescales (added)
 * has_patch:  0 => 1


Comment:

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

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

Re: [Django] #26596: Document {{ csrf_input }} in Jinja2 templates

2016-06-03 Thread Django

#26596: Document {{ csrf_input }} in Jinja2 templates
-+-
 Reporter:  aaugustin|Owner:  bjcubsfan
 Type:  Bug  |   Status:  closed
Component:  Documentation|  Version:  master
 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:  1|UI/UX:  0
-+-

Comment (by Tim Graham ):

 In [changeset:"16ce7a51ea5147949d652f8bf60b6e215ec16d8d" 16ce7a51]:
 {{{
 #!CommitTicketReference repository=""
 revision="16ce7a51ea5147949d652f8bf60b6e215ec16d8d"
 [1.9.x] Fixed #26596 -- Added Jinja2 {{ csrf_input }} documentation.

 Backport of 9c53facc45908bc0593de194a60bc75e5d34a48e 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.81211079c5020eae87459e978f57c9e5%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #26596: Document {{ csrf_input }} in Jinja2 templates

2016-06-03 Thread Django

#26596: Document {{ csrf_input }} in Jinja2 templates
-+-
 Reporter:  aaugustin|Owner:  bjcubsfan
 Type:  Bug  |   Status:  closed
Component:  Documentation|  Version:  master
 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:  1|UI/UX:  0
-+-

Comment (by Tim Graham ):

 In [changeset:"926529d6189bd0749067f8567b4e34bbf8b0e545" 926529d]:
 {{{
 #!CommitTicketReference repository=""
 revision="926529d6189bd0749067f8567b4e34bbf8b0e545"
 [1.10.x] Fixed #26596 -- Added Jinja2 {{ csrf_input }} documentation.

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

Re: [Django] #26596: Document {{ csrf_input }} in Jinja2 templates

2016-06-03 Thread Django

#26596: Document {{ csrf_input }} in Jinja2 templates
-+-
 Reporter:  aaugustin|Owner:  bjcubsfan
 Type:  Bug  |   Status:  closed
Component:  Documentation|  Version:  master
 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:  1|UI/UX:  0
-+-
Changes (by Tim Graham ):

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


Comment:

 In [changeset:"9c53facc45908bc0593de194a60bc75e5d34a48e" 9c53facc]:
 {{{
 #!CommitTicketReference repository=""
 revision="9c53facc45908bc0593de194a60bc75e5d34a48e"
 Fixed #26596 -- Added Jinja2 {{ csrf_input }} documentation.
 }}}

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

Re: [Django] #26659: Allow filtering of which tests run

2016-06-03 Thread Django

#26659: Allow filtering of which tests run
-+-
 Reporter:  apiraino |Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  Testing framework|  Version:  1.9
 Severity:  Normal   |   Resolution:
 Keywords:  tests| Triage Stage:
 |  Someday/Maybe
Has patch:  1|  Needs documentation:  1
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+-

Comment (by tbeadle):

 py.test gives you the ability to select tests by
 1) full path (test ID)
 2) using a "-k " command-line option to select tests that include
  in the name/path
 3) passing --lf to run the tests that failed during the last run

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

Re: [Django] #26705: DjangoTranslation instance has no attribute 'plural'

2016-06-03 Thread Django

#26705: DjangoTranslation instance has no attribute 'plural'
--+
 Reporter:  theju |Owner:  nobody
 Type:  Bug   |   Status:  new
Component:  Internationalization  |  Version:  master
 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 claudep):

 * needs_better_patch:   => 0
 * needs_docs:   => 0
 * version:  1.8 => master
 * needs_tests:   => 0
 * stage:  Unreviewed => Accepted


Comment:

 We could copy this line from the `gettext` module in `__init__`:
 `self.plural = lambda n: int(n != 1) # germanic plural by default`

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

Re: [Django] #4136: Add a way to save null CharField's as null rather than an empty string

2016-06-03 Thread Django

#4136: Add a way to save null CharField's as null rather than an empty string
-+-
 Reporter:  David Cramer |Owner:
  |
 Type:  New feature  |   Status:  new
Component:  Forms|  Version:  master
 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:

 Comments for improvement are on the 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/090.8d755dc087efa660ce33ae88d93b6870%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #26496: AdminEmailHandler can produce mails violating RFC2822

2016-06-03 Thread Django

#26496: AdminEmailHandler can produce mails violating RFC2822
-+-
 Reporter:  nijel|Owner:  knightrix
 Type:  Bug  |   Status:  closed
Component:  Error reporting  |  Version:  1.9
 Severity:  Normal   |   Resolution:  fixed
 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 timgraham):

 More friendly formatting of dictionaries may still be useful if someone is
 so inclined to reopen the ticket and make that change.

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

[Django] #26706: ManyToMany clear doesn't clear the items from the object but deletes from db

2016-06-03 Thread Django

#26706: ManyToMany clear doesn't clear the items from the object but deletes 
from
db
--+
 Reporter:  cosmosgenius  |  Owner:  nobody
 Type:  Bug   | Status:  new
Component:  Database layer (models, ORM)  |Version:  1.8
 Severity:  Normal|   Keywords:  manytomany,
  |  m2m, clear
 Triage Stage:  Unreviewed|  Has patch:  0
Easy pickings:  0 |  UI/UX:  0
--+
 {{{

 class Media(models.Model):
 name = models.CharField(max_length=100)


 class Tag(models.Model):
 tag = models.CharField(max_length=100)
 medias = models.ManyToManyField(Media)

 def __unicode__(self):
 return self.tag
 }}}

 Assume tag object below already has three items of Media model in medias
 which are saved in db. [m1, m2, m3].

 {{{
 tag = Tag.objects.get(id=1)
 tag.medias.clear()
 print(tag.medias.all())
 }}}

 The above code prints all the three [m1, m2, m3]. Fetching the tag again
 using get and printing givens an empty 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/055.e0c044b4b37cf9b7d5465a024f5dd867%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

[Django] #26705: DjangoTranslation instance has no attribute 'plural'

2016-06-03 Thread Django

#26705: DjangoTranslation instance has no attribute 'plural'
--+
 Reporter:  theju |  Owner:  nobody
 Type:  Bug   | Status:  new
Component:  Internationalization  |Version:  1.8
 Severity:  Normal|   Keywords:
 Triage Stage:  Unreviewed|  Has patch:  0
Easy pickings:  0 |  UI/UX:  0
--+
 When you activate a language that is not supported by django, an error is
 raised during the internationalization. Here is a test to reproduce the
 error:

 {{{
 import datetime

 from django.utils.translation import activate
 from django.utils.timesince import timesince
 from django.test import TestCase
 from django.conf import settings

 # Create your tests here.
 class TmpTestCase(TestCase):
 def test_lang(self):
 today = datetime.datetime.now()
 yesterday = today - datetime.timedelta(minutes=5)

 tt = timesince(yesterday, now=today)
 self.assertEqual(tt, u"5\xa0minutes")

 activate("hi")
 tt = timesince(yesterday, now=today)
 self.assertEqual(tt, u"5\xa0minutes")

 activate("as")
 tt = timesince(yesterday, now=today)
 self.assertEqual(tt, u"5\xa0minutes")
 }}}

 `as` is Assamese, a language that is currently not in django.

 The error is

 {{{
 AttributeErrorTraceback (most recent call
 last)
  in ()
 > 1 capfirst(ngettext(u"test", u"tests", 2))

 /home/ubuntu/wg_env/local/lib/python2.7/site-
 packages/django/utils/translation/__init__.pyc in ngettext(singular,
 plural, number)
  78
  79 def ngettext(singular, plural, number):
 ---> 80 return _trans.ngettext(singular, plural, number)
  81
  82

 /home/ubuntu/wg_env/local/lib/python2.7/site-
 packages/django/utils/translation/trans_real.pyc in ngettext(singular,
 plural, number)
 369 Returns a string on Python 3 and an UTF-8-encoded bytestring
 on Python 2.
 370 """
 --> 371 return do_ntranslate(singular, plural, number, 'ngettext')
 372
 373 if six.PY3:

 /home/ubuntu/wg_env/local/lib/python2.7/site-
 packages/django/utils/translation/trans_real.pyc in
 do_ntranslate(singular, plural, number, translation_function)
 356 t = getattr(_active, "value", None)
 357 if t is not None:
 --> 358 return getattr(t, translation_function)(singular, plural,
 number)
 359 if _default is None:
 360 _default = translation(settings.LANGUAGE_CODE)

 /usr/lib/python2.7/gettext.pyc in ngettext(self, msgid1, msgid2, n)
 368 def ngettext(self, msgid1, msgid2, n):
 369 try:
 --> 370 tmsg = self._catalog[(msgid1, self.plural(n))]
 371 if self._output_charset:
 372 return tmsg.encode(self._output_charset)

 AttributeError: DjangoTranslation instance has no attribute 'plural'
 }}}

 Ideally, there shouldn't be an 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/048.9a4391bbf05f5b178c695c71c2be04bb%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #26704: Document DjangoJSONEncoder

2016-06-03 Thread Django

#26704: Document DjangoJSONEncoder
--+
 Reporter:  willhardy |Owner:  tbeadle
 Type:  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:  0 |UI/UX:  0
--+
Changes (by tbeadle):

 * owner:  nobody => tbeadle
 * status:  new => assigned


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

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

Re: [Django] #25920: Add number formatting support for locales that use non-uniform digit grouping (e.g. India)

2016-06-03 Thread Django

#25920: Add number formatting support for locales that use non-uniform digit
grouping (e.g. India)
-+-
 Reporter:  dbinoj   |Owner:  jasisz
 Type:  New feature  |   Status:  assigned
Component:   |  Version:  1.9
  Internationalization   |
 Severity:  Normal   |   Resolution:
 Keywords:  en-IN| 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 phildini):

 * stage:  Accepted => Ready for checkin


Comment:

 I looked at the pull request, and think it looks RTC for the following
 reasons:

 - Has tests
 - Test suite passes
 - Old functionality from previous tests remains unchanged.

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

Re: [Django] #26496: AdminEmailHandler can produce mails violating RFC2822

2016-06-03 Thread Django

#26496: AdminEmailHandler can produce mails violating RFC2822
-+-
 Reporter:  nijel|Owner:  knightrix
 Type:  Bug  |   Status:  closed
Component:  Error reporting  |  Version:  1.9
 Severity:  Normal   |   Resolution:  fixed
 Keywords:   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-
Changes (by knightrix):

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


Comment:

 It looks like this is fixed by #22561. I modified the test like below and
 it passed for the use case.
 {{{#!python
def test_send_long_lines(self):
 email = EmailMessage('Subject', "Commentçava},{'this': {'another':
 {'more': 'nested'}, 'inner': 'myinner'}, 'that': 'hi'}" * 100,
 'f...@example.com', ['t...@example.com'])
 email.send()
 message = self.get_the_message()
 message_content = message.get_payload()
 has_long_lines = any(len(l) > 998 for l in
 message_content.splitlines())
 self.assertFalse(has_long_lines)

 }}}

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

Re: [Django] #25127: document how to define models in multiple modules

2016-06-03 Thread Django

#25127: document how to define models in multiple modules
--+
 Reporter:  keturn|Owner:  palmerev
 Type:  Cleanup/optimization  |   Status:  assigned
Component:  Documentation |  Version:  1.8
 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 palmerev):

 * status:  new => assigned
 * owner:  nobody => palmerev


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

Re: [Django] #26043: Add a hook to run queries between the start of a transaction and a view

2016-06-03 Thread Django

#26043: Add a hook to run queries between the start of a transaction and a view
---+
 Reporter:  srkunze|Owner:  nobody
 Type:  New feature|   Status:  closed
Component:  HTTP handling  |  Version:  1.8
 Severity:  Normal |   Resolution:  wontfix
 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):

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


Comment:

 Closing in light of the middleware refactor.

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

Re: [Django] #25616: Add note regarding missing dependencies on LookupError for migrations

2016-06-03 Thread Django

#25616: Add note regarding missing dependencies on LookupError for migrations
--+
 Reporter:  mcfletch  |Owner:  nip3o
 Type:  Cleanup/optimization  |   Status:  assigned
Component:  Migrations|  Version:  master
 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:

 If in doubt, we could close the ticket as "needsinfo" as we've not
 received steps to reproduce the 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/066.0f22a7c88e6c9144892b4b59d4699107%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #26683: Oracle DBs: Add option to use VARCHAR2 data type

2016-06-03 Thread Django

Comment (by shaib):

A few points:

1) Oracle 11.2 "extended support" is until 2020. We may decide to drop our
support of 11.2 earlier, but that wouldn't be nice to our users.

2) Varchar vs. NVarchar performance issues are well documented; such an
issue was [https://sourceforge.net/p/cx-oracle/mailman/message/35134630/
raised] only a few hours ago on the cx-oracle users group.

3) Actually, if anyone has the time to put into it, a compatibility-
breaking new Oracle backend could have a lot of benefits -- two important
problems that are hard to fix in a backward-compatible manner are the
performance issues around numbers (we translate many numbers to strings in
order to figure out the right Python type) and the case issues around
database object (tables etc) names.

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

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

Re: [Django] #26698: dbshell crashes on Postgres backend with empty database name

2016-06-03 Thread Django

#26698: dbshell crashes on Postgres backend with empty database name
-+-
 Reporter:  IlyaSemenov  |Owner:  mieciu
 Type:  Bug  |   Status:  closed
Component:  Core (Management |  Version:  1.9
  commands)  |
 Severity:  Normal   |   Resolution:  fixed
 Keywords:  dbshell  | Triage Stage:  Ready for
 |  checkin
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:"9a204fc8a52d79942325ed984d48e5aef5b64d21" 9a204fc]:
 {{{
 #!CommitTicketReference repository=""
 revision="9a204fc8a52d79942325ed984d48e5aef5b64d21"
 [1.10.x] Fixed #26698 -- Fixed PostgreSQL dbshell crash on an empty
 database name.

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

Re: [Django] #26698: dbshell crashes on Postgres backend with empty database name

2016-06-03 Thread Django

#26698: dbshell crashes on Postgres backend with empty database name
-+-
 Reporter:  IlyaSemenov  |Owner:  mieciu
 Type:  Bug  |   Status:  closed
Component:  Core (Management |  Version:  1.9
  commands)  |
 Severity:  Normal   |   Resolution:  fixed
 Keywords:  dbshell  | Triage Stage:  Ready for
 |  checkin
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:"5d60eb8bd72ee7d8a99f34ea060d9c3f4c3a6ff9" 5d60eb8b]:
 {{{
 #!CommitTicketReference repository=""
 revision="5d60eb8bd72ee7d8a99f34ea060d9c3f4c3a6ff9"
 [1.9.x] Fixed #26698 -- Fixed PostgreSQL dbshell crash on an empty
 database name.

 Backport of 19ff506878071ac93de684fe01328707e75e2b3a 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/069.3ee601a85afd10b3146b3bfbdc2549f6%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #26698: dbshell crashes on Postgres backend with empty database name

2016-06-03 Thread Django

#26698: dbshell crashes on Postgres backend with empty database name
-+-
 Reporter:  IlyaSemenov  |Owner:  mieciu
 Type:  Bug  |   Status:  closed
Component:  Core (Management |  Version:  1.9
  commands)  |
 Severity:  Normal   |   Resolution:  fixed
 Keywords:  dbshell  | Triage Stage:  Ready for
 |  checkin
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:"19ff506878071ac93de684fe01328707e75e2b3a" 19ff5068]:
 {{{
 #!CommitTicketReference repository=""
 revision="19ff506878071ac93de684fe01328707e75e2b3a"
 Fixed #26698 -- Fixed PostgreSQL dbshell crash on an empty database name.
 }}}

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

Re: [Django] #26698: dbshell crashes on Postgres backend with empty database name

2016-06-03 Thread Django

#26698: dbshell crashes on Postgres backend with empty database name
-+-
 Reporter:  IlyaSemenov  |Owner:  mieciu
 Type:  Bug  |   Status:  assigned
Component:  Core (Management |  Version:  1.9
  commands)  |
 Severity:  Normal   |   Resolution:
 Keywords:  dbshell  | Triage Stage:  Ready for
 |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-
Changes (by timgraham):

 * stage:  Accepted => Ready for checkin


Comment:

 I don't see an easy way to add a regression test for this since the
 current tests bypass `DatabaseClient.runshell()` which is what's changed
 to fix the issue.

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

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

Re: [Django] #23546: callproc **kwargs or *args parameter

2016-06-03 Thread Django

#23546: callproc **kwargs or *args parameter
-+-
 Reporter:  fatal10110   |Owner:
 Type:  New feature  |   Status:  new
Component:  Database layer   |  Version:  1.7
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  oracle   | 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):

 * owner:  averybigant =>
 * status:  assigned => new


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

Re: [Django] #24317: Deprecate field.rel, replace it with real field instances

2016-06-03 Thread Django

#24317: Deprecate field.rel, replace it with real field instances
-+-
 Reporter:  akaariai |Owner:
 Type:   |   Status:  new
  Cleanup/optimization   |
Component:  Database layer   |  Version:  master
  (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):

 * owner:  auvipy =>
 * status:  assigned => new


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

Re: [Django] #15619: Logout link should be protected

2016-06-03 Thread Django

#15619: Logout link should be protected
--+
 Reporter:  void  |Owner:
 Type:  Bug   |   Status:  new
Component:  contrib.auth  |  Version:  master
 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):

 * owner:  ashchristopher =>
 * status:  assigned => new


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

Re: [Django] #23155: Add request attr to user_login_failed signal

2016-06-03 Thread Django

#23155: Add request attr to user_login_failed signal
--+
 Reporter:  anonymous |Owner:  nobody
 Type:  New feature   |   Status:  new
Component:  contrib.auth  |  Version:  master
 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
--+

Comment (by timgraham):

 I think #25187 could be used as that separate ticket.

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

Re: [Django] #26021: Standardize on hanging indent in documentation

2016-06-03 Thread Django

#26021: Standardize on hanging indent in documentation
--+
 Reporter:  timgraham |Owner:  kutenai
 Type:  Cleanup/optimization  |   Status:  closed
Component:  Documentation |  Version:  master
 Severity:  Normal|   Resolution:  fixed
 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 Tim Graham ):

 In [changeset:"521772ff0779ced13f94a6ebcd96740a9eafbb1d" 521772ff]:
 {{{
 #!CommitTicketReference repository=""
 revision="521772ff0779ced13f94a6ebcd96740a9eafbb1d"
 [1.10.x] Fixed #26021 -- Applied hanging indentation to docs.

 Backport of 4a4d7f980e2a66756e1e424f7648dcd28ff765b7 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.26951f20ef7d1895dd16be9e4402c88e%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #26021: Standardize on hanging indent in documentation

2016-06-03 Thread Django

#26021: Standardize on hanging indent in documentation
--+
 Reporter:  timgraham |Owner:  kutenai
 Type:  Cleanup/optimization  |   Status:  closed
Component:  Documentation |  Version:  master
 Severity:  Normal|   Resolution:  fixed
 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 Tim Graham ):

 In [changeset:"6d0c9f95da7084abf09170ca5a06bd47fd20f0c4" 6d0c9f9]:
 {{{
 #!CommitTicketReference repository=""
 revision="6d0c9f95da7084abf09170ca5a06bd47fd20f0c4"
 [1.9.x] Fixed #26021 -- Applied hanging indentation to docs.

 Backport of 4a4d7f980e2a66756e1e424f7648dcd28ff765b7 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.95a401819b75ace270e739d472cd2dac%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #26021: Standardize on hanging indent in documentation

2016-06-03 Thread Django

#26021: Standardize on hanging indent in documentation
--+
 Reporter:  timgraham |Owner:  kutenai
 Type:  Cleanup/optimization  |   Status:  closed
Component:  Documentation |  Version:  master
 Severity:  Normal|   Resolution:  fixed
 Keywords:| Triage Stage:  Accepted
Has patch:  0 |  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:"4a4d7f980e2a66756e1e424f7648dcd28ff765b7" 4a4d7f98]:
 {{{
 #!CommitTicketReference repository=""
 revision="4a4d7f980e2a66756e1e424f7648dcd28ff765b7"
 Fixed #26021 -- Applied hanging indentation to docs.
 }}}

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

Re: [Django] #10107: Allow mark_safe() to be used as a decorator

2016-06-03 Thread Django

#10107: Allow mark_safe() to be used as a decorator
-+
 Reporter:  matehat  |Owner:  svvitale
 Type:  New feature  |   Status:  assigned
Component:  Utilities|  Version:  master
 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_docs:  1 => 0


Comment:

 Left comments for improvement on the PR. Please uncheck "Patch needs
 improvement" after updating.

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

Re: [Django] #12666: Setting for sending email using localtime instead of UTC

2016-06-03 Thread Django

#12666: Setting for sending email using localtime instead of UTC
-+
 Reporter:  net147   |Owner:  aisipos
 Type:  New feature  |   Status:  assigned
Component:  Core (Mail)  |  Version:  1.1
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  1|UI/UX:  0
-+
Changes (by timgraham):

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


Comment:

 [https://github.com/django/django/pull/6703 PR] with 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/064.279f8fc19c2c1d099973d7d7ac885d52%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #26628: Log CSRF failures to django.security instead of django.request (was: Log CSRF failures to django.security by default.)

2016-06-03 Thread Django

#26628: Log CSRF failures to django.security instead of django.request
--+
 Reporter:  jacobian  |Owner:  Hwesta
 Type:  Cleanup/optimization  |   Status:  assigned
Component:  CSRF  |  Version:  1.9
 Severity:  Normal|   Resolution:
 Keywords:  csrf security | Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  1
Easy pickings:  1 |UI/UX:  0
--+
Changes (by timgraham):

 * needs_docs:  1 => 0
 * has_patch:  0 => 1
 * component:  Documentation => CSRF
 * needs_better_patch:  0 => 1


Comment:

 [https://github.com/django/django/pull/6707 PR] with 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/066.9b5d4115a344791ef86b6cffa34c2c45%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #26702: Document custom field subclass change requires new custom field class

2016-06-03 Thread Django

#26702: Document custom field subclass change requires new custom field class
--+
 Reporter:  baylee|Owner:  baylee
 Type:  Cleanup/optimization  |   Status:  assigned
Component:  Documentation |  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
 * has_patch:  0 => 1


Comment:

 [https://github.com/django/django/pull/6705 PR]. I haven't reviewed it
 myself, but marking as needs improvement per previous comment.

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

Re: [Django] #15250: Cannot fill parent model instance in cache

2016-06-03 Thread Django

#15250: Cannot fill parent model instance in cache
-+-
 Reporter:  vzima|Owner:  czpython
 Type:  Bug  |   Status:  closed
Component:  Database layer   |  Version:  1.2
  (models, ORM)  |
 Severity:  Normal   |   Resolution:  fixed
 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 Tim Graham ):

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


Comment:

 In [changeset:"38575b007a722d6af510ea46d46393a4cda9ca29" 38575b00]:
 {{{
 #!CommitTicketReference repository=""
 revision="38575b007a722d6af510ea46d46393a4cda9ca29"
 Fixed #15250 -- Avoided extra query on some multi-table inheritance
 queries.

 Thanks marekw2143 for the initial patch and carljm for support.
 }}}

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

Re: [Django] #26638: Allow callable in defaults argument for QuerySet.get_or_create

2016-06-03 Thread Django

#26638: Allow callable in defaults argument for QuerySet.get_or_create
-+-
 Reporter:  mlorant  |Owner:
 |  ddsnowboard
 Type:  New feature  |   Status:  closed
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:  fixed
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  1|UI/UX:  0
-+-
Changes (by Tim Graham ):

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


Comment:

 In [changeset:"9899347641b2d3b4457cc99203a2b06504b32a16" 9899347]:
 {{{
 #!CommitTicketReference repository=""
 revision="9899347641b2d3b4457cc99203a2b06504b32a16"
 Fixed #26638 -- Allowed callable arguments for
 QuerySet.get_or_create()/update_or_create() defaults.
 }}}

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

Re: [Django] #26703: field automatically choosen as primary_key (primary_key=False do not work)

2016-06-03 Thread Django

#26703: field automatically choosen as primary_key (primary_key=False do not 
work)
-+-
 Reporter:  nbremond |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Database layer   |  Version:  1.9
  (models, ORM)  |
 Severity:  Normal   |   Resolution:  duplicate
 Keywords:  multi-table  | Triage Stage:
  inheritance, primary_key,  |  Unreviewed
  OneToOneField  |
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by timgraham):

 Seems like it wouldn't hurt.

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

Re: [Django] #26703: field automatically choosen as primary_key (primary_key=False do not work)

2016-06-03 Thread Django

#26703: field automatically choosen as primary_key (primary_key=False do not 
work)
-+-
 Reporter:  nbremond |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Database layer   |  Version:  1.9
  (models, ORM)  |
 Severity:  Normal   |   Resolution:  duplicate
 Keywords:  multi-table  | Triage Stage:
  inheritance, primary_key,  |  Unreviewed
  OneToOneField  |
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by charettes):

 @timgraham, It makes me wonder if we should adjust
 
[https://github.com/django/django/blob/44c7e5d3740edf796591ea3a89b0ff085534f225/django/db/models/options.py#L249-L252
 the deprecation warning] raised on implicit non-parent_link
 `OneToOneField` promotion to mention either to add `parent_link=True` or
 how to declare the usual implicit `parent_link` as the actions to take in
 order to have both fields available is non-trivial from the deprecation
 message.

 For example, in the reported case the message would be:

 `Implicit parent link is deprecated, either add parent_link=True to
 A.other or declare base_ptr = models.OneToOneField(Base, parent_link=True,
 primary_key=True) before it during the deprecation period`

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

Re: [Django] #19513: update() after annotate(val=Sum(...)) crashes on PostgreSQL & Oracle

2016-06-03 Thread Django

#19513: update() after annotate(val=Sum(...)) crashes on PostgreSQL & Oracle
-+-
 Reporter:  mengzhuo1203@…   |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  1.4
  (models, ORM)  |
 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:

 Comments for improvement are on the 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/080.e371a4cea93b0178ae271d1683e796f8%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #26703: field automatically choosen as primary_key (primary_key=False do not work)

2016-06-03 Thread Django

#26703: field automatically choosen as primary_key (primary_key=False do not 
work)
-+-
 Reporter:  nbremond |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Database layer   |  Version:  1.9
  (models, ORM)  |
 Severity:  Normal   |   Resolution:  duplicate
 Keywords:  multi-table  | Triage Stage:
  inheritance, primary_key,  |  Unreviewed
  OneToOneField  |
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:   => duplicate


Comment:

 I'm fairly confident it is.

 During the deprecation period you'll have to declare both
 `OneToOneField`s:

 {{{#!python
 class A(Base):
 base_ptr = models.OneToOneField(Base, parent_link=True,
 primary_key=True)
 other = models.OneToOneField(Base, null=True,
 related_name='other_base')
 }}}

 Where the `base_ptr` field should be the named after the lower cased name
 of the parent-linked base followed by the `'_ptr'` suffix.

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

Re: [Django] #26701: Improve link to issue tracker in the contributor guide

2016-06-03 Thread Django

#26701: Improve link to issue tracker in the contributor guide
--+
 Reporter:  shaunagm  |Owner:  shaunagm
 Type:  Cleanup/optimization  |   Status:  closed
Component:  Documentation |  Version:  1.9
 Severity:  Normal|   Resolution:  fixed
 Keywords:| Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+

Comment (by Tim Graham ):

 In [changeset:"a0ebfa0c56e16f8305d48dfa1eb74e1350db" a0ebfa0c]:
 {{{
 #!CommitTicketReference repository=""
 revision="a0ebfa0c56e16f8305d48dfa1eb74e1350db"
 [1.9.x] Fixed #26701 -- Replaced /newticket links to Trac with /.

 Backport of 44c7e5d3740edf796591ea3a89b0ff085534f225 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/066.94c95055cadbb3321b1e69f8c26a540d%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #26701: Improve link to issue tracker in the contributor guide

2016-06-03 Thread Django

#26701: Improve link to issue tracker in the contributor guide
--+
 Reporter:  shaunagm  |Owner:  shaunagm
 Type:  Cleanup/optimization  |   Status:  closed
Component:  Documentation |  Version:  1.9
 Severity:  Normal|   Resolution:  fixed
 Keywords:| Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+

Comment (by Tim Graham ):

 In [changeset:"971adb9e9ceaf50ecfa72db1b357bb38150048ea" 971adb9]:
 {{{
 #!CommitTicketReference repository=""
 revision="971adb9e9ceaf50ecfa72db1b357bb38150048ea"
 [1.10.x] Fixed #26701 -- Replaced /newticket links to Trac with /.

 Backport of 44c7e5d3740edf796591ea3a89b0ff085534f225 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/066.d31d2431ca3aac299f9f825cd2db46a0%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #26701: Improve link to issue tracker in the contributor guide

2016-06-03 Thread Django

#26701: Improve link to issue tracker in the contributor guide
--+
 Reporter:  shaunagm  |Owner:  shaunagm
 Type:  Cleanup/optimization  |   Status:  closed
Component:  Documentation |  Version:  1.9
 Severity:  Normal|   Resolution:  fixed
 Keywords:| Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+
Changes (by Tim Graham ):

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


Comment:

 In [changeset:"44c7e5d3740edf796591ea3a89b0ff085534f225" 44c7e5d3]:
 {{{
 #!CommitTicketReference repository=""
 revision="44c7e5d3740edf796591ea3a89b0ff085534f225"
 Fixed #26701 -- Replaced /newticket links to Trac with /.
 }}}

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

Re: [Django] #26703: field automatically choosen as primary_key (primary_key=False do not work)

2016-06-03 Thread Django

#26703: field automatically choosen as primary_key (primary_key=False do not 
work)
-+-
 Reporter:  nbremond |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  1.9
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  multi-table  | Triage Stage:
  inheritance, primary_key,  |  Unreviewed
  OneToOneField  |
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by timgraham):

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


Comment:

 Is this a duplicate of #26320?

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

Re: [Django] #26704: Document DjangoJSONEncoder

2016-06-03 Thread Django

#26704: Document DjangoJSONEncoder
--+
 Reporter:  willhardy |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:  0 |UI/UX:  0
--+
Changes (by timgraham):

 * needs_better_patch:   => 0
 * stage:  Unreviewed => Accepted
 * type:  Uncategorized => Cleanup/optimization
 * 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/067.05d7af4331b35a86f50e4b78976d9bab%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #21523: Models DateField to_python method no longer supports mock dates.

2016-06-03 Thread Django

#21523: Models DateField to_python method no longer supports mock dates.
-+-
 Reporter:  hugo@…   |Owner:  akki
 Type:   |   Status:  assigned
  Cleanup/optimization   |
Component:  Database layer   |  Version:  1.6
  (models, ORM)  |
 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
 * stage:  Ready for checkin => Accepted


Comment:

 Added some comments for improvement on the 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/079.89c27e9659dcd6a5b963820216e119fa%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #26644: SuspiciousFileOperation when creating a File from a NamedTemporaryFile

2016-06-03 Thread Django

#26644: SuspiciousFileOperation when creating a File from a NamedTemporaryFile
-+-
 Reporter:  hobarrera|Owner:  hobarrera
 Type:  Bug  |   Status:  assigned
Component:  File |  Version:  1.10
  uploads/storage|
 Severity:  Release blocker  |   Resolution:
 Keywords:  File,| Triage Stage:  Accepted
  SuspiciousFileOperation,   |
  NamedTemporaryFile, regression |
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


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

Re: [Django] #26683: Oracle DBs: Add option to use VARCHAR2 data type

2016-06-03 Thread Django

#26683: Oracle DBs: Add option to use VARCHAR2 data type
+--
 Reporter:  elarandjelovic  |Owner:  nobody
 Type:  New feature |   Status:  new
Component:  Migrations  |  Version:  1.9
 Severity:  Normal  |   Resolution:
 Keywords:  Oracle  | Triage Stage:  Unreviewed
Has patch:  0   |  Needs documentation:  0
  Needs tests:  0   |  Patch needs improvement:  0
Easy pickings:  0   |UI/UX:  0
+--

Comment (by jtiai):

 Replying to [comment:12 VackarAfzal]:
 > Replying to [comment:10 jtiai]:
 > > Oracle database encoding is slightly problematic case since once you
 have set it it's quite impossible to change it without reinstalling whole
 server.
 >
 > I can only speak for Oracle12c, but you can change the charecterset
 without having to re-install the server, not sure what the situation is
 with older versions.

 Well we do have Oracle 11g mostly, as well as our customers.

 > >
 > > At least we and our customers do have servers that run with
 WE8ISO8859P1 encoding, and very probably will have them for next few years
 at least. From my perspective I would like to have that datatype switch to
 be permanent so I could use that per customer basis.

 This is our main problem for unseen future. There exists, mainly windows
 applications that doesn't handle unicode and customers do use them still.

 > > I could do Proof of Concept with a switch and to see if it wouldn't be
 too complex to achieve.
 > >
 > > Sidenote: There is also in use NCLOB which supposed to be CLOB as
 well?
 > I've never had a use case that required NCLOB, but I'm sure there will
 be others who do. Suppose it makes sense for the same reason NVARCHAR2 was
 used.

 Django uses NCLOB as database datatype for models.TextFields.

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

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

Re: [Django] #26656: Add timedelta support to DjangoJSONEncoder

2016-06-03 Thread Django

#26656: Add timedelta support to DjangoJSONEncoder
-+-
 Reporter:  willhardy|Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  Core |  Version:  1.9
  (Serialization)|
 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
-+-

Comment (by willhardy):

 See https://code.djangoproject.com/ticket/26704 for the
 `DjangoJSONEncoder` documentation ticket.

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

Re: [Django] #26683: Oracle DBs: Add option to use VARCHAR2 data type

2016-06-03 Thread Django

#26683: Oracle DBs: Add option to use VARCHAR2 data type
+--
 Reporter:  elarandjelovic  |Owner:  nobody
 Type:  New feature |   Status:  new
Component:  Migrations  |  Version:  1.9
 Severity:  Normal  |   Resolution:
 Keywords:  Oracle  | Triage Stage:  Unreviewed
Has patch:  0   |  Needs documentation:  0
  Needs tests:  0   |  Patch needs improvement:  0
Easy pickings:  0   |UI/UX:  0
+--

Comment (by VackarAfzal):

 Replying to [comment:10 jtiai]:
 > Oracle database encoding is slightly problematic case since once you
 have set it it's quite impossible to change it without reinstalling whole
 server.

 I can only speak for Oracle12c, but you can change the charecterset
 without having to re-install the server, not sure what the situation is
 with older versions.
 >
 > At least we and our customers do have servers that run with WE8ISO8859P1
 encoding, and very probably will have them for next few years at least.
 From my perspective I would like to have that datatype switch to be
 permanent so I could use that per customer basis.
 >
 > It's not that we could use tools like DMU. It's just that some of our
 customers do still have non-unicode aware applications that requires
 VARCHAR2 to be something else but unicode.
 >
 > I could do Proof of Concept with a switch and to see if it wouldn't be
 too complex to achieve.
 >
 > Sidenote: There is also in use NCLOB which supposed to be CLOB as well?
 I've never had a use case that required NCLOB, but I'm sure there will be
 others who do. Suppose it makes sense for the same reason NVARCHAR2 was
 used.

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

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

[Django] #26704: Document DjangoJSONEncoder

2016-06-03 Thread Django

#26704: Document DjangoJSONEncoder
---+
 Reporter:  willhardy  |  Owner:  nobody
 Type:  Uncategorized  | Status:  new
Component:  Documentation  |Version:  1.9
 Severity:  Normal |   Keywords:
 Triage Stage:  Unreviewed |  Has patch:  0
Easy pickings:  0  |  UI/UX:  0
---+
 `DjangoJSONEncoder` only appears incidentally in the documentation.

 Add a small overview of the class, a use case or two and a list of the
 fields it supports with their output.

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

Re: [Django] #26683: Oracle DBs: Add option to use VARCHAR2 data type

2016-06-03 Thread Django

#26683: Oracle DBs: Add option to use VARCHAR2 data type
+--
 Reporter:  elarandjelovic  |Owner:  nobody
 Type:  New feature |   Status:  new
Component:  Migrations  |  Version:  1.9
 Severity:  Normal  |   Resolution:
 Keywords:  Oracle  | Triage Stage:  Unreviewed
Has patch:  0   |  Needs documentation:  0
  Needs tests:  0   |  Patch needs improvement:  0
Easy pickings:  0   |UI/UX:  0
+--

Comment (by VackarAfzal):

 Replying to [comment:9 timgraham]:
 > If we move forward with this, I prefer the approach of a temporary
 setting to opt-in to the new behavior (which eventually becomes mandatory)
 rather than creating a backend with a new name (unless there are
 compelling arguments against this approach).

 Thinking about it,  this actually would be more sensible.

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

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

Re: [Django] #26656: Add timedelta support to DjangoJSONEncoder

2016-06-03 Thread Django

#26656: Add timedelta support to DjangoJSONEncoder
-+-
 Reporter:  willhardy|Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  Core |  Version:  1.9
  (Serialization)|
 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
-+-

Comment (by willhardy):

 `DjangoJSONEncoder` does not seem to be documented at all. I've added an
 entry to the release notes, and will open another ticket for the whole
 class to be documented.

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

Re: [Django] #26683: Oracle DBs: Add option to use VARCHAR2 data type

2016-06-03 Thread Django

Comment (by jtiai):

Oracle database encoding is slightly problematic case since once you have
set it it's quite impossible to change it without reinstalling whole
server.

At least we and our customers do have servers that run with WE8ISO8859P1
encoding, and very probably will have them for next few years at least.
From my perspective I would like to have that datatype switch to be
permanent so I could use that per customer basis.

It's not that we could use tools like DMU. It's just that some of our
customers do still have non-unicode aware applications that requires
VARCHAR2 to be something else but unicode.

I could do Proof of Concept with a switch and to see if it wouldn't be too
complex to achieve.

Sidenote: There is also in use NCLOB which supposed to be CLOB as well?

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

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

[Django] #26703: field automatically choosen as primary_key (primary_key=False do not work)

2016-06-03 Thread Django

#26703: field automatically choosen as primary_key (primary_key=False do not 
work)
-+-
 Reporter:  nbremond |  Owner:  nobody
 Type:  Bug  | Status:  new
Component:  Database layer   |Version:  1.9
  (models, ORM)  |   Keywords:  multi-table
 Severity:  Normal   |  inheritance, primary_key,
 |  OneToOneField
 Triage Stage:  Unreviewed   |  Has patch:  0
Easy pickings:  0|  UI/UX:  0
-+-
 I tried to use multi-table inheritance with a OneToOne field to the parent
 class in the child class but this field seems to be detected as
 primary_key by Django (there is only one row in the database).

 The field has the same type as the parent link automatically created by
 Django and
 the [https://docs.djangoproject.com/en/1.10/topics/db/models/#specifying-
 the-parent-link-field doc on inheritance] tells that we can choose to use
 a such field for the inheritance relation with `parent_link=True` but I
 need the inheritance relation AND my other relation.
 I tried to add `parent_link=False` but this don't change anything.
 If I add `null=True` I got an error :
 {{{
 SystemCheckError: System check identified some issues:

 ERRORS:
 testapp.A.other: (fields.E007) Primary keys must not have null=True.
 HINT: Set null=False on the field, or remove primary_key=True
 argument.
 from django.db import models
 }}}
 So I tried to add `primary_key=False` but that don't change anything.

 There is a minimal code wich reproduce the error

 models.py :
 {{{
 #!python
 class Base(models.Model):
 pass

 class A(Base):
 other=models.OneToOneField(Base,
 parent_link=False,#do not change anything
 primary_key=False,#do not change anything
 null=True,#raise a SystemCheckError
 related_name='other_base',
 )

 }}}

 I can continue my project if I replace the `OneToOneField` by a
 `ForeignKey` with `unique=True` but I have a warning with a hint to
 replace the `ForeignKey` by a `OneToOneField` :
 {{{
 System check identified some issues:

 WARNINGS:
 testapp.A.other: (fields.W342) Setting unique=True on a ForeignKey has the
 same effect as using a OneToOneField.
 HINT: ForeignKey(unique=True) is usually better served by a
 OneToOneField.
 }}}

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

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

Re: [Django] #26702: Document custom field subclass change requires new custom field class

2016-06-03 Thread Django

#26702: Document custom field subclass change requires new custom field class
--+
 Reporter:  baylee|Owner:  baylee
 Type:  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:  0 |UI/UX:  0
--+

Comment (by tuffnatty):

 The method/mixin part is confusing for an average reader who is searching
 for a simple case; I think that it should be an example separate from the
 original case in #26586 where no mixin is needed.

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

83 matches

Mail list logo