Re: [Django] #27178: ImageField when default provided in model, it's impossible to change the value.

[Django]

#27178: ImageField when default provided in model, it's impossible to change the
value.
-+-
 Reporter:  phonkee  |Owner:  timgraham
 Type:  Bug  |   Status:  closed
Component:  Forms|  Version:  1.10
 Severity:  Release blocker  |   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 timgraham):

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


Comment:

 I retitled #27186 and am closing this as a duplicate since the patch is
 the same for both tickets.

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

Re: [Django] #27220: MultiWidget not considered in form submit

[Django]

#27220: MultiWidget not considered in form submit
--+--
 Reporter:  andreage  |Owner:  nobody
 Type:  Bug   |   Status:  closed
Component:  Forms |  Version:  master
 Severity:  Normal|   Resolution:  duplicate
 Keywords:| Triage Stage:  Unreviewed
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+--
Changes (by timgraham):

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


Comment:

 Duplicate of #27186. Please check the patch there.

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

Re: [Django] #27186: Cannot change FileInput, MultiWidget, SplitDateTimeWidget, and SelectDateWidget with model field default since Django 1.10.1 (was: Cannot change DateTimeField with default via Adm

[Django]

#27186: Cannot change FileInput, MultiWidget, SplitDateTimeWidget, and
SelectDateWidget with model field default since Django 1.10.1
-+-
 Reporter:  michael-k|Owner:  timgraham
 Type:  Bug  |   Status:  assigned
Component:  Forms|  Version:  1.10
 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
-+-

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

Re: [Django] #27220: MultiWidget not considered in form submit

[Django]

#27220: MultiWidget not considered in form submit
--+--
 Reporter:  andreage  |Owner:  nobody
 Type:  Bug   |   Status:  new
Component:  Forms |  Version:  master
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Unreviewed
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+--

Comment (by andreage):

 See also https://code.djangoproject.com/ticket/27186

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

Re: [Django] #27220: MultiWidget not considered in form submit

[Django]

#27220: MultiWidget not considered in form submit
--+--
 Reporter:  andreage  |Owner:  nobody
 Type:  Bug   |   Status:  new
Component:  Forms |  Version:  master
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Unreviewed
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+--
Changes (by andreage):

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

Re: [Django] #27220: MultiWidget not considered in form submit

[Django]

#27220: MultiWidget not considered in form submit
--+--
 Reporter:  andreage  |Owner:  nobody
 Type:  Bug   |   Status:  new
Component:  Forms |  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
--+--
Description changed by andreage:

Old description:

> I have a custom widget for a field, for example:
>
> {{{
> class TestWidget(MultiWidget):
> def __init__(self, attrs=None):
> widgets = (
> Select(choices=func_start()),
> Select(choices=func_end())
> )
> super(TestWidget, self).__init__(widgets, attrs)
>
> ...
>

> class TestModel(models.Model)
>   test = ArrayField(models.PositiveSmallIntegerField(), default=list,
> blank=True)
>

> class TestForm(forms.ModelForm):
> def __init__(self, *args, **kwargs):
> super(TestForm, self).__init__(*args, **kwargs)
> self.fields['test'].widget = TestWidget(self.facility)
> }}}
>
> It's been working fine until Django 10.0. With Django 10.1 and
> specifically due to this commit it breaks.
>
> https://github.com/django/django/commit/4bc6b939944183533ae74791d21282e613f63a96
> #diff-70af885c2725fe87eb3b99a393268d10
>
> `f.name` in this commit would be "test", but `form.data` would contain
> "test_0" and "test_1". For this reason form field content is skipped and
> not saved to the model instance.

New description:

 I have a custom widget for a field, for example:

 {{{
 class TestWidget(MultiWidget):
 def __init__(self, attrs=None):
 widgets = (
 Select(choices=func_start()),
 Select(choices=func_end())
 )
 super(TestWidget, self).__init__(widgets, attrs)

 ...


 class TestModel(models.Model)
   test = ArrayField(models.PositiveSmallIntegerField(), default=list,
 blank=True)


 class TestForm(forms.ModelForm):
 def __init__(self, *args, **kwargs):
 super(TestForm, self).__init__(*args, **kwargs)
 self.fields['test'].widget = TestWidget()
 }}}

 It's been working fine until Django 10.0. With Django 10.1 and
 specifically due to this commit it breaks.

 
https://github.com/django/django/commit/4bc6b939944183533ae74791d21282e613f63a96
 #diff-70af885c2725fe87eb3b99a393268d10

 `f.name` in this commit would be "test", but `form.data` would contain
 "test_0" and "test_1". For this reason form field content is skipped and
 not saved to the model instance.

--

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

Re: [Django] #27220: MultiWidget not considered in form submit

[Django]

#27220: MultiWidget not considered in form submit
--+--
 Reporter:  andreage  |Owner:  nobody
 Type:  Bug   |   Status:  new
Component:  Forms |  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
--+--
Description changed by andreage:

Old description:

> I have a custom widget for a field, for example:
>
> {{{
> class TestWidget(MultiWidget):
> def __init__(self, attrs=None):
> widgets = (
> Select(choices=func_start()),
> Select(choices=func_end())
> )
> super(TestWidget, self).__init__(widgets, attrs)
>
> ...
>

> class TestModel(models.Model)
>   test = ArrayField(models.PositiveSmallIntegerField(), default=list,
> blank=True)
>

> class TestForm(forms.ModelForm):
> def __init__(self, *args, **kwargs):
> super(TestForm, self).__init__(*args, **kwargs)
> self.fields['test'].widget = SlotsWidget(self.facility)
> }}}
>
> It's been working fine until Django 10.0. With Django 10.1 and
> specifically due to this commit it breaks.
>
> https://github.com/django/django/commit/4bc6b939944183533ae74791d21282e613f63a96
> #diff-70af885c2725fe87eb3b99a393268d10
>
> `f.name` in this commit would be "test", but `form.data` would contain
> "test_0" and "test_1". For this reason form field content is skipped and
> not saved to the model instance.

New description:

 I have a custom widget for a field, for example:

 {{{
 class TestWidget(MultiWidget):
 def __init__(self, attrs=None):
 widgets = (
 Select(choices=func_start()),
 Select(choices=func_end())
 )
 super(TestWidget, self).__init__(widgets, attrs)

 ...


 class TestModel(models.Model)
   test = ArrayField(models.PositiveSmallIntegerField(), default=list,
 blank=True)


 class TestForm(forms.ModelForm):
 def __init__(self, *args, **kwargs):
 super(TestForm, self).__init__(*args, **kwargs)
 self.fields['test'].widget = TestWidget(self.facility)
 }}}

 It's been working fine until Django 10.0. With Django 10.1 and
 specifically due to this commit it breaks.

 
https://github.com/django/django/commit/4bc6b939944183533ae74791d21282e613f63a96
 #diff-70af885c2725fe87eb3b99a393268d10

 `f.name` in this commit would be "test", but `form.data` would contain
 "test_0" and "test_1". For this reason form field content is skipped and
 not saved to the model instance.

--

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

Re: [Django] #27220: MultiWidget not considered in form submit

[Django]

#27220: MultiWidget not considered in form submit
--+--
 Reporter:  andreage  |Owner:  nobody
 Type:  Bug   |   Status:  new
Component:  Forms |  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
--+--
Description changed by andreage:

Old description:

> I have a custom widget for a field, for example:
>
> {{{
> class TestWidget(MultiWidget):
> def __init__(self, attrs=None):
> widgets = (
> Select(choices=func_start()),
> Select(choices=func_end())
> )
> super(TestWidget, self).__init__(widgets, attrs)
>
> ...
>

> class TestModel(models.Model)
>   test = ArrayField(models.PositiveSmallIntegerField(), default=list,
> blank=True)
>

> class TestForm(forms.ModelForm):
> def __init__(self, *args, **kwargs):
> super(TestForm, self).__init__(*args, **kwargs)
> self.fields['test'].widget = SlotsWidget(self.facility)
> }}}
>
> It's been working fine until Django 10.0. With Django 10.1 and
> specifically due to this commit it breaks.
>
> https://github.com/django/django/commit/4bc6b939944183533ae74791d21282e613f63a96
> #diff-70af885c2725fe87eb3b99a393268d10
>
> `f.name` in this commit would be "test", but `form.data` would contain
> "test_0" and "test_1". For this reason form field content is skipped and
> not saved to the form instance.

New description:

 I have a custom widget for a field, for example:

 {{{
 class TestWidget(MultiWidget):
 def __init__(self, attrs=None):
 widgets = (
 Select(choices=func_start()),
 Select(choices=func_end())
 )
 super(TestWidget, self).__init__(widgets, attrs)

 ...


 class TestModel(models.Model)
   test = ArrayField(models.PositiveSmallIntegerField(), default=list,
 blank=True)


 class TestForm(forms.ModelForm):
 def __init__(self, *args, **kwargs):
 super(TestForm, self).__init__(*args, **kwargs)
 self.fields['test'].widget = SlotsWidget(self.facility)
 }}}

 It's been working fine until Django 10.0. With Django 10.1 and
 specifically due to this commit it breaks.

 
https://github.com/django/django/commit/4bc6b939944183533ae74791d21282e613f63a96
 #diff-70af885c2725fe87eb3b99a393268d10

 `f.name` in this commit would be "test", but `form.data` would contain
 "test_0" and "test_1". For this reason form field content is skipped and
 not saved to the model instance.

--

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

Re: [Django] #27220: MultiWidget not considered in form submit

[Django]

#27220: MultiWidget not considered in form submit
--+--
 Reporter:  andreage  |Owner:  nobody
 Type:  Bug   |   Status:  new
Component:  Forms |  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 andreage):

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


Old description:

> I have a custom widget for a field, for example:
>
> {{{
> class TestWidget(MultiWidget):
> def __init__(self, attrs=None):
> widgets = (
> Select(choices=func_start()),
> Select(choices=func_end())
> )
> super(TestWidget, self).__init__(widgets, attrs)
>
> ...
>

> class TestModel(models.Model)
>   test = ArrayField(models.PositiveSmallIntegerField(), default=list,
> blank=True)
>

> class TestForm(forms.ModelForm):
> def __init__(self, *args, **kwargs):
> super(TestForm, self).__init__(*args, **kwargs)
> self.fields['test'].widget = SlotsWidget(self.facility)
> }}}
>
> It's been working fine until Django 10.0. With Django 10.1 and
> specifically due to this commit it breaks.
>
> https://github.com/django/django/commit/4bc6b939944183533ae74791d21282e613f63a96
> #diff-70af885c2725fe87eb3b99a393268d10
>
> `f.name` in this commit would be "test", but `form.data` would contain
> "test_0" and "test_1". For this reason form content is skipped and not
> saved to the form instance.

New description:

 I have a custom widget for a field, for example:

 {{{
 class TestWidget(MultiWidget):
 def __init__(self, attrs=None):
 widgets = (
 Select(choices=func_start()),
 Select(choices=func_end())
 )
 super(TestWidget, self).__init__(widgets, attrs)

 ...


 class TestModel(models.Model)
   test = ArrayField(models.PositiveSmallIntegerField(), default=list,
 blank=True)


 class TestForm(forms.ModelForm):
 def __init__(self, *args, **kwargs):
 super(TestForm, self).__init__(*args, **kwargs)
 self.fields['test'].widget = SlotsWidget(self.facility)
 }}}

 It's been working fine until Django 10.0. With Django 10.1 and
 specifically due to this commit it breaks.

 
https://github.com/django/django/commit/4bc6b939944183533ae74791d21282e613f63a96
 #diff-70af885c2725fe87eb3b99a393268d10

 `f.name` in this commit would be "test", but `form.data` would contain
 "test_0" and "test_1". For this reason form field content is skipped and
 not saved to the form instance.

--

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

[Django] #27220: MultiWidget not considered in form submit

[Django]

#27220: MultiWidget not considered in form submit
+
 Reporter:  andreage|  Owner:  nobody
 Type:  Bug | Status:  new
Component:  Forms   |Version:  1.10
 Severity:  Normal  |   Keywords:
 Triage Stage:  Unreviewed  |  Has patch:  0
Easy pickings:  0   |  UI/UX:  0
+
 I have a custom widget for a field, for example:

 {{{
 class TestWidget(MultiWidget):
 def __init__(self, attrs=None):
 widgets = (
 Select(choices=func_start()),
 Select(choices=func_end())
 )
 super(TestWidget, self).__init__(widgets, attrs)

 ...


 class TestModel(models.Model)
   test = ArrayField(models.PositiveSmallIntegerField(), default=list,
 blank=True)


 class TestForm(forms.ModelForm):
 def __init__(self, *args, **kwargs):
 super(TestForm, self).__init__(*args, **kwargs)
 self.fields['test'].widget = SlotsWidget(self.facility)
 }}}

 It's been working fine until Django 10.0. With Django 10.1 and
 specifically due to this commit it breaks.

 
https://github.com/django/django/commit/4bc6b939944183533ae74791d21282e613f63a96
 #diff-70af885c2725fe87eb3b99a393268d10

 `f.name` in this commit would be "test", but `form.data` would contain
 "test_0" and "test_1". For this reason form content is skipped and not
 saved to the form instance.

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

Re: [Django] #24941: Add get_exclude() hook to BaseModelAdmin

[Django]

#24941: Add get_exclude() hook to BaseModelAdmin
---+---
 Reporter:  peterfarrell   |Owner:  olasitarska
 Type:  New feature|   Status:  assigned
Component:  contrib.admin  |  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 zborboa-g):

 * cc: zborboa@… (added)


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

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

Re: [Django] #27211: Include HTTP-caching headers to "304 Not Modified" responses

[Django]

#27211: Include HTTP-caching headers to "304 Not Modified" responses
---+
 Reporter:  renskiy|Owner:  renskiy
 Type:  Bug|   Status:  assigned
Component:  HTTP handling  |  Version:  1.10
 Severity:  Normal |   Resolution:
 Keywords: | Triage Stage:  Accepted
Has patch:  1  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+
Changes (by timgraham):

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


Old description:

> Most browsers can cache responses with 304 HTTP code. So why not to
> include such headers to response if necessary.
>
> '''UPDATE''':
> According to the [https://tools.ietf.org/html/rfc7232 RFC7232] all "304
> Not Modified" responses must include "Cache-Control" and "Expires"
> headers that would have been sent in a corresponding "200 OK" response.
>
> See [https://tools.ietf.org/html/rfc7232#section-4.1 Section 4.1 of
> RFC7232]

New description:

 According to [https://tools.ietf.org/html/rfc7232#section-4.1 RFC7232] all
 "304 Not Modified" responses must include "Cache-Control" and "Expires"
 headers that would have been sent in a corresponding "200 OK" response.

--

Comment:

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

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

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

Re: [Django] #27219: Emoji don't work in TextFields using Oracle backend

[Django]

#27219: Emoji don't work in TextFields using Oracle backend
-+-
 Reporter:  dmedvinsky   |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  1.10
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  oracle, unicode  | Triage Stage:
 |  Unreviewed
Has patch:  1|  Needs documentation:  0
  Needs tests:  1|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by dmedvinsky):

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

[Django] #27219: Emoji don't work in TextFields using Oracle backend

[Django]

#27219: Emoji don't work in TextFields using Oracle backend
--+
 Reporter:  dmedvinsky|  Owner:  nobody
 Type:  Bug   | Status:  new
Component:  Database layer (models, ORM)  |Version:  1.10
 Severity:  Normal|   Keywords:  oracle,
  |  unicode
 Triage Stage:  Unreviewed|  Has patch:  1
Easy pickings:  0 |  UI/UX:  0
--+
 When using cx_Oracle as a backend, I can't use Emoji in TextFields, which
 are stored as NCLOBs in the database. When inputting an emoji and saving
 them in the database, upon retrieving I get four replacement charaters (�)
 per emoji instead.

 Django
 
[https://github.com/django/django/blob/18c72d59e0807dae75ac2c34890d08c1e0972d0a/django/db/backends/oracle/base.py#L44
 uses hardcoded NLS_LANG=".UTF8"] variable, which is outdated, only
 supports Unicode standard version 3 and cannot properly store 4-byte
 characters. [https://docs.oracle.com/database/121/NLSPG/ch6unicode.htm
 #NLSPG-GUID-EB57AB68-A390-4814-81DD-6B78D33310CC The Oracle documentation
 recommends] using the AL32UTF8 encoding instead, which supports latest
 Unicode standard and stores 4-byte characters properly.

 The change that fixes the emoji for me:
 https://github.com/django/django/pull/7241

 I recognize that it needs some tests, so I seek the help from those with
 better knowledge of Django test cases than me. If someone can kindly
 direct me, I can create the test for this 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/053.9b26a78c0e6be4f9d87524387e5c12fa%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #27214: The skipIfDBFeature decorators and its variants should respect their defined wrapped order and test case inheritance.

[Django]

#27214: The skipIfDBFeature decorators and its variants should respect their
defined wrapped order and test case inheritance.
-+-
 Reporter:  charettes|Owner:  charettes
 Type:   |   Status:  closed
  Cleanup/optimization   |
Component:  Testing framework|  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:  0|UI/UX:  0
-+-
Changes (by Simon Charette ):

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


Comment:

 In [changeset:"18c72d59e0807dae75ac2c34890d08c1e0972d0a" 18c72d59]:
 {{{
 #!CommitTicketReference repository=""
 revision="18c72d59e0807dae75ac2c34890d08c1e0972d0a"
 Fixed #27214 -- Made skip db features decorators respect wrapping order
 and inheritance.
 }}}

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

Re: [Django] #27214: The skipIfDBFeature decorators and its variants should respect their defined wrapped order and test case inheritance.

[Django]

#27214: The skipIfDBFeature decorators and its variants should respect their
defined wrapped order and test case inheritance.
-+-
 Reporter:  charettes|Owner:  charettes
 Type:   |   Status:  new
  Cleanup/optimization   |
Component:  Testing framework|  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Ready for
 |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by timgraham):

 * stage:  Unreviewed => Ready for checkin


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

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

Re: [Django] #27203: Update tests that use assertQuerysetEqual lambda o: o to use assertSequenceEqual

[Django]

#27203: Update tests that use assertQuerysetEqual lambda o: o to use
assertSequenceEqual
--+
 Reporter:  timgraham |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  closed
Component:  Core (Other)  |  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:"0627858ada32e13bafef74f9541dafd8c854ae25" 0627858a]:
 {{{
 #!CommitTicketReference repository=""
 revision="0627858ada32e13bafef74f9541dafd8c854ae25"
 Fixed a couple ordering dependent tests on Oracle broken by refs #27203.
 }}}

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

Re: [Django] #27216: Wrong import location in deprecation message

[Django]

#27216: Wrong import location in deprecation message
---+---
 Reporter:  claudep|Owner:  deltaskelta
 Type:  Bug|   Status:  closed
Component:  contrib.admin  |  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:"ca825b1779097168545b79c96317da3e1780282c" ca825b1]:
 {{{
 #!CommitTicketReference repository=""
 revision="ca825b1779097168545b79c96317da3e1780282c"
 [1.10.x] Fixed #27216 -- Corrected import location in admin deprecation
 messages.

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

Re: [Django] #27216: Wrong import location in deprecation message

[Django]

#27216: Wrong import location in deprecation message
---+---
 Reporter:  claudep|Owner:  deltaskelta
 Type:  Bug|   Status:  closed
Component:  contrib.admin  |  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:"07760d07146816bd9aa32786891bb24f467d713d" 07760d07]:
 {{{
 #!CommitTicketReference repository=""
 revision="07760d07146816bd9aa32786891bb24f467d713d"
 [1.9.x] Fixed #27216 -- Corrected import location in admin deprecation
 messages.

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

Re: [Django] #27216: Wrong import location in deprecation message

[Django]

#27216: Wrong import location in deprecation message
---+---
 Reporter:  claudep|Owner:  deltaskelta
 Type:  Bug|   Status:  closed
Component:  contrib.admin  |  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:"7148929a5ef4a5fb8332a43f7d39394618313476" 7148929]:
 {{{
 #!CommitTicketReference repository=""
 revision="7148929a5ef4a5fb8332a43f7d39394618313476"
 Fixed #27216 -- Corrected import location in admin deprecation messages.
 }}}

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

Re: [Django] #26708: Update the contributing tutorial to use GitHub workflow

[Django]

#26708: Update the contributing tutorial to use GitHub workflow
-+-
 Reporter:  nnja |Owner:
 Type:   |  deltaskelta
  Cleanup/optimization   |   Status:  assigned
Component:  Documentation|  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-

Comment (by timgraham):

 The contributing tutorial is `docs/intro/contributing.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/062.f0db2b33f60ba09657280e2c23e9260e%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #26708: Update the contributing tutorial to use GitHub workflow

[Django]

#26708: Update the contributing tutorial to use GitHub workflow
-+-
 Reporter:  nnja |Owner:
 Type:   |  deltaskelta
  Cleanup/optimization   |   Status:  assigned
Component:  Documentation|  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-

Comment (by deltaskelta):

 Just to make sure I understand, It looks like:

 1. The majority of the documentation that needs to be fixed is in the
 contributing/writing_code and contributing/committing_code sections,
 2. Removing all references to patches. I'm assuming the proper substitute
 would be the word "pull request" with the proper verb for the sentence?

 Everything else seems to be clearly stated, but I just want to verify that
 #1 would be the sections where the bulk of the reorganizing needs to take
 place.

--
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.de1572da6e4e016fbfa6c4097d266a9a%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 (was: GeoDjango issues on Django 1.11.dev version)

[Django]

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

 * stage:  Unreviewed => Accepted


Comment:

 Bisected the regression to 7fc4c1db627807874966e4f96b34cff7c9af886f. Steps
 to reproduce and a sample project are [https://groups.google.com/d/msg
 /django-users/5XHFjuRmJkU/fsReJVrPAQAJ on django-users].

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

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

[Django]

#20705: Allow customizing the email field name for PasswordResetForm
--+
 Reporter:  Cloudream |Owner:  nobody
 Type:  New feature   |   Status:  new
Component:  contrib.auth  |  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 AleksejManaev):

 * cc: AleksejManaev (added)


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

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

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

[Django]

#20705: Allow customizing the email field name for PasswordResetForm
--+-
 Reporter:  Cloudream |Owner:  mlevental
 Type:  New feature   |   Status:  assigned
Component:  contrib.auth  |  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 mlevental):

 * owner:  nobody => mlevental
 * 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.5e7fdc59920c8e3a367c9ce6391366ee%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #26210: Make the SMTP more efficient if an error passes silently when creating a connection

[Django]

#26210: Make the SMTP more efficient if an error passes silently when creating a
connection
-+-
 Reporter:  aptiko   |Owner:  mlevental
 Type:   |   Status:  assigned
  Cleanup/optimization   |
Component:  Core (Mail)  |  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 AleksejManaev):

 * cc: AleksejManaev (added)


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

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

Re: [Django] #26210: Make the SMTP more efficient if an error passes silently when creating a connection

[Django]

#26210: Make the SMTP more efficient if an error passes silently when creating a
connection
-+-
 Reporter:  aptiko   |Owner:  mlevental
 Type:   |   Status:  assigned
  Cleanup/optimization   |
Component:  Core (Mail)  |  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 mlevental):

 * status:  new => assigned
 * owner:  nobody => mlevental
 * cc: m.levental@… (added)


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

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

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

[Django]

#20705: Allow customizing the email field name for PasswordResetForm
--+
 Reporter:  Cloudream |Owner:  nobody
 Type:  New feature   |   Status:  new
Component:  contrib.auth  |  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 mlevental):

 * cc: m.levental@… (added)


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

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

Re: [Django] #27216: Wrong import location in deprecation message

[Django]

#27216: Wrong import location in deprecation message
---+---
 Reporter:  claudep|Owner:  deltaskelta
 Type:  Bug|   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:  1  |UI/UX:  0
---+---

Comment (by deltaskelta):

 Pull request: https://github.com/django/django/pull/7242

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

Re: [Django] #27203: Update tests that use assertQuerysetEqual lambda o: o to use assertSequenceEqual

[Django]

#27203: Update tests that use assertQuerysetEqual lambda o: o to use
assertSequenceEqual
--+
 Reporter:  timgraham |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  closed
Component:  Core (Other)  |  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:  new => closed
 * resolution:   => fixed


Comment:

 In [changeset:"0c1f71635f8a3f32195e1573fe929c7d88a78511" 0c1f716]:
 {{{
 #!CommitTicketReference repository=""
 revision="0c1f71635f8a3f32195e1573fe929c7d88a78511"
 Fixed #27203 -- Replaced assertQuerysetEqual(..., lambda o: o) with
 assertSequenceEqual().
 }}}

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

Re: [Django] #27215: Document new location of jquery in v1.10

[Django]

#27215: Document new location of jquery in v1.10
-+-
 Reporter:  rerb |Owner:  nobody
 Type:   |   Status:  closed
  Cleanup/optimization   |
Component:  Documentation|  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 timgraham):

 * status:  new => closed
 * needs_better_patch:   => 0
 * component:  contrib.admin => Documentation
 * needs_tests:   => 0
 * needs_docs:   => 0
 * resolution:   => invalid


Comment:

 This is a change in Django 1.9 and it is documented in the 1.9 release
 notes (788071e22d632e5f353d193f9e3bde3738d49879).

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

Re: [Django] #27218: Return LogEntry instances from log_addition, log_change, log_deletion

[Django]

#27218: Return LogEntry instances from log_addition, log_change, log_deletion
---+
 Reporter:  claudep|Owner:  nobody
 Type:  New feature|   Status:  new
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 timgraham):

 * stage:  Unreviewed => Accepted


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

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

Re: [Django] #27217: GeoDjango issues on Django 1.11.dev version

[Django]

#27217: GeoDjango issues on Django 1.11.dev version
-+--
 Reporter:  MVSatish |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  GIS  |  Version:  master
 Severity:  Release blocker  |   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 MVSatish):

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


Old description:

> Am Using postgis as a backend and makemigrations threw back the error:
>

> {{{
> Traceback (most recent call last):
>   File "manage.py", line 22, in 
> execute_from_command_line(sys.argv)
>   File "/home/satish/work/django/django/core/management/__init__.py",
> line 366, in execute_from_command_line
> utility.execute()
>   File "/home/satish/work/django/django/core/management/__init__.py",
> line 358, in execute
> self.fetch_command(subcommand).run_from_argv(self.argv)
>   File "/home/satish/work/django/django/core/management/base.py", line
> 294, in run_from_argv
> self.execute(*args, **cmd_options)
>   File "/home/satish/work/django/django/core/management/base.py", line
> 345, in execute
> output = self.handle(*args, **options)
>   File
> "/home/satish/work/django/django/core/management/commands/makemigrations.py",
> line 173, in handle
> migration_name=self.migration_name,
>   File "/home/satish/work/django/django/db/migrations/autodetector.py",
> line 47, in changes
> changes = self._detect_changes(convert_apps, graph)
>   File "/home/satish/work/django/django/db/migrations/autodetector.py",
> line 198, in _detect_changes
> self._optimize_migrations()
>   File "/home/satish/work/django/django/db/migrations/autodetector.py",
> line 362, in _optimize_migrations
> migration.operations =
> MigrationOptimizer().optimize(migration.operations, app_label=app_label)
>   File "/home/satish/work/django/django/db/migrations/optimizer.py", line
> 38, in optimize
> result = self.optimize_inner(operations, app_label)
>   File "/home/satish/work/django/django/db/migrations/optimizer.py", line
> 53, in optimize_inner
> result = operation.reduce(other, in_between, app_label)
>   File
> "/home/satish/work/django/django/db/migrations/operations/models.py",
> line 213, in reduce
> return super(CreateModel, self).reduce(operation, in_between,
> app_label=app_label)
>   File
> "/home/satish/work/django/django/db/migrations/operations/models.py",
> line 39, in reduce
> not operation.references_model(self.name, app_label)
>   File
> "/home/satish/work/django/django/db/migrations/operations/models.py",
> line 119, in references_model
> model_app_label, model_name = self.model_to_key(model)
>   File
> "/home/satish/work/django/django/db/migrations/operations/models.py",
> line 133, in model_to_key
> return model._meta.app_label, model._meta.object_name
> AttributeError: type object 'SpatialRefSysMixin' has no attribute '_meta'
>
> }}}
>
> Is GeoDjango ready for 1.11 dev version yet?

New description:

 Am Using postgis as a backend and makemigrations threw back the error:


 {{{
 Traceback (most recent call last):
   File "manage.py", line 22, in 
 execute_from_command_line(sys.argv)
   File "/home/satish/work/django/django/core/management/__init__.py", line
 366, in execute_from_command_line
 utility.execute()
   File "/home/satish/work/django/django/core/management/__init__.py", line
 358, in execute
 self.fetch_command(subcommand).run_from_argv(self.argv)
   File "/home/satish/work/django/django/core/management/base.py", line
 294, in run_from_argv
 self.execute(*args, **cmd_options)
   File "/home/satish/work/django/django/core/management/base.py", line
 345, in execute
 output = self.handle(*args, **options)
   File
 "/home/satish/work/django/django/core/management/commands/makemigrations.py",
 line 173, in handle
 migration_name=self.migration_name,
   File "/home/satish/work/django/django/db/migrations/autodetector.py",
 line 47, in changes
 changes = self._detect_changes(convert_apps, graph)
   File "/home/satish/work/django/django/db/migrations/autodetector.py",
 line 198, in _detect_changes
 self._optimize_migrations()
   File "/home/satish/work/django/django/db/migrations/autodetector.py",
 line 362, in _optimize_migrations
 migration.operations =
 MigrationOptimizer().optimize(migration.operations, app_label=app_label)
   File "/home/satish/work/django/django/db/migrations/optimizer.py", line
 38, in optimize
 result = self.optimize_inner(operations, app_label)
   File 

[Django] #27218: Return LogEntry instances from log_addition, log_change, log_deletion

[Django]

#27218: Return LogEntry instances from log_addition, log_change, log_deletion
-+
   Reporter:  claudep|  Owner:  nobody
   Type:  New feature| Status:  new
  Component:  contrib.admin  |Version:  master
   Severity:  Normal |   Keywords:
   Triage Stage:  Unreviewed |  Has patch:  0
Needs documentation:  0  |Needs tests:  0
Patch needs improvement:  0  |  Easy pickings:  0
  UI/UX:  0  |
-+
 For customized `ModelAdmin` classes, it might be handy to have access to
 the created LogEntry instances in inherited methods to be able to
 customize the logging behavior (django-reversion has a use case for that).

 I suggest to return the LogEntry instance from those methods (which
 currently don't return anything).

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

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

[Django] #27217: GeoDjango issues on Django 1.11.dev version

[Django]

#27217: GeoDjango issues on Django 1.11.dev version
-+
 Reporter:  MVSatish |  Owner:  nobody
 Type:  Bug  | Status:  new
Component:  GIS  |Version:  master
 Severity:  Release blocker  |   Keywords:
 Triage Stage:  Unreviewed   |  Has patch:  0
Easy pickings:  0|  UI/UX:  0
-+
 Am Using postgis as a backend and makemigrations threw back the error:


 {{{
 Traceback (most recent call last):
   File "manage.py", line 22, in 
 execute_from_command_line(sys.argv)
   File "/home/satish/work/django/django/core/management/__init__.py", line
 366, in execute_from_command_line
 utility.execute()
   File "/home/satish/work/django/django/core/management/__init__.py", line
 358, in execute
 self.fetch_command(subcommand).run_from_argv(self.argv)
   File "/home/satish/work/django/django/core/management/base.py", line
 294, in run_from_argv
 self.execute(*args, **cmd_options)
   File "/home/satish/work/django/django/core/management/base.py", line
 345, in execute
 output = self.handle(*args, **options)
   File
 "/home/satish/work/django/django/core/management/commands/makemigrations.py",
 line 173, in handle
 migration_name=self.migration_name,
   File "/home/satish/work/django/django/db/migrations/autodetector.py",
 line 47, in changes
 changes = self._detect_changes(convert_apps, graph)
   File "/home/satish/work/django/django/db/migrations/autodetector.py",
 line 198, in _detect_changes
 self._optimize_migrations()
   File "/home/satish/work/django/django/db/migrations/autodetector.py",
 line 362, in _optimize_migrations
 migration.operations =
 MigrationOptimizer().optimize(migration.operations, app_label=app_label)
   File "/home/satish/work/django/django/db/migrations/optimizer.py", line
 38, in optimize
 result = self.optimize_inner(operations, app_label)
   File "/home/satish/work/django/django/db/migrations/optimizer.py", line
 53, in optimize_inner
 result = operation.reduce(other, in_between, app_label)
   File
 "/home/satish/work/django/django/db/migrations/operations/models.py", line
 213, in reduce
 return super(CreateModel, self).reduce(operation, in_between,
 app_label=app_label)
   File
 "/home/satish/work/django/django/db/migrations/operations/models.py", line
 39, in reduce
 not operation.references_model(self.name, app_label)
   File
 "/home/satish/work/django/django/db/migrations/operations/models.py", line
 119, in references_model
 model_app_label, model_name = self.model_to_key(model)
   File
 "/home/satish/work/django/django/db/migrations/operations/models.py", line
 133, in model_to_key
 return model._meta.app_label, model._meta.object_name
 AttributeError: type object 'SpatialRefSysMixin' has no attribute '_meta'

 }}}

 Is GeoDjango ready for 1.11 dev version yet?

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

Re: [Django] #26708: Update the contributing tutorial to use GitHub workflow

[Django]

#26708: Update the contributing tutorial to use GitHub workflow
-+-
 Reporter:  nnja |Owner:
 Type:   |  deltaskelta
  Cleanup/optimization   |   Status:  assigned
Component:  Documentation|  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-
Changes (by deltaskelta):

 * owner:  nobody => deltaskelta
 * 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/062.a38d87bb9397fe96544d5f16d6a5645a%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #27216: Wrong import location in deprecation message

[Django]

#27216: Wrong import location in deprecation message
---+---
 Reporter:  claudep|Owner:  deltaskelta
 Type:  Bug|   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:  1  |UI/UX:  0
---+---
Changes (by deltaskelta):

 * owner:  nobody => deltaskelta
 * 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/065.ac0ad5f8f1e69dda404a14bd60c0eb8d%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

[Django] #27216: Wrong import location in deprecation message

[Django]

#27216: Wrong import location in deprecation message
-+
   Reporter:  claudep|  Owner:  nobody
   Type:  Bug| Status:  new
  Component:  contrib.admin  |Version:  master
   Severity:  Normal |   Keywords:
   Triage Stage:  Accepted   |  Has patch:  0
Needs documentation:  0  |Needs tests:  0
Patch needs improvement:  0  |  Easy pickings:  1
  UI/UX:  0  |
-+
 Two contrib.admin deprecation message mention: `Use
 django.utils.safestring.format_html(), format_html_join(), or mark_safe()
 instead.`

 `mark_safe` is indeed in `django.utils.safestring`, but the `format_html`
 utilities are in `django.utils.html`.

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

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

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

[Django]

#23155: Add request attr to user_login_failed signal
--+
 Reporter:  anonymous |Owner:  nobody
 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:  1
Easy pickings:  0 |UI/UX:  0
--+
Changes (by AleksejManaev):

 * cc: AleksejManaev (added)


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

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

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

[Django]

#23155: Add request attr to user_login_failed signal
--+
 Reporter:  anonymous |Owner:  nobody
 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:  1
Easy pickings:  0 |UI/UX:  0
--+
Changes (by mlevental):

 * cc: m.levental@… (added)


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

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

Re: [Django] #25187: Make request available in authentication backends

[Django]

#25187: Make request available in authentication backends
-+-
 Reporter:  carljm   |Owner:  Tim
 |  Graham 
 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:  1
Easy pickings:  0|UI/UX:  0
-+-
Changes (by mlevental):

 * cc: m.levental@… (added)


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

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

Re: [Django] #18763: Shortcut to get users by permission

[Django]

#18763: Shortcut to get users by permission
--+
 Reporter:  shelldweller  |Owner:  berkerpeksag
 Type:  New feature   |   Status:  assigned
Component:  contrib.auth  |  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 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/070.8796c7e46ae6160ebf37636b82b88d5a%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

[Django]

#25251: Inconsistent availability of data migrations in TransactionTestCase when
using --keepdb
---+
 Reporter:  davidszotten   |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:  0
Easy pickings:  0  |UI/UX:  0
---+
Changes (by romgar):

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