date:20160927

Re: [Django] #27263: Allow validators to short-circuit in form field validation

2016-09-27 Thread Django

#27263: Allow validators to short-circuit in form field validation
-+-
 Reporter:  Alexey Rogachev  |Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  Forms|  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:  form, validator  | Triage Stage:  Someday/Maybe
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Alexey Rogachev):

 Based on [https://code.djangoproject.com/ticket/27263#comment:8 idea of
 Aymeric Augustin] I've come up with this workaround:

 {{{#!python
 class MultiValidator(object):
 def __init__(self, validators):
 self.validators = validators

 def __call__(self, value):
 for validator in self.validators:
 validator(value)
 }}}

 Then we can group multiple validators using this `MultiValidator`:

 {{{#!python
 class ChartForm(forms.ModelForm):
 import_file = forms.FileField(required=False, label='File for import',
 validators=[MultiValidator([
 FileSizeValidator(max_size='500 kb'),
 FileTypeValidator(extensions=('xlsx',)),
 ])])
 }}}

 I don't like the additional nesting and mess with brackets, but besides
 that I think it's OK.

 We can improve the look by subclassing and creating specific class:

 {{{#!python
 class ChartFileMultiValidator(MultiValidator):
 def __init__(self):
 validators = [
 FileSizeValidator(max_size='500 kb'),
 FileTypeValidator(extensions=('xlsx',)),
 ]
 super(ChartFileMultiValidator, self).__init__(validators)
 }}}

 Then the code reduces to:

 {{{#!python
 class ChartForm(forms.ModelForm):
 import_file = forms.FileField(required=False, label='File for import',
 validators=[ChartFileMultiValidator])
 }}}

 I personally prefer first approach.

 In this case maybe add info about default strategy of applying validators
 for form field and possible option for short circuit validation to
 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.5c83abcb81f8bb3ed2d351911e7f4e31%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #26886: Wrong warnings during template rendering

2016-09-27 Thread Django

#26886: Wrong warnings during template rendering
-+--
 Reporter:  None |Owner:  None
 Type:  Bug  |   Status:  new
Component:  Template system  |  Version:  1.9
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+--
Changes (by nrogers64):

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


Comment:

 I wasn't the one to report this bug, but I ran into the same thing. I made
 a fresh Django 1.10.1 project and added this to settings.py:


 {{{
 LOGGING = {
 'version': 1,
 'disable_existing_loggers': False,
 'handlers': {
 'console': {
 'class': 'logging.StreamHandler',
 },
 },
 'loggers': {
 'django.template': {
 'handlers': ['console'],
 'level': 'DEBUG',
 'propagate': False,
 },
 }
 }
 }}}

 That is the only code I added. I then did the initial migrate and started
 runserver. Then, in another Terminal tab, I ran `curl
 http://localhost:8001/favicon.ico`, which resulted in a "Page not found at
 /favicon.ico", as expected. But this was in the output of runserver:


 {{{
 Exception while resolving variable 'name' in template 'unknown'.
 Traceback (most recent call last):
   File ".../.virtualenvs/project/local/lib/python2.7/site-
 packages/django/template/base.py", line 907, in _resolve_lookup
 (bit, current))  # missing attribute
 VariableDoesNotExist: Failed lookup for key [name] in u' (admin:admin) ^admin/>'
 }}}

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

Re: [Django] #26836: Allow applications to register links in the admin interface

2016-09-27 Thread Django

#26836: Allow applications to register links in the admin interface
-+-
 Reporter:  Mathieu Poussin  |Owner:  Luis Del
 |  Giudice
 Type:  New feature  |   Status:  assigned
Component:  contrib.admin|  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 Luis Del Giudice):

 * owner:  nobody => Luis Del Giudice
 * 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/064.5bb726d06911e0178f2614a78132f20c%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #27217: makemigrations crashes with "'SpatialRefSysMixin' has no attribute '_meta'" on PostGIS

2016-09-27 Thread Django

#27217: makemigrations crashes with "'SpatialRefSysMixin' has no attribute 
'_meta'"
on PostGIS
-+
 Reporter:  Satish V Madala  |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  GIS  |  Version:  master
 Severity:  Release blocker  |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+
Changes (by Tim Graham):

 * has_patch:  0 => 1


Comment:

 [https://github.com/django/django/pull/7305 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/066.ca4d812e862f82829fdfbff72e5dcb4e%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #26761: Add 'help_text' property to methods in ModelAdmin.list_display

2016-09-27 Thread Django

#26761: Add 'help_text' property to methods in ModelAdmin.list_display
---+--
 Reporter:  Derek Hohls|Owner:  ducdetronquito
 Type:  New feature|   Status:  assigned
Component:  contrib.admin  |  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 Tim Graham):

 * needs_better_patch:  0 => 1


Comment:

 I left some ideas 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/067.29aac90e6b0b0c7e773df75fd063c4b5%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #27102: simplify_regex is not cleaning up any outstanding regex-y character

2016-09-27 Thread Django

#27102: simplify_regex is not cleaning up any outstanding regex-y character
-+-
 Reporter:  Prajjwol Gautam  |Owner:  Prajjwol
 |  Gautam
 Type:  Bug  |   Status:  closed
Component:  contrib.admindocs|  Version:  master
 Severity:  Normal   |   Resolution:  duplicate
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Tim Graham):

 * resolution:  fixed => duplicate


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

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

Re: [Django] #27282: port cant be integer with oracle backend

2016-09-27 Thread Django

#27282: port cant be integer with oracle backend
-+-
 Reporter:  Zapelini |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Database layer   |  Version:  1.10
  (models, ORM)  |
 Severity:  Normal   |   Resolution:  fixed
 Keywords:  port | 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 Tim Graham ):

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


Comment:

 In [changeset:"62543260dd58309902fa73f0984e245fd6c6da2a" 62543260]:
 {{{
 #!CommitTicketReference repository=""
 revision="62543260dd58309902fa73f0984e245fd6c6da2a"
 Fixed #27282 -- Allowed using an integer DATABASES['PORT'] for Oracle.
 }}}

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

Re: [Django] #27268: Regression on error message for invalid related fields lookup in QuerySet.get()

2016-09-27 Thread Django

#27268: Regression on error message for invalid related fields lookup in
QuerySet.get()
-+-
 Reporter:  François Freitag |Owner:  felixxm
 Type:  Bug  |   Status:  closed
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:  fixed
 Keywords:  get lookup related   | Triage Stage:  Ready for
  fields |  checkin
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:"14986a0b9d5ef9e89eb9b9cac561d5baab89f123" 14986a0]:
 {{{
 #!CommitTicketReference repository=""
 revision="14986a0b9d5ef9e89eb9b9cac561d5baab89f123"
 Fixed #27268 --  Restored an invalid related field lookup error message in
 QuerySet filtering.
 }}}

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

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

2016-09-27 Thread Django

#26401: Allow auth machinery to be used without installing auth app
--+-
 Reporter:  Matt Johnson  |Owner:  Andrew Konoff
 Type:  New feature   |   Status:  new
Component:  contrib.auth  |  Version:  1.9
 Severity:  Normal|   Resolution:
 Keywords:  auth 1.11 | Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+-
Changes (by Jon Dufresne):

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


Comment:

 Reopening until the above issue is handled.

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

Re: [Django] #27268: Regression on error message for invalid related fields lookup in QuerySet.get()

2016-09-27 Thread Django

#27268: Regression on error message for invalid related fields lookup in
QuerySet.get()
-+-
 Reporter:  François Freitag |Owner:  felixxm
 Type:  Bug  |   Status:  assigned
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  get lookup related   | Triage Stage:  Ready for
  fields |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Tim Graham):

 * has_patch:  0 => 1
 * stage:  Accepted => Ready for checkin


Comment:

 [https://github.com/django/django/pull/7303 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/073.8020c00932ee019b3dea8e8e4f97ce3d%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #27210: smtp EmailBackend doesn't honor fail_silently=True when receiving a socket level connection error

2016-09-27 Thread Django

#27210: smtp EmailBackend doesn't honor fail_silently=True when receiving a 
socket
level connection error
-+-
 Reporter:  Tom Hendrikx |Owner:  Vesteinn
 |  Snaebjarnarson
 Type:  Bug  |   Status:  closed
Component:  Core (Mail)  |  Version:  master
 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:"602bffe7585c6b61f3d9badf21f84c1eb445d58f" 602bffe7]:
 {{{
 #!CommitTicketReference repository=""
 revision="602bffe7585c6b61f3d9badf21f84c1eb445d58f"
 Fixed #27210 -- Allowed SMTPBackend to fail silently on a socket
 connection 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/067.05f3ee9f9f38bd9a936168851e7eee00%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #27281: can-delete: we don't use initial data

2016-09-27 Thread Django

#27281: can-delete: we don't use initial data
-+-
 Reporter:  Kifsif   |Owner:  nobody
 Type:   |   Status:  closed
  Cleanup/optimization   |
Component:  Documentation|  Version:  1.10
 Severity:  Normal   |   Resolution:  duplicate
 Keywords:   | Triage Stage:
 |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Tim Graham):

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


Comment:

 As noted in #27280, I'm not sure the suggestion is correct. Anyway, we can
 discuss it there and make this change as part of that ticket if I'm wrong.

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

Re: [Django] #27280: can-order: we don't use initial data

2016-09-27 Thread Django

#27280: can-order: we don't use initial data
-+-
 Reporter:  Kifsif   |Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |
Component:  Documentation|  Version:  1.10
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:
 |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Tim Graham):

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


Comment:

 I'm not sure about that suggestion. The initial is needed for the previous
 code block on the page and generally you should pass the same `initial`
 when processing formset data so that `form.has_changed()` works properly.

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

Re: [Django] #27282: port cant be integer with oracle backend

2016-09-27 Thread Django

#27282: port cant be integer with oracle backend
-+-
 Reporter:  Zapelini |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  1.10
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  port | 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 Tim Graham):

 * has_patch:  0 => 1
 * stage:  Unreviewed => Ready for checkin


Comment:

 The `strip()` is from the
 
[https://github.com/django/django/commit/cac7675f247da325cb862a312804fe64845d1155
 #diff-54b46d05e1da568b3cc987c423e00c50R33 original backend] but I don't
 see much need for it either.

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

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

Re: [Django] #27282: port cant be integer with oracle backend

2016-09-27 Thread Django

#27282: port cant be integer with oracle backend
-+-
 Reporter:  Zapelini |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  1.10
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  port | Triage Stage:
 |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Zapelini):

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


Comment:

 There is a pull request at: https://github.com/django/django/pull/7302

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

[Django] #27282: port cant be integer with oracle backend

2016-09-27 Thread Django

#27282: port cant be integer with oracle backend
--+
 Reporter:  Zapelini  |  Owner:  nobody
 Type:  Bug   | Status:  new
Component:  Database layer (models, ORM)  |Version:  1.10
 Severity:  Normal|   Keywords:  port
 Triage Stage:  Unreviewed|  Has patch:  0
Easy pickings:  0 |  UI/UX:  0
--+
 if you set the PORT to be an integer with the oracle backend you will get
 an exception because it calls strip on the value:

 
https://github.com/django/django/blob/master/django/db/backends/oracle/base.py#L194

 note that the other backends do not do this, so either an integer or
 string value will do just fine.

 
https://github.com/django/django/blob/master/django/db/backends/postgresql/base.py#L165

 The fix ix simple: just remove the .strip() call from line 194

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

Re: [Django] #27268: Regression on error message for invalid related fields lookup in QuerySet.get()

2016-09-27 Thread Django

#27268: Regression on error message for invalid related fields lookup in
QuerySet.get()
-+-
 Reporter:  François Freitag |Owner:  felixxm
 Type:  Bug  |   Status:  assigned
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  get lookup related   | Triage Stage:  Accepted
  fields |
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by felixxm):

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


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

Re: [Django] #27076: Document django.contrib.admin.sites.AdminSite.register()

2016-09-27 Thread Django

#27076: Document django.contrib.admin.sites.AdminSite.register()
-+-
 Reporter:  Baptiste Mispelon|Owner:  Austin
 Type:   |  Simmons
  Cleanup/optimization   |   Status:  closed
Component:  Documentation|  Version:  1.10
 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:"0f6829a68afb91abfdea8489008ebffac3d5220c" 0f6829a]:
 {{{
 #!CommitTicketReference repository=""
 revision="0f6829a68afb91abfdea8489008ebffac3d5220c"
 Fixed #27076 -- Documented contrib.admin.sites.AdminSite.register().
 }}}

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

Re: [Django] #27076: Document django.contrib.admin.sites.AdminSite.register()

2016-09-27 Thread Django

#27076: Document django.contrib.admin.sites.AdminSite.register()
-+-
 Reporter:  Baptiste Mispelon|Owner:  Austin
 Type:   |  Simmons
  Cleanup/optimization   |   Status:  closed
Component:  Documentation|  Version:  1.10
 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
-+-

Comment (by Tim Graham ):

 In [changeset:"933ebfad06b736e872b4c9afca6697cda8c3e216" 933ebfad]:
 {{{
 #!CommitTicketReference repository=""
 revision="933ebfad06b736e872b4c9afca6697cda8c3e216"
 [1.10.x] Fixed #27076 -- Documented
 contrib.admin.sites.AdminSite.register().

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

Re: [Django] #20705: Allow customizing the email field name for PasswordResetForm

2016-09-27 Thread Django

#20705: Allow customizing the email field name for PasswordResetForm
--+-
 Reporter:  Cloudream |Owner:  mlevental
 Type:  New feature   |   Status:  closed
Component:  contrib.auth  |  Version:  master
 Severity:  Normal|   Resolution:  fixed
 Keywords:| Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+-
Changes (by Tim Graham ):

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


Comment:

 In [changeset:"617e36dc1ede2a311dfd03f18432b31cbfe4c0f7" 617e36dc]:
 {{{
 #!CommitTicketReference repository=""
 revision="617e36dc1ede2a311dfd03f18432b31cbfe4c0f7"
 Fixed #20705 -- Allowed using PasswordResetForm with user models with an
 email field not named 'email'.
 }}}

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

[Django] #27281: can-delete: we don't use initial data

2016-09-27 Thread Django

#27281: can-delete: we don't use initial data
--+
 Reporter:  Kifsif|  Owner:  nobody
 Type:  Cleanup/optimization  | Status:  new
Component:  Documentation |Version:  1.10
 Severity:  Normal|   Keywords:
 Triage Stage:  Unreviewed|  Has patch:  0
Easy pickings:  0 |  UI/UX:  0
--+
 https://docs.djangoproject.com/en/1.10/topics/forms/formsets/#can-delete


 {{{
 >>> data = {
 ... 'form-TOTAL_FORMS': '3',
 ... 'form-INITIAL_FORMS': '2',
 ... 'form-MAX_NUM_FORMS': '',
 ... 'form-0-title': 'Article #1',
 ... 'form-0-pub_date': '2008-05-10',
 ... 'form-0-DELETE': 'on',
 ... 'form-1-title': 'Article #2',
 ... 'form-1-pub_date': '2008-05-11',
 ... 'form-1-DELETE': '',
 ... 'form-2-title': '',
 ... 'form-2-pub_date': '',
 ... 'form-2-DELETE': '',
 ... }

 >>> formset = ArticleFormSet(data, initial=[
 ... {'title': 'Article #1', 'pub_date': datetime.date(2008, 5, 10)},
 ... {'title': 'Article #2', 'pub_date': datetime.date(2008, 5, 11)},
 ... ])
 }}}


 We don't use initial data here. It overburdens the documentation.

 Offer: formset = ArticleFormSet(data)

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

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

[Django] #27280: can-order: we don't use initial data

2016-09-27 Thread Django

#27280: can-order: we don't use initial data
--+
 Reporter:  Kifsif|  Owner:  nobody
 Type:  Cleanup/optimization  | Status:  new
Component:  Documentation |Version:  1.10
 Severity:  Normal|   Keywords:
 Triage Stage:  Unreviewed|  Has patch:  0
Easy pickings:  0 |  UI/UX:  0
--+
 https://docs.djangoproject.com/en/1.10/topics/forms/formsets/#can-order


 {{{
 >>> data = {
 ... 'form-TOTAL_FORMS': '3',
 ... 'form-INITIAL_FORMS': '2',
 ... 'form-MAX_NUM_FORMS': '',
 ... 'form-0-title': 'Article #1',
 ... 'form-0-pub_date': '2008-05-10',
 ... 'form-0-ORDER': '2',
 ... 'form-1-title': 'Article #2',
 ... 'form-1-pub_date': '2008-05-11',
 ... 'form-1-ORDER': '1',
 ... 'form-2-title': 'Article #3',
 ... 'form-2-pub_date': '2008-05-01',
 ... 'form-2-ORDER': '0',
 ... }

 >>> formset = ArticleFormSet(data, initial=[
 ... {'title': 'Article #1', 'pub_date': datetime.date(2008, 5, 10)},
 ... {'title': 'Article #2', 'pub_date': datetime.date(2008, 5, 11)},
 ... ])
 }}}


 We don't use initial data here. It overburdens the documentation.

 Offer: formset = ArticleFormSet(data).

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

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

Re: [Django] #25251: Inconsistent availability of data migrations in TransactionTestCase when using --keepdb

2016-09-27 Thread Django

#25251: Inconsistent availability of data migrations in TransactionTestCase when
using --keepdb
---+
 Reporter:  David Szotten  |Owner:  nobody
 Type:  Bug|   Status:  new
Component:  Testing framework  |  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 Tim Graham):

 * needs_better_patch:  0 => 1


Comment:

 `$ ./tests/runtests.py postgres_tests --settings=test_postgres -k` is
 crashing with the patch where it seems to work fine currently.

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

Re: [Django] #27267: Migrations: Need API to drop a foreign key constraint

2016-09-27 Thread Django

#27267: Migrations: Need API to drop a foreign key constraint
+--
 Reporter:  Melvyn Sopacua  |Owner:  nobody
 Type:  Bug |   Status:  new
Component:  Migrations  |  Version:  1.8
 Severity:  Normal  |   Resolution:
 Keywords:  | Triage Stage:  Unreviewed
Has patch:  0   |  Needs documentation:  0
  Needs tests:  0   |  Patch needs improvement:  0
Easy pickings:  0   |UI/UX:  0
+--
Changes (by Tim Graham):

 * type:  Uncategorized => Bug


Comment:

 Could it be a duplicate of #22761? The same error message appears there.
 If not, can you provide a minimal set of models to reproduce?

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

Re: [Django] #11078: Proxy models do not inherit META.app_label

2016-09-27 Thread Django

#11078: Proxy models do not inherit META.app_label
-+-
 Reporter:  George Song  |Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  proxy model  | Triage Stage:  Accepted
  app_label  |
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Tim Graham):

 Sure.

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

Re: [Django] #27053: Document django.contrib.auth.get_user()

2016-09-27 Thread Django

#27053: Document django.contrib.auth.get_user()
-+-
 Reporter:  Kevin Christopher|Owner:  Berker
  Henry  |  Peksag
 Type:   |   Status:  closed
  Cleanup/optimization   |
Component:  Documentation|  Version:  master
 Severity:  Normal   |   Resolution:  fixed
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Tim Graham ):

 In [changeset:"a9fefd26dc2a8dd2138475635a61e32e014b1e4f" a9fefd2]:
 {{{
 #!CommitTicketReference repository=""
 revision="a9fefd26dc2a8dd2138475635a61e32e014b1e4f"
 [1.10.x] Fixed #27053 -- Documented contrib.auth.get_user().

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

Re: [Django] #27053: Document django.contrib.auth.get_user()

2016-09-27 Thread Django

#27053: Document django.contrib.auth.get_user()
-+-
 Reporter:  Kevin Christopher|Owner:  Berker
  Henry  |  Peksag
 Type:   |   Status:  closed
  Cleanup/optimization   |
Component:  Documentation|  Version:  master
 Severity:  Normal   |   Resolution:  fixed
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Tim Graham ):

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


Comment:

 In [changeset:"f7e91cac689b28fc32ca52cdeac258ec0d58b4fc" f7e91cac]:
 {{{
 #!CommitTicketReference repository=""
 revision="f7e91cac689b28fc32ca52cdeac258ec0d58b4fc"
 Fixed #27053 -- Documented contrib.auth.get_user().
 }}}

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

Re: [Django] #27272: Add a on_delete RESTRICT handler to allow cascading deletions while protecting direct ones (was: Protected objects not deleted even if they would have been deleted via cascade any

2016-09-27 Thread Django

#27272: Add a on_delete RESTRICT handler to allow cascading deletions while
protecting direct ones
-+-
 Reporter:  Daniel Izquierdo |Owner:  nobody
 Type:  New feature  |   Status:  new
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 Simon Charette):

 * cc: Simon Charette (added)
 * version:  1.10 => master
 * type:  Bug => New feature


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

Re: [Django] #27272: Protected objects not deleted even if they would have been deleted via cascade anyway

2016-09-27 Thread Django

* stage: Unreviewed => Accepted

Comment:

Thanks for the detailed analysis Daniele!

The `on_delete` argument was introduced in
616b30227d901a7452810a9ffaa55eaf186dc9e1 to fix #7539 where there was some
discussion about `RESTRICT` but I cannot find a mention of why `PROTECT`
work this way.

I would argue that both `PROTECT` and `RESTRICT` can be useful and that
`PROTECT` should be kept this way given some users might rely on its
current behavior. What I would suggest we do here is introduce a new
`on_delete=RESTRICT` handler that mimics what the SQL one does.

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

Re: [Django] #27271: ServerFormatter should handle simple string messages with or without args

2016-09-27 Thread Django

Comment (by Tim Graham ):

In [changeset:"bcdd13de9394618cf51c7e141b418918f2f9dda5" bcdd13d]:
{{{
#!CommitTicketReference repository=""
revision="bcdd13de9394618cf51c7e141b418918f2f9dda5"
[1.10.x] Fixed #27271 -- Fixed a crash in runserver logging.

Allowed ServerFormatter to handle simple string messages or messages with
formatting arguments. The formatter will set the server_time variable on
the log record if it's required by the format string but wasn't passed in
extra parameters.

Backport of 6709ea4ae91b906742506ac0c42a3a272991001f 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/064.ab9f819492bca26346c41373e977b6f1%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #27266: assertFormError fails when trying to check a custom validation in an Admin form

2016-09-27 Thread Django

#27266: assertFormError fails when trying to check a custom validation in an 
Admin
form
-+-
 Reporter:  Diego Andrés |Owner:  nobody
  Sanabria Martín|
 Type:  Bug  |   Status:  closed
Component:  contrib.admin|  Version:  master
 Severity:  Normal   |   Resolution:  fixed
 Keywords:  unittest, admin, | Triage Stage:  Accepted
  modelform, adminform, test |
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by GitHub ):

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


Comment:

 In [changeset:"6f3c78dbe6f17997aa9d115d041bbb0318061ba7" 6f3c78d]:
 {{{
 #!CommitTicketReference repository=""
 revision="6f3c78dbe6f17997aa9d115d041bbb0318061ba7"
 Fixed #27266 -- Allowed using assertFormError()/assertFormsetError() in
 admin forms and formsets.

 Thanks Diego Andrés Sanabria Martín for the report and review.
 }}}

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

Re: [Django] #27271: ServerFormatter should handle simple string messages with or without args

2016-09-27 Thread Django

#27271: ServerFormatter should handle simple string messages with or without 
args
-+-
 Reporter:  Sergey Fursov|Owner:  Sergey Fursov
 Type:  Bug  |   Status:  closed
Component:  Utilities|  Version:  1.10
 Severity:  Release blocker  |   Resolution:  fixed
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Tim Graham ):

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


Comment:

 In [changeset:"6709ea4ae91b906742506ac0c42a3a272991001f" 6709ea4]:
 {{{
 #!CommitTicketReference repository=""
 revision="6709ea4ae91b906742506ac0c42a3a272991001f"
 Fixed #27271 -- Fixed a crash in runserver logging.

 Allowed ServerFormatter to handle simple string messages or messages with
 formatting arguments. The formatter will set the server_time variable on
 the log record if it's required by the format string but wasn't passed in
 extra parameters.
 }}}

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

Re: [Django] #26762: Allow using parts of flatpages without install the app

2016-09-27 Thread Django

#26762: Allow using parts of flatpages without install the app
-+-
 Reporter:  Vlastimil Zíma   |Owner:  Vlastimil
 |  Zíma
 Type:  Bug  |   Status:  closed
Component:  contrib.flatpages|  Version:  1.9
 Severity:  Normal   |   Resolution:  wontfix
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Vlastimil Zíma):

 `MIGRATION_MODULES` trick doesn't work for tests in 1.9. Test database
 creation runs migration with `run_syncdb=True` which suppresses the effect
 of `MIGRATION_MODULES` override. That results either in conflicts with my
 own migrations or it creates database different from the one on
 production.

 I found no way to suppress the `syncdb` in test database creation.

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

Re: [Django] #11078: Proxy models do not inherit META.app_label

2016-09-27 Thread Django

#11078: Proxy models do not inherit META.app_label
-+-
 Reporter:  George Song  |Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  proxy model  | Triage Stage:  Accepted
  app_label  |
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Jonatas CD):

 So, I'd say that, for now, it's better to document the current behavior
 and then set to discussion if it's still the expected behavior or not.
 Based on that eventually open or not a new ticket to change that. Correct?

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

Re: [Django] #27277: Error in generation of SQL query when have a ForeignKey with Model with ChoiceField

2016-09-27 Thread Django

#27277: Error in generation of SQL query when have a ForeignKey with Model with
ChoiceField
-+-
 Reporter:  Cátia Simões |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Database layer   |  Version:  1.9
  (models, ORM)  |
 Severity:  Normal   |   Resolution:  invalid
 Keywords:  SQL, QUERYSET,   | Triage Stage:
  CHOICEFIELD|  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Cátia Simões):

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


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

Re: [Django] #27274: KeyError when using RenameModel in migrations that refer to an unmanaged model in another app.

2016-09-27 Thread Django

#27274: KeyError when using RenameModel in migrations that refer to an unmanaged
model in another app.
---+--
Reporter: Dennis Ahrens |Owner: nobody
Type: Bug| Status: closed
Component: Migrations | Version: 1.10
Severity: Normal | Resolution: invalid
Keywords: | Triage Stage: Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 |UI/UX: 0
---+--
Changes (by Dennis Ahrens):

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

Comment:

Thank you for the reply. You are totally right - having migrations in the
legacy app solves the issue. It feels a little scary to have migrations
for a schema, where django should __not__ do anything with SQL, but on the
other hand it perfectly makes sense, that django needs information about
those migrations, if another app relies on this information within its
migrations.

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

Re: [Django] #27055: Model form with geometry widgets has invalid html

2016-09-27 Thread Django

#27055: Model form with geometry widgets has invalid html
-+-
 Reporter:  Antonis  |Owner:  Antonis
  Christofides   |  Christofides
 Type:  Bug  |   Status:  assigned
Component:  GIS  |  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 Antonis Christofides):

 Another problem is that the contents of the

37 matches

Mail list logo