date:20210915

Re: [Django] #33107: ImportError: partially initialized module '...' has no attribute '...'

2021-09-15 Thread Django

#33107: ImportError: partially initialized module '...' has no attribute '...'
-+-
 Reporter:  Collin Anderson  |Owner:  Mariusz
 |  Felisiak
 Type:  Bug  |   Status:  closed
Component:  Utilities|  Version:  4.0
 Severity:  Release blocker  |   Resolution:  fixed
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by GitHub ):

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


Comment:

 In [changeset:"6426c3077c8048bb3fa5bfcec6be80f73476b534" 6426c307]:
 {{{
 #!CommitTicketReference repository=""
 revision="6426c3077c8048bb3fa5bfcec6be80f73476b534"
 Fixed #33107 -- Fixed import_string() crash on not fully initialized
 modules.

 Regression in ecf87ad513fd8af6e4a6093ed918723a7d88d5ca.

 Thanks Collin Anderson for the report.
 }}}

-- 
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.5d8e59e733cdb11ecc469e0acf5dd63c%40djangoproject.com.

Re: [Django] #33111: Conditionally changing ModelAdmin inlines based on object's field breaks when changing object and new inlines should appear. (was: Conditionally changing ModelAdmin inlines based

2021-09-15 Thread Django

#33111: Conditionally changing ModelAdmin inlines based on object's field breaks
when changing object and new inlines should appear.
---+
 Reporter:  joeli  |Owner:  nobody
 Type:  Bug|   Status:  new
Component:  contrib.admin  |  Version:  3.2
 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 Mariusz Felisiak):

 * cc: Hasan Ramezani, WeizhongTu (added)
 * stage:  Unreviewed => Accepted


Comment:

 Thanks for the report. I was able to fix this issue by passing an old
 instance to the `get_inlines()` 樂:
 {{{
 diff --git a/django/contrib/admin/options.py
 b/django/contrib/admin/options.py
 index 1e5fab917e..7b2b893c10 100644
 --- a/django/contrib/admin/options.py
 +++ b/django/contrib/admin/options.py
 @@ -1585,12 +1585,16 @@ class ModelAdmin(BaseModelAdmin):
  )
  if request.method == 'POST':
  form = ModelForm(request.POST, request.FILES, instance=obj)
 +formsets, inline_instances = self._create_formsets(
 +request,
 +form.instance if add else obj,
 +change=not add,
 +)
  form_validated = form.is_valid()
  if form_validated:
  new_object = self.save_form(request, form, change=not
 add)
  else:
  new_object = form.instance
 -formsets, inline_instances = self._create_formsets(request,
 new_object, change=not add)
  if all_valid(formsets) and form_validated:
  self.save_model(request, new_object, form, not add)
  self.save_related(request, form, formsets, not add)
 }}}

-- 
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/064.d802d1f4e07d83b2e4961a1eb6797352%40djangoproject.com.

Re: [Django] #33109: Testing the presence of SameSite and Secure cookies doesn't work

2021-09-15 Thread Django

#33109: Testing the presence of SameSite and Secure cookies doesn't work
-+-
 Reporter:  Adrien Carpentier|Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Testing framework|  Version:  3.1
 Severity:  Normal   |   Resolution:  needsinfo
 Keywords:  cookies, samesite,   | Triage Stage:
  secure, test   |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Mariusz Felisiak):

 * status:  new => closed
 * resolution:   => needsinfo
 * component:  HTTP handling => Testing framework


Comment:

 Thanks for the ticket, however I cannot reproduce this issue. Please
 reopen the ticket if you can debug your issue and provide a sample
 project.

-- 
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/074.5b25e5b0bc428c36b0de76892c7da83a%40djangoproject.com.

Re: [Django] #33112: BaseValidator does not localize params passed to rendered ValidationError

2021-09-15 Thread Django

#33112: BaseValidator does not localize params passed to rendered 
ValidationError
-+-
 Reporter:  JakeUrban|Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Core (Other) |  Version:  3.2
 Severity:  Normal   |   Resolution:
 Keywords:  validators,  | Triage Stage:
  localization, i10n, error, |  Unreviewed
  message|
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  1
-+-
Changes (by JakeUrban):

 * Attachment "Screen Shot 2021-09-15 at 4.42.51 PM.png" added.

 A Portuguese error message containing an english-style number.

-- 
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.adc6e8d33cb1663a7ef8a953c6e8df3f%40djangoproject.com.

[Django] #33112: BaseValidator does not localize params passed to rendered ValidationError

2021-09-15 Thread Django

#33112: BaseValidator does not localize params passed to rendered 
ValidationError
-+-
   Reporter:  JakeUrban  |  Owner:  nobody
   Type:  Bug| Status:  new
  Component:  Core   |Version:  3.2
  (Other)|   Keywords:  validators,
   Severity:  Normal |  localization, i10n, error, message
   Triage Stage: |  Has patch:  0
  Unreviewed |
Needs documentation:  0  |Needs tests:  0
Patch needs improvement:  0  |  Easy pickings:  0
  UI/UX:  1  |
-+-
 django.core.validators.BaseValidator does not localize the values
 contained in the params dict passed to ValidatorError. The result is that
 error messages contain localized error messages with non-localized values.

 Here is a photo of an english-style number included in a Portuguese error
 message:

 [[Image(https://ibb.co/nwNbsjx)]]

-- 
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.181987320ca909179edadb7cd268cb5b%40djangoproject.com.

Re: [Django] #32508: Raise proper exceptions instead of using "assert".

2021-09-15 Thread Django

#32508: Raise proper exceptions instead of using "assert".
-+-
 Reporter:  Adam Johnson |Owner:  Mateo
 Type:   |  Radman
  Cleanup/optimization   |   Status:  closed
Component:  Core (Other) |  Version:  dev
 Severity:  Normal   |   Resolution:  fixed
 Keywords:   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Adam Johnson):

 Thanks all!

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

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

Re: [Django] #33107: ImportError: partially initialized module '...' has no attribute '...'

2021-09-15 Thread Django

#33107: ImportError: partially initialized module '...' has no attribute '...'
-+-
 Reporter:  Collin Anderson  |Owner:  Mariusz
 |  Felisiak
 Type:  Bug  |   Status:  assigned
Component:  Utilities|  Version:  4.0
 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
-+-

Comment (by Collin Anderson):

 By the way, I figured out I can just put `time.sleep(5)` at the top-level
 of my custom auth backend to reproduce the issue the patch does fix the
 issue. Thanks!

-- 
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.a1b1a842cd9c024fa91da4e11def4176%40djangoproject.com.

Re: [Django] #5793: Allow custom attributes in Meta classes

2021-09-15 Thread Django

#5793: Allow custom attributes in Meta classes
-+-
 Reporter:  eikke@…  |Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  Database layer   |  Version:  dev
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by omelched):

 * cc: omelched (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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/073.d8d2df67a1adaaf22a049d7185275a2a%40djangoproject.com.

[Django] #33111: Conditionally changing ModelAdmin inlines based on object's field breaks saving object in admin site when new inlines should appear

2021-09-15 Thread Django

#33111: Conditionally changing ModelAdmin inlines based on object's field breaks
saving object in admin site when new inlines should appear
-+
   Reporter:  joeli  |  Owner:  nobody
   Type:  Bug| Status:  new
  Component:  contrib.admin  |Version:  3.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  |
-+
 Minimal example:

 {{{
 #!python

 # models.py
 class Parent(models.Model):
 show_inlines = models.BooleanField(default=False)

 class Child(models.Model):
 parent = models.ForeignKey(Parent, on_delete=models.CASCADE)


 # admin.py
 class ChildInline(admin.StackedInline):
 model = Child

 @admin.register(Parent)
 class ParentAdmin(admin.ModelAdmin):
 def get_inlines(self, request, obj):
 if obj is not None and obj.show_inlines:
 return [ChildInline]
 return []
 }}}

 - Create `Parent` objects in either initial state and it works as you'd
 expect, where `ChildInline` is rendered when `show_inlines` is True.
 - When `show_inlines` is True, you can also set it to False from the admin
 site, and the `ChildInline` disappears as expected.
 - But when `show_inlines` is False, you cannot re-enable it. Saving the
 object fails due to a validation error in the new `ChildInline` that
 didn't exist before saving:

 {{{
 (Hidden field TOTAL_FORMS) This field is required.
 (Hidden field INITIAL_FORMS) This field is required.
 ManagementForm data is missing or has been tampered with. Missing fields:
 child_set-TOTAL_FORMS, child_set-INITIAL_FORMS. You may need to file a bug
 report if the issue persists.
 }}}

-- 
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/049.6109b94301e84a649527fc9c43222e5d%40djangoproject.com.

Re: [Django] #33100: Add a DateInput widget that provides a date picker via the HTML element

2021-09-15 Thread Django

#33100: Add a DateInput widget that provides a date picker via the HTML  element
-+--
 Reporter:  dvg  |Owner:  nobody
 Type:  New feature  |   Status:  closed
Component:  Forms|  Version:  3.2
 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
-+--

Comment (by dvg):

 Replying to [comment:7 Claude Paroz]:
 > I think it would be interesting to complete the  `DateInput`
 documentation explaining that and giving the small code excerpt given by
 Tim.

 I agree.

 The implementation is indeed trivial, as Tim Graham's example proves.

 However, one cannot implement something that one does not know about.

 Therefore, I think an example in the documentation would be very helpful.

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

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

Re: [Django] #33107: ImportError: partially initialized module '...' has no attribute '...'

2021-09-15 Thread Django

#33107: ImportError: partially initialized module '...' has no attribute '...'
-+-
 Reporter:  Collin Anderson  |Owner:  Mariusz
 |  Felisiak
 Type:  Bug  |   Status:  assigned
Component:  Utilities|  Version:  4.0
 Severity:  Release blocker  |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Mariusz Felisiak):

 * owner:  nobody => Mariusz Felisiak
 * status:  new => assigned
 * has_patch:  0 => 1


Comment:

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

 > Possibly worth noting however is `importlib.util._module_to_load` which
 has equivalent but different (at least in `3.9.5`):

 As far as I'm aware we shouldn't reach `_module_to_load()` using
 `import_module()`. Also Python uses the same strategy (checking
 `__spec__._initialized`) in few places, e.g.
 
[https://github.com/python/cpython/blob/40d2ac92f9a28a486156dafdbb613016bb1f6b98/Python/import.c#L353-L370
 import_ensure_initialized()].

-- 
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.f79a37e609a2c467c9ce270d3780151e%40djangoproject.com.

Re: [Django] #32492: Add django API for Postgres pg_trgm word_similarity, fuzzy full-text search.

2021-09-15 Thread Django

#32492: Add django API for Postgres pg_trgm word_similarity, fuzzy full-text
search.
-+-
 Reporter:  Taneli   |Owner:  Nikita
 |  Marchant
 Type:  New feature  |   Status:  assigned
Component:  contrib.postgres |  Version:  dev
 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 Nikita Marchant):

 * needs_better_patch:  1 => 0
 * needs_docs:  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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/065.77c636757c4861918512b79ddacf183f%40djangoproject.com.

Re: [Django] #33107: ImportError: partially initialized module '...' has no attribute '...'

2021-09-15 Thread Django

#33107: ImportError: partially initialized module '...' has no attribute '...'
-+
 Reporter:  Collin Anderson  |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Utilities|  Version:  4.0
 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
-+

Comment (by Keryn Knight):

 Serendipitous find :) For historical reference, it looks like
 `_initializing`  is set via `importlib._bootstrap._load_unlocked`:
 {{{
 # This must be done before putting the module in sys.modules
 # (otherwise an optimization shortcut in import.c becomes
 # wrong).
 spec._initializing = True
 }}}
 Possibly worth noting however is `importlib.util._module_to_load` which
 has equivalent but different (at least in `3.9.5`):
 {{{
 # This must be done before putting the module in sys.modules
 # (otherwise an optimization shortcut in import.c becomes wrong)
 module.__initializing__ = True
 }}}
 If we're going to try and keep the `cached_import`, perhaps we need to
 accommodate both, or at least investigate the `__initializing__`
 variation?

 FWIW, the investigation/patch proposed above does change the performance
 profile (it's `5.64 µs` for me now) but is still world's better than
 repeatedly doing `import_module` (at least until Python `3.11` which might
 improve things via the linked bpo-43392)

-- 
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.85fe96d7f2323f207847a3d36cf0fcaf%40djangoproject.com.

Re: [Django] #27674: Deprecate GeoModelAdmin and OSMGeoAdmin

2021-09-15 Thread Django

#27674: Deprecate GeoModelAdmin and OSMGeoAdmin
-+-
 Reporter:  Claude Paroz |Owner:  Giannis
 Type:   |  Adamopoulos
  Cleanup/optimization   |   Status:  assigned
Component:  GIS  |  Version:  dev
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Ready for
 |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  1|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Mariusz Felisiak):

 * needs_better_patch:  1 => 0
 * stage:  Accepted => Ready for checkin
 * needs_docs:  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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/065.57dcac1eadd6b65a0e1f732240ee55c6%40djangoproject.com.

Re: [Django] #33110: django.contrib.admin.templates base.html load i18n two times

2021-09-15 Thread Django

#33110: django.contrib.admin.templates base.html  load i18n two times
-+-
 Reporter:  Maxim Danilov|Owner:  nobody
 Type:   |   Status:  closed
  Cleanup/optimization   |
Component:  contrib.admin|  Version:  3.2
 Severity:  Normal   |   Resolution:  duplicate
 Keywords:  admin, modeladmin| Triage Stage:
 |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-
Changes (by Keryn Knight):

 * cc: Keryn Knight (added)
 * status:  new => closed
 * resolution:   => duplicate


Comment:

 Thanks for the report, this is a duplicate of #32385 I believe.

-- 
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.7ca0b7bf118c997d8daecd01222666e1%40djangoproject.com.

Re: [Django] #27624: Optimize ORM by using more immutable data structures

2021-09-15 Thread Django

* cc: Keryn Knight (added)

Comment:

Can I ask that we consider not closing it? I've only just been made aware
of this ticket (... Trac search being what it is), and it turns out it
discusses hoisting immutables to class level attributes for an
improvement, which is a branch I have recently been working on, with the
intent to fully bench (well, y'know, at least timeit/cprofile) each part
and subsequently submit a ticket/PR for discussion. If I can get around to
rebasing and re-testing, that change could potentially still land as part
of this ticket, some time after 4.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 view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/068.0d8ba9beecd8c8a774baa8cee149af8b%40djangoproject.com.

Re: [Django] #33110: django.contrib.admin.templates base.html load i18n two times (was: django contrib admin templates base.htm has two time load i18n)

2021-09-15 Thread Django

#33110: django.contrib.admin.templates base.html  load i18n two times
-+-
 Reporter:  Maxim Danilov|Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |
Component:  contrib.admin|  Version:  3.2
 Severity:  Normal   |   Resolution:
 Keywords:  admin, modeladmin| Triage Stage:
 |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/067.74990c89ee43ced5d678466df1d4d7e0%40djangoproject.com.

[Django] #33110: django contrib admin templates base.htm has two time load i18n

2021-09-15 Thread Django

#33110: django contrib admin templates base.htm has two time load i18n
-+-
   Reporter:  Maxim  |  Owner:  nobody
  Danilov|
   Type: | Status:  new
  Cleanup/optimization   |
  Component: |Version:  3.2
  contrib.admin  |
   Severity:  Normal |   Keywords:  admin, modeladmin
   Triage Stage: |  Has patch:  0
  Unreviewed |
Needs documentation:  0  |Needs tests:  0
Patch needs improvement:  0  |  Easy pickings:  1
  UI/UX:  0  |
-+-
 1 line {% load i18n static %}
 21 line {% load i18n %}

 why we need it?

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

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

Re: [Django] #16493: Windows: makemessages generate django.po should use forward slashes too

2021-09-15 Thread Django

#16493: Windows:  makemessages generate django.po should use forward slashes too
-+-
 Reporter:  raidsan@…|Owner:  nobody
 Type:  New feature  |   Status:  closed
Component:  Core (Management |  Version:  1.3
  commands)  |
 Severity:  Normal   |   Resolution:  needsinfo
 Keywords:   | Triage Stage:
 |  Unreviewed
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-

Comment (by John Vandenberg):

 This makes it difficult for Unix and Windows developers to be working on
 the same project.  The .po file will switch back and forth each time.  The
 file in the comment is useful information, so using `--no-location` is not
 a great solution.

-- 
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/075.2b124b94adc02eaac88fe809bb52411f%40djangoproject.com.

Re: [Django] #33029: Can't open multiple Django Admin Popups for the same related field.

2021-09-15 Thread Django

#33029: Can't open multiple Django Admin Popups for the same related field.
-+-
 Reporter:  Yash Jhunjhunwala|Owner:  Yash
 |  Jhunjhunwala
 Type:  New feature  |   Status:  assigned
Component:  contrib.admin|  Version:  3.2
 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:  1
-+-
Changes (by Yash Jhunjhunwala):

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

Re: [Django] #33107: ImportError: partially initialized module '...' has no attribute '...'

Re: [Django] #33111: Conditionally changing ModelAdmin inlines based on object's field breaks when changing object and new inlines should appear. (was: Conditionally changing ModelAdmin inlines based

Re: [Django] #33109: Testing the presence of SameSite and Secure cookies doesn't work

Re: [Django] #33112: BaseValidator does not localize params passed to rendered ValidationError

[Django] #33112: BaseValidator does not localize params passed to rendered ValidationError

Re: [Django] #32508: Raise proper exceptions instead of using "assert".

Re: [Django] #33107: ImportError: partially initialized module '...' has no attribute '...'

Re: [Django] #5793: Allow custom attributes in Meta classes

[Django] #33111: Conditionally changing ModelAdmin inlines based on object's field breaks saving object in admin site when new inlines should appear

Re: [Django] #33100: Add a DateInput widget that provides a date picker via the HTML element

Re: [Django] #33107: ImportError: partially initialized module '...' has no attribute '...'

Re: [Django] #32492: Add django API for Postgres pg_trgm word_similarity, fuzzy full-text search.

Re: [Django] #33107: ImportError: partially initialized module '...' has no attribute '...'

Re: [Django] #27674: Deprecate GeoModelAdmin and OSMGeoAdmin

Re: [Django] #33110: django.contrib.admin.templates base.html load i18n two times

Re: [Django] #27624: Optimize ORM by using more immutable data structures

Re: [Django] #33110: django.contrib.admin.templates base.html load i18n two times (was: django contrib admin templates base.htm has two time load i18n)

[Django] #33110: django contrib admin templates base.htm has two time load i18n

Re: [Django] #16493: Windows: makemessages generate django.po should use forward slashes too

Re: [Django] #33029: Can't open multiple Django Admin Popups for the same related field.

20 matches

Site Navigation

Mail list logo

Footer information