date:20200624

Re: [Django] #31737: Strange admin behaviour on Django 3.1b1 with Firefox

2020-06-24 Thread Django

#31737: Strange admin behaviour on Django 3.1b1 with Firefox
-+--
 Reporter:  Claude Paroz |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  contrib.admin|  Version:  3.1
 Severity:  Release blocker  |   Resolution:  invalid
 Keywords:   | Triage Stage:  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+--

Comment (by Carlton Gibson):

 No worries! Always happy to look. :)

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/065.9b9dd4a01c0ea2a52afdfd6f18d7feae%40djangoproject.com.

[Django] #31742: Not working model on 3.1 (lazy reference)

2020-06-24 Thread Django

#31742: Not working model on 3.1 (lazy reference)
+
   Reporter:  Ignacio Santolin  |  Owner:  nobody
   Type:  Bug   | Status:  new
  Component:  Migrations|Version:  3.1
   Severity:  Release blocker   |   Keywords:
   Triage Stage:  Unreviewed|  Has patch:  0
Needs documentation:  0 |Needs tests:  0
Patch needs improvement:  0 |  Easy pickings:  0
  UI/UX:  0 |
+
 When i run "python3 manage.py migrate" on Django 3.1b1 shows me that error
 **(Please, note that the code works well in 3.0)**


 {{{
 ValueError: The field DJ_RegLogin.Content.category was declared with a
 lazy reference to 'dj_reglogin.category', but app 'dj_reglogin' isn't
 installed.
 }}}



 model.py (Conflict Part)
 {{{
 class Category(models.Model):
 title = models.CharField(max_length=100, db_index=True)
 slug = models.SlugField(max_length=100, db_index=True)

 class Meta:
 verbose_name = 'Category'
 verbose_name_plural = 'Categories'

 def __str__(self):
 return self.title

 def get_absolute_url(self):
 return reverse('view_blog_category', None, kwargs={'slug':
 self.slug})


 class Content(models.Model):
 title = models.CharField(max_length=100, unique=True)
 slug = models.SlugField(max_length=100, unique=True)
 body = RichTextField(config_name='default')
 posted = models.DateTimeField(db_index=True, auto_now_add=True)
 sites = models.ManyToManyField(Site)
 ip = models.GenericIPAddressField(editable=False)
 category = models.ForeignKey(Category, on_delete=models.CASCADE)
 user = models.ForeignKey(User, on_delete=models.CASCADE, null=False,
 blank=False, editable=False)
 status = models.CharField(max_length=10, choices=STATUS_CHOICES,
 default='draft')

 def __str__(self):
 return self.title

 def get_absolute_url(self):
 return reverse('view_blog_post', None, kwargs={'slug': self.slug})
 }}}

 settings.py (Related to issue part)

 {{{
 INSTALLED_APPS = [
 'DJ_RegLogin',
 'django.contrib.admin',
 'django.contrib.auth',
 'django.contrib.contenttypes',
 'django.contrib.sessions',
 'django.contrib.messages',
 'django.contrib.staticfiles',
 'social_django',
 'ckeditor',
 'django.contrib.sites',
 'django.contrib.flatpages',
 'django.contrib.sitemaps',
 ]
 }}}


 apps.py
 {{{
 from django.apps import AppConfig


 class DJ_RegLoginConfig(AppConfig):
 name = 'DJ_RegLogin'
 verbose_name = "Contents"
 }}}

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/052.3594fe00bd7a5e304da56c5c44c3b43e%40djangoproject.com.

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

2020-06-24 Thread Django

#26761: Add 'help_text' property to methods in ModelAdmin.list_display
---+--
 Reporter:  Derek Hohls|Owner:  Hasan Ramezani
 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:  0
Easy pickings:  0  |UI/UX:  0
---+--

Comment (by Mariusz Felisiak ):

 In [changeset:"fbe82f82555bc25dccb476c749ca062f0b522be3" fbe82f82]:
 {{{
 #!CommitTicketReference repository=""
 revision="fbe82f82555bc25dccb476c749ca062f0b522be3"
 Refs #26761 -- Removed extra space in admin change list result header.
 }}}

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/067.89ba10ad74a3db532ae4f4c6f9b6f6e5%40djangoproject.com.

Re: [Django] #31741: Admin site applies formfield_overrides for parent field class to instance of a child class

2020-06-24 Thread Django

#31741: Admin site applies formfield_overrides for parent field class to 
instance
of a child class
---+--
 Reporter:  Mark Gregson   |Owner:  nobody
 Type:  Bug|   Status:  closed
Component:  contrib.admin  |  Version:  2.2
 Severity:  Normal |   Resolution:  wontfix
 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 Mark Gregson):

 It's unfortunate that these different use-cases for creating custom model
 fields are not handled equally well by the admin options, but thanks for
 the information, I'll have a look at writing a note for the docs.

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

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

Re: [Django] #31741: Admin site applies formfield_overrides for parent field class to instance of a child class

2020-06-24 Thread Django

#31741: Admin site applies formfield_overrides for parent field class to 
instance
of a child class
---+--
 Reporter:  Mark Gregson   |Owner:  nobody
 Type:  Bug|   Status:  closed
Component:  contrib.admin  |  Version:  2.2
 Severity:  Normal |   Resolution:  wontfix
 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 felixxm):

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


Comment:

 It is expected behavior, see #10059.
 
[https://docs.djangoproject.com/en/3.0/ref/contrib/admin/#django.contrib.admin.ModelAdmin.formfield_overrides
 Docs] improvements are always welcome, please feel-free to send PR with
 clarification.

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/066.f2846827094c8280eb938db1871552e2%40djangoproject.com.

Re: [Django] #31358: Increase default password salt size in BasePasswordHasher.

2020-06-24 Thread Django

#31358: Increase default password salt size in BasePasswordHasher.
--+
 Reporter:  Jon Moroney   |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  Utilities |  Version:  master
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  1
  Needs tests:  0 |  Patch needs improvement:  1
Easy pickings:  0 |UI/UX:  0
--+

Comment (by Jon Moroney):

 I've made a new PR to convert the salt function to work in bits rather
 than in character length. I've also set the entropy value to 128 bits.

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

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/066.726383abedfad8625b00f5ed5783961f%40djangoproject.com.

[Django] #31741: Admin site applies formfield_overrides for parent field class to instance of a child class

2020-06-24 Thread Django

#31741: Admin site applies formfield_overrides for parent field class to 
instance
of a child class
-+
   Reporter:  Mark Gregson   |  Owner:  nobody
   Type:  Bug| Status:  new
  Component:  contrib.admin  |Version:  2.2
   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  |
-+
 If I have a custom model field that inherits from a builtin field and then
 use formfield_overrides to customise the form for the builtin field, those
 customisations are also applied to the custom field.

 In this example, the override will also apply to a `CustomField` field on
 the model.

 {{{#!python
 class CustomField(models.TextField):
 ...

 class SomeModelAdmin(admin.ModelAdmin):
 formfield_overrides = {
 models.TextField: {"widget": forms.Textarea},
 }
 }}}

 In my situation I am using a custom bleached field that sets a different
 default widget in its `formfield` method and it is counterintuitive to me
 that overriding `TextField` also overrides the custom implementation.  I
 expect that it would only override fields matching the class precisely,
 ie, override fields declared as `TextField` instances but not those
 declared as `CustomField`.

 The code that implements this behaviour is
 `BaseModelAdmin.formfield_for_dbfield()` which traverses the MRO looking
 for any matching overrides.
 
https://github.com/django/django/blob/master/django/contrib/admin/options.py#L179-L184

 I discovered it working with 2.2. The code looks unchanged from 2.2 to
 master, although I haven't tested in master.

 If there is no appetite to change this behaviour, could break some folk's
 implementations, a note in the docs would be nice.

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/051.e7d3805ae9c1e7157591bb68b4a1f4e0%40djangoproject.com.

Re: [Django] #31740: Part 4 of the tutorial incorrectly uses a namespaced url

2020-06-24 Thread Django

#31740: Part 4 of the tutorial incorrectly uses a namespaced url
-+-
 Reporter:  Max  |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Documentation|  Version:  3.0
 Severity:  Normal   |   Resolution:  invalid
 Keywords:  documentation,   | Triage Stage:
  namespace, error   |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-
Changes (by felixxm):

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


Comment:

 Namespacing URL names are already described in
 [https://docs.djangoproject.com/en/3.0/intro/tutorial03/#namespacing-url-
 names tutorial 03], moreover `app_name` is also included in
 [https://docs.djangoproject.com/en/3.0/intro/tutorial03/#namespacing-url-
 names Tutorial 4]. All works for me.

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/066.8c7f7cecc3aa5f22f86bdf2406c23fcb%40djangoproject.com.

Re: [Django] #29112: Make it easier to update specific keys within nested Django JSONField data.

2020-06-24 Thread Django

#29112: Make it easier to update specific keys within nested Django JSONField 
data.
-+-
 Reporter:  Michael  |Owner:  Asif
 |  Saifuddin Auvi
 Type:  New feature  |   Status:  assigned
Component:  contrib.postgres |  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:  1
-+-

Comment (by shauryashahi):

 https://stackoverflow.com/q/62561675/2415394

 Similar question. Posting here for visibility.

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/065.0bdbea6c7d94f20e687f4f72cef546f0%40djangoproject.com.

[Django] #31740: Part 4 of the tutorial incorrectly uses a namespaced url

2020-06-24 Thread Django

#31740: Part 4 of the tutorial incorrectly uses a namespaced url
-+-
   Reporter:  maxi-mil   |  Owner:  nobody
   Type:  Bug| Status:  new
  Component: |Version:  3.0
  Documentation  |   Keywords:  documentation,
   Severity:  Normal |  namespace, error
   Triage Stage: |  Has patch:  0
  Unreviewed |
Needs documentation:  0  |Needs tests:  0
Patch needs improvement:  0  |  Easy pickings:  1
  UI/UX:  0  |
-+-
 I am new to using Django, but I believe I noticed an error with one of the
 urls in a template.

 This url is used in the form:

 {{{
 {% url 'polls:vote' question.id %}
 }}}

 Despite the path definition:

 {{{
 path('/vote/', views.vote, name='vote'),
 }}}

 When I do the same, I get an error as the namespace doesn't exist. This is
 easily fixed by removing the namespace from the template.

 https://docs.djangoproject.com/en/3.0/intro/tutorial04/#write-a-minimal-
 form

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/051.424755ff5c82157ca5e7446d26c5e15d%40djangoproject.com.

Re: [Django] #29617: django.template.Template crashes if the template_string argument is lazy

2020-06-24 Thread Django

#29617: django.template.Template crashes if the template_string argument is lazy
-+-
 Reporter:  Dražen Odobašić  |Owner:  Dražen
 |  Odobašić
 Type:  Bug  |   Status:  closed
Component:  Template system  |  Version:  2.0
 Severity:  Release blocker  |   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
-+-

Comment (by Daniel Miller):

 It appears that as of
 
[https://github.com/django/django/commit/4dadf4eb7bad7c8e9154ff86e7e42ed846c8974d
 this change] it is no longer possible to use `Template` with bytes since
 the input is now coerced to `str`. [https://github.com/dimagi/commcare-
 hq/pull/27911/commits/897b3ff56cdef6179f1d4373f34b15d9d5411fec CommCareHQ
 was using that feature] and ran into the issue while upgrading Django. I
 did not see mention of this backward-incompatible change in the release
 notes.

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/065.a1763bda62e9cdf1e15c0b891281c47f%40djangoproject.com.

Re: [Django] #31737: Strange admin behaviour on Django 3.1b1 with Firefox

2020-06-24 Thread Django

#31737: Strange admin behaviour on Django 3.1b1 with Firefox
-+--
 Reporter:  Claude Paroz |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  contrib.admin|  Version:  3.1
 Severity:  Release blocker  |   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 Claude Paroz):

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


Comment:

 P... you are right, it was most probably a caching issue with using an
 outdated `base.css`.

 So sorry for wasted time :-(

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/065.fbac1dc184494edfa0f3bef9f709e210%40djangoproject.com.

Re: [Django] #31493: Replace var usage with const and let keywords in JavaScript.

2020-06-24 Thread Django

#31493: Replace var usage with const and let keywords in JavaScript.
--+
 Reporter:  Jon Dufresne  |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  closed
Component:  contrib.admin |  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 Carlton Gibson ):

 In [changeset:"af2e95b0fae0437c1cc6c08adfe4ce9c68991a50" af2e95b0]:
 {{{
 #!CommitTicketReference repository=""
 revision="af2e95b0fae0437c1cc6c08adfe4ce9c68991a50"
 [3.0.x] Refs #31493 -- Replaced var with const/let in documentation JS.

 Backport of 2afa61e7d99b2ff2656dc64b6e28db88baf786a4 from master

 Co-authored-by: Carlton Gibson 
 }}}

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/067.a95e3234ed67abbf6ce105bd8ff0d275%40djangoproject.com.

Re: [Django] #31493: Replace var usage with const and let keywords in JavaScript.

2020-06-24 Thread Django

#31493: Replace var usage with const and let keywords in JavaScript.
--+
 Reporter:  Jon Dufresne  |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  closed
Component:  contrib.admin |  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 Carlton Gibson ):

 In [changeset:"6ed4a9bdb3dcb8eb6d6f175947e5fef7827245fc" 6ed4a9b]:
 {{{
 #!CommitTicketReference repository=""
 revision="6ed4a9bdb3dcb8eb6d6f175947e5fef7827245fc"
 [3.1.x] Refs #31493 -- Replaced var with const/let in documentation JS.

 Backport of 2afa61e7d99b2ff2656dc64b6e28db88baf786a4 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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/067.bd6a575a3f89fb80950c9a1e562ac4c6%40djangoproject.com.

Re: [Django] #31493: Replace var usage with const and let keywords in JavaScript.

2020-06-24 Thread Django

#31493: Replace var usage with const and let keywords in JavaScript.
--+
 Reporter:  Jon Dufresne  |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  closed
Component:  contrib.admin |  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 Carlton Gibson ):

 In [changeset:"2afa61e7d99b2ff2656dc64b6e28db88baf786a4" 2afa61e]:
 {{{
 #!CommitTicketReference repository=""
 revision="2afa61e7d99b2ff2656dc64b6e28db88baf786a4"
 Refs #31493 -- Replaced var with const/let in documentation JS.
 }}}

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/067.977c67c5aa18c8f66c24e25d1193aff8%40djangoproject.com.

[Django] #31739: Document RawPostDataException

2020-06-24 Thread Django

#31739: Document RawPostDataException
-+
   Reporter:  Adam (Chainz) Johnson  |  Owner:  nobody
   Type:  Cleanup/optimization   | Status:  new
  Component:  HTTP handling  |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  |
-+
 When accessing HttpRequest.body it's possible that it will raise
 RawPostDataException due to prior use of HttpRequest.read() / readline().
 However there is no documentation covering this exception, nor any
 guidance about solving it. Other exceptions like RequestDataTooBig are
 covered.

 Also the exception message is a little obscure: "You cannot access body
 after reading from request's data stream" . What's the 'data stream' here?

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/053.1e310fb7f564d9fd5cc8ef1f8c1cf36b%40djangoproject.com.

Re: [Django] #31739: Document RawPostDataException

2020-06-24 Thread Django

#31739: Document RawPostDataException
-+-
 Reporter:  Adam (Chainz)|Owner:  nobody
  Johnson|
 Type:   |   Status:  new
  Cleanup/optimization   |
Component:  HTTP handling|  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:
 |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-
Changes (by Adam (Chainz) Johnson):

 * easy:  0 => 1


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

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

Re: [Django] #31523: Remove jQuery dependency from actions.js.

2020-06-24 Thread Django

#31523: Remove jQuery dependency from actions.js.
-+-
 Reporter:  Jon Dufresne |Owner:  Jon
 Type:   |  Dufresne
  Cleanup/optimization   |   Status:  closed
Component:  contrib.admin|  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 Carlton Gibson ):

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


Comment:

 In [changeset:"30e59705fc3e3e9e8370b965af794ad6173bf92b" 30e59705]:
 {{{
 #!CommitTicketReference repository=""
 revision="30e59705fc3e3e9e8370b965af794ad6173bf92b"
 Fixed #31523 -- Removed jQuery dependency from actions.js.
 }}}

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/067.dc97483be6c05334a7a80d3d41cf8708%40djangoproject.com.

Re: [Django] #31529: Add support for pathlib and os.PathLike in migrations serializer.

2020-06-24 Thread Django

#31529: Add support for pathlib and os.PathLike in migrations serializer.
-+-
 Reporter:  Nick Pope|Owner:  Nick Pope
 Type:  New feature  |   Status:  closed
Component:  Migrations   |  Version:  master
 Severity:  Normal   |   Resolution:  fixed
 Keywords:  pathlib migrations   | Triage Stage:  Ready for
  serializer |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Mariusz Felisiak ):

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


Comment:

 In [changeset:"074844e9479a9ee1420685b36189aa2881289993" 074844e9]:
 {{{
 #!CommitTicketReference repository=""
 revision="074844e9479a9ee1420685b36189aa2881289993"
 Fixed #31529 -- Added support for serialization of pathlib.Path/PurePath
 and os.PathLike in 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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/065.8005cd888b79816cd7470bc2bf169dfc%40djangoproject.com.

Re: [Django] #31523: Remove jQuery dependency from actions.js.

2020-06-24 Thread Django

#31523: Remove jQuery dependency from actions.js.
-+-
 Reporter:  Jon Dufresne |Owner:  Jon
 Type:   |  Dufresne
  Cleanup/optimization   |   Status:  assigned
Component:  contrib.admin|  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 Carlton Gibson):

 * stage:  Accepted => Ready for checkin


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

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

Re: [Django] #31529: Add support for pathlib and os.PathLike in migrations serializer.

2020-06-24 Thread Django

#31529: Add support for pathlib and os.PathLike in migrations serializer.
-+-
 Reporter:  Nick Pope|Owner:  Nick Pope
 Type:  New feature  |   Status:  assigned
Component:  Migrations   |  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:  pathlib migrations   | Triage Stage:  Ready for
  serializer |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by felixxm):

 * stage:  Accepted => Ready for checkin


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

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

Re: [Django] #9061: formsets with can_delete=True shouldn't add delete field to extra forms

2020-06-24 Thread Django

#9061: formsets with can_delete=True shouldn't add delete field to extra forms
-+-
 Reporter:  Gabriel Farrell  |Owner:  David
 |  Smith
 Type:  New feature  |   Status:  closed
Component:  Forms|  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 Mariusz Felisiak ):

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


Comment:

 In [changeset:"162765d6c3182e36095d29543e21b44b908625fc" 162765d6]:
 {{{
 #!CommitTicketReference repository=""
 revision="162765d6c3182e36095d29543e21b44b908625fc"
 Fixed #9061 -- Allowed FormSets to disable deleting extra forms.

 Thanks to Dan Ward for the initial patch.
 }}}

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/061.c37e8edd1a5dd02fa0990d8999ba307b%40djangoproject.com.

Re: [Django] #31737: Strange admin behaviour on Django 3.1b1 with Firefox

2020-06-24 Thread Django

Comment (by Carlton Gibson):

Two things going on here.

1. The parent element should have `display: flex`.
2. Browser support.

On 1. This looks to be the case.

[https://github.com/django/django/blob/2e8941b6f90e65ffad3f07083b8de59e8ed29767/django/contrib/admin/static/admin/css/base.css#L748-L751
From base.css]:

{{{
#container > .main {
display: flex;
flex: 1 0 auto;
}
}}}

Disabling that in the inspector causes the issue described.

So where and why exactly is it not being set? (Currently at
`needsinfo`/`worksforme`.)

Then browser support: the intention of
8b30360322d4de6687e17ab267a856db4e3c78a6 for #31032 was precisely to
support only the latest versions. With the current batch of evergreen
browsers, you have to opt-out of being up to date. No doubt it won't last
forever but, we seem to be in a ''belle époque'' from a maintenance
perspective for browser support. I don't think we should willingly
compromise that.

Nonetheless, Firefox ESR isn't that far behind. I think the discussion at
least here should be moot.

If we can answer 1 that would help.

--
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 view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/065.ef363df8d0252d903e80480c501193ca%40djangoproject.com.

Re: [Django] #31735: Migration crash when adding inline foreign key to different schema on PostgreSQL.

2020-06-24 Thread Django

#31735: Migration crash when adding inline foreign key to different schema on
PostgreSQL.
-+-
 Reporter:  Rodrigo Estevao  |Owner:  Simon
 |  Charette
 Type:  Bug  |   Status:  closed
Component:  Migrations   |  Version:  3.0
 Severity:  Release blocker  |   Resolution:  fixed
 Keywords:  many-to- | Triage Stage:  Ready for
  many;relationship;intermediate;table;through|  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Mariusz Felisiak ):

 In [changeset:"453a5bf3024ed385f95f2f9a5378d8fc03baffc2" 453a5bf3]:
 {{{
 #!CommitTicketReference repository=""
 revision="453a5bf3024ed385f95f2f9a5378d8fc03baffc2"
 [3.0.x] Fixed #31735 -- Fixed migrations crash on namespaced inline FK
 addition on PostgreSQL.

 The namespace of the constraint must be included when making the
 constraint immediate.

 Regression in 22ce5d0031bd795ade081394043833e82046016c.

 Thanks Rodrigo Estevao for the report.

 Backport of 2e8941b6f90e65ffad3f07083b8de59e8ed29767 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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/072.a1764b0104b3acd24c8eb696fa8664f4%40djangoproject.com.

Re: [Django] #31735: Migration crash when adding inline foreign key to different schema on PostgreSQL.

2020-06-24 Thread Django

#31735: Migration crash when adding inline foreign key to different schema on
PostgreSQL.
-+-
 Reporter:  Rodrigo Estevao  |Owner:  Simon
 |  Charette
 Type:  Bug  |   Status:  closed
Component:  Migrations   |  Version:  3.0
 Severity:  Release blocker  |   Resolution:  fixed
 Keywords:  many-to- | Triage Stage:  Ready for
  many;relationship;intermediate;table;through|  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Mariusz Felisiak ):

 In [changeset:"b8cb14e8a0d49a1544e3b2d6dbe40ab015bf9a8e" b8cb14e8]:
 {{{
 #!CommitTicketReference repository=""
 revision="b8cb14e8a0d49a1544e3b2d6dbe40ab015bf9a8e"
 [3.1.x] Fixed #31735 -- Fixed migrations crash on namespaced inline FK
 addition on PostgreSQL.

 The namespace of the constraint must be included when making the
 constraint immediate.

 Regression in 22ce5d0031bd795ade081394043833e82046016c.

 Thanks Rodrigo Estevao for the report.

 Backport of 2e8941b6f90e65ffad3f07083b8de59e8ed29767 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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/072.f86ce265237959e9242adf79c3ef3b46%40djangoproject.com.

Re: [Django] #31737: Strange admin behaviour on Django 3.1b1 with Firefox

[Django] #31742: Not working model on 3.1 (lazy reference)

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

Re: [Django] #31741: Admin site applies formfield_overrides for parent field class to instance of a child class

Re: [Django] #31741: Admin site applies formfield_overrides for parent field class to instance of a child class

Re: [Django] #31358: Increase default password salt size in BasePasswordHasher.

[Django] #31741: Admin site applies formfield_overrides for parent field class to instance of a child class

Re: [Django] #31740: Part 4 of the tutorial incorrectly uses a namespaced url

Re: [Django] #29112: Make it easier to update specific keys within nested Django JSONField data.

[Django] #31740: Part 4 of the tutorial incorrectly uses a namespaced url

Re: [Django] #29617: django.template.Template crashes if the template_string argument is lazy

Re: [Django] #31737: Strange admin behaviour on Django 3.1b1 with Firefox

Re: [Django] #31493: Replace var usage with const and let keywords in JavaScript.

Re: [Django] #31493: Replace var usage with const and let keywords in JavaScript.

Re: [Django] #31493: Replace var usage with const and let keywords in JavaScript.

[Django] #31739: Document RawPostDataException

Re: [Django] #31739: Document RawPostDataException

Re: [Django] #31523: Remove jQuery dependency from actions.js.

Re: [Django] #31529: Add support for pathlib and os.PathLike in migrations serializer.

Re: [Django] #31523: Remove jQuery dependency from actions.js.

Re: [Django] #31529: Add support for pathlib and os.PathLike in migrations serializer.

Re: [Django] #9061: formsets with can_delete=True shouldn't add delete field to extra forms

Re: [Django] #31737: Strange admin behaviour on Django 3.1b1 with Firefox

Re: [Django] #31735: Migration crash when adding inline foreign key to different schema on PostgreSQL.

Re: [Django] #31735: Migration crash when adding inline foreign key to different schema on PostgreSQL.

25 matches

Site Navigation

Mail list logo

Footer information