Re: [Django] #32813: Display development server address after server bind

2023-02-09 Thread Django 
#32813: Display development server address after server bind
-+-
 Reporter:  fmwviormv|Owner:  Dhanush
 Type:  Bug  |   Status:  assigned
Component:  Core (Management |  Version:  dev
  commands)  |
 Severity:  Normal   |   Resolution:
 Keywords:  development server,  | Triage Stage:  Ready for
  automatic port |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Mariusz Felisiak):

 * 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/010701863a3bbb82-eccc8bae-e9f0-4d32-aed5-e6b8b4e319ac-00%40eu-central-1.amazonses.com.

Re: [Django] #34329: django-formset new app - i am facing the issue Uncaught (in promise) SyntaxError: JSON.parse (was: django-formset new app - i am facing the issue Uncaught (in promise) SyntaxError

2023-02-09 Thread Django 
#34329: django-formset new app - i am facing the issue Uncaught (in promise)
SyntaxError: JSON.parse
-+--
 Reporter:  Sasikumar K  |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Forms|  Version:  4.1
 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 Mariusz Felisiak):

 * status:  new => closed
 * needs_docs:  1 => 0
 * resolution:   => invalid


Old description:

> I am new to django . while i am trying to use django-formset third party
> app in my form modelchoice control change event  show the error -
> Uncaught (in promise) SyntaxError: JSON.parse: unexpected character at
> line 1 column 1 of the JSON data - i have spent 6 hours i could not fix
> the error.
>

>

> form.py
>
> class OfficedetForm(forms.ModelForm):
>
> office_logo = fields.FileField(
> label="Office Logo",
> widget=UploadedFileInput,
> required=True,
> )
>
> office_gender_type = forms.ModelChoiceField(
> queryset=OFFICE_GENDER_TYPE_CHOICE.objects.all(),
> widget=Selectize(
>
> placeholder="Choose Gender",
> ),
> )
>
> office_mgnt_type = forms.ModelChoiceField(
> queryset=OFFICE_MGNT_TYPE_CHOICE.objects.all(),
> widget=Selectize(
>
> placeholder="Choose Management",
> ),
> )
>
> office_class_level = forms.ModelChoiceField(
> queryset=OfficeClassLevel.objects.all(),
> widget=Selectize(
>
> placeholder="Choose Class Level",
> ),
> )
>
> office_place = forms.ModelChoiceField(
> queryset=Places.objects.all(),
> widget=Selectize(
> search_lookup='placename__icontains',
> placeholder="Choose Place",
>
> ),
> )
>
> office_type = forms.ChoiceField(
> choices=[ ('SCHOOL','SCHOOL'),
> ('ADMIN','ADMIN'),],
> widget=Selectize,
> )
>

> default_renderer = FormRenderer(
> form_css_classes='row',
> field_css_classes={
> '*': 'mb-2 col-12',
> "office_code": 'mb-2 col-2',
> "office_name": 'mb-2 col-4',
> "office_mail": 'mb-2 col-3',
> "office_place": 'mb-2 col-3',
>  '*': 'mb-2 col-12',
> "office_gender_type": 'mb-2 col-3',
> "office_mgnt_type": 'mb-2 col-3',
> "office_class_level": 'mb-2 col-3',
> "office_type": 'mb-2 col-3',
>
>  '*': 'mb-2 col-12',
> "office_tanno": 'mb-2 col-4',
> "office_udisecode": 'mb-2 col-4',
> "office_logo": 'mb-2 col-4',
>

> }
> )
> class Meta:
> model = Officedet
> fields = ["office_code",
> "office_name",
> "office_mail",
> "office_place",
> "office_gender_type",
> "office_mgnt_type",
> "office_class_level",
> "office_type",
> 'office_tanno',
> 'office_udisecode',
> "office_logo",
> ]
>

> views.py
>

> class OfficeDetailCreateView(AdminUserTypeAuthMixin,FileUploadMixin,
> FormViewMixin, LoginRequiredMixin, CreateView):
> model = Officedet
> template_name = 'home/crud/crud_template.html'
> form_class = OfficedetForm
> success_url = reverse_lazy('office_list_view')  # or whatever makes
> sense
> extra_context = {
> 'pagetitle':'Office Creation'
> }
>
> page.html
>
> {% extends "layouts/masterpage-formset.html" %}
> {% block pagecontent %}
> {% load render_form from formsetify %}
> 
>   {% render_form form %}
>

>   
> Submit class="ms-2 dj-button-decorator">
> Reset
> Back to list
>
> 
> 
> {% endblock pagecontent %}

New description:

 I am new to django . while i am trying to use django-formset third party
 app in my form modelchoice control change event  show the error -
 Uncaught (in promise) SyntaxError: JSON.parse: unexpected character at
 line 1 column 1 of the JSON data - i have spent 6 hours i could not fix
 the error.

 {{{
 form.py

 class OfficedetForm(forms.ModelForm):

 office_logo = fields.FileField(
 label="Office Logo",
 widget=UploadedFileInput,
 required=True,
 )

 office_gender_type = forms.ModelChoiceField(
 queryset=OFFICE_GENDER_TYPE_CHOICE.objects.all(),
 widget=Selectize(

 placeholder="Choose Gender",
 ),
 )

 office_mgnt_type = forms.ModelChoiceField(
 queryset=OFFICE_MGNT_TYPE_CHOICE.objects.all(),
 widget=Selectize(

 placeholder="Choose Management",
 ),
 )

Re: [Django] #34329: django-formset new app - i am facing the issue Uncaught (in promise) SyntaxError: JSON.parse: unexpected character at line 1 column 1 of the JSON data

2023-02-09 Thread Django 
#34329: django-formset new app - i am facing the issue Uncaught (in promise)
SyntaxError: JSON.parse: unexpected character at line 1 column 1 of the
JSON data
-+--
 Reporter:  Sasikumar K  |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Forms|  Version:  4.1
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Unreviewed
Has patch:  0|  Needs documentation:  1
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+--
Description changed by Sasikumar K:

Old description:

> I am new to django . while i am trying to use django-formset third party
> app in my form modelchoice control change event  show the error -
> Uncaught (in promise) SyntaxError: JSON.parse: unexpected character at
> line 1 column 1 of the JSON data - i have spent 6 hours i could not fix
> the error.

New description:

 I am new to django . while i am trying to use django-formset third party
 app in my form modelchoice control change event  show the error -
 Uncaught (in promise) SyntaxError: JSON.parse: unexpected character at
 line 1 column 1 of the JSON data - i have spent 6 hours i could not fix
 the error.




 form.py

 class OfficedetForm(forms.ModelForm):

 office_logo = fields.FileField(
 label="Office Logo",
 widget=UploadedFileInput,
 required=True,
 )

 office_gender_type = forms.ModelChoiceField(
 queryset=OFFICE_GENDER_TYPE_CHOICE.objects.all(),
 widget=Selectize(

 placeholder="Choose Gender",
 ),
 )

 office_mgnt_type = forms.ModelChoiceField(
 queryset=OFFICE_MGNT_TYPE_CHOICE.objects.all(),
 widget=Selectize(

 placeholder="Choose Management",
 ),
 )

 office_class_level = forms.ModelChoiceField(
 queryset=OfficeClassLevel.objects.all(),
 widget=Selectize(

 placeholder="Choose Class Level",
 ),
 )

 office_place = forms.ModelChoiceField(
 queryset=Places.objects.all(),
 widget=Selectize(
 search_lookup='placename__icontains',
 placeholder="Choose Place",

 ),
 )

 office_type = forms.ChoiceField(
 choices=[ ('SCHOOL','SCHOOL'),
 ('ADMIN','ADMIN'),],
 widget=Selectize,
 )


 default_renderer = FormRenderer(
 form_css_classes='row',
 field_css_classes={
 '*': 'mb-2 col-12',
 "office_code": 'mb-2 col-2',
 "office_name": 'mb-2 col-4',
 "office_mail": 'mb-2 col-3',
 "office_place": 'mb-2 col-3',
  '*': 'mb-2 col-12',
 "office_gender_type": 'mb-2 col-3',
 "office_mgnt_type": 'mb-2 col-3',
 "office_class_level": 'mb-2 col-3',
 "office_type": 'mb-2 col-3',

  '*': 'mb-2 col-12',
 "office_tanno": 'mb-2 col-4',
 "office_udisecode": 'mb-2 col-4',
 "office_logo": 'mb-2 col-4',


 }
 )
 class Meta:
 model = Officedet
 fields = ["office_code",
 "office_name",
 "office_mail",
 "office_place",
 "office_gender_type",
 "office_mgnt_type",
 "office_class_level",
 "office_type",
 'office_tanno',
 'office_udisecode',
 "office_logo",
 ]


 views.py


 class OfficeDetailCreateView(AdminUserTypeAuthMixin,FileUploadMixin,
 FormViewMixin, LoginRequiredMixin, CreateView):
 model = Officedet
 template_name = 'home/crud/crud_template.html'
 form_class = OfficedetForm
 success_url = reverse_lazy('office_list_view')  # or whatever makes
 sense
 extra_context = {
 'pagetitle':'Office Creation'
 }

 page.html

 {% extends "layouts/masterpage-formset.html" %}
 {% block pagecontent %}
 {% load render_form from formsetify %}
 
   {% render_form form %}


   
 Submit
 Reset
 Back to list

 
 
 {% endblock pagecontent %}

--

-- 
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/010701863a2e8f9e-1b90a404-5ea8-4662-8fa4-728905104f4d-00%40eu-central-1.amazonses.com.

Re: [Django] #34329: django-formset new app - i am facing the issue Uncaught (in promise) SyntaxError: JSON.parse: unexpected character at line 1 column 1 of the JSON data

2023-02-09 Thread Django 
#34329: django-formset new app - i am facing the issue Uncaught (in promise)
SyntaxError: JSON.parse: unexpected character at line 1 column 1 of the
JSON data
-+--
 Reporter:  Sasikumar K  |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Forms|  Version:  4.1
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Unreviewed
Has patch:  0|  Needs documentation:  1
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+--
Changes (by Sasikumar K):

 * needs_docs:  0 => 1


Old description:

> I am new to django . while i am trying to use django-formset third party
> app in my form modelchoice control change event  show the error -
> Uncaught (in promise) SyntaxError: JSON.parse: unexpected character at
> line 1 column 1 of the JSON data - i have spent 6 hours i could not fix
> the error.

New description:

 I am new to django . while i am trying to use django-formset third party
 app in my form modelchoice control change event  show the error -
 Uncaught (in promise) SyntaxError: JSON.parse: unexpected character at
 line 1 column 1 of the JSON data - i have spent 6 hours i could not fix
 the error.

--

Comment:

 form.py

 class OfficedetForm(forms.ModelForm):

 office_logo = fields.FileField(
 label="Office Logo",
 widget=UploadedFileInput,
 required=True,
 )

 office_gender_type = forms.ModelChoiceField(
 queryset=OFFICE_GENDER_TYPE_CHOICE.objects.all(),
 widget=Selectize(

 placeholder="Choose Gender",
 ),
 )

 office_mgnt_type = forms.ModelChoiceField(
 queryset=OFFICE_MGNT_TYPE_CHOICE.objects.all(),
 widget=Selectize(

 placeholder="Choose Management",
 ),
 )

 office_class_level = forms.ModelChoiceField(
 queryset=OfficeClassLevel.objects.all(),
 widget=Selectize(

 placeholder="Choose Class Level",
 ),
 )

 office_place = forms.ModelChoiceField(
 queryset=Places.objects.all(),
 widget=Selectize(
 search_lookup='placename__icontains',
 placeholder="Choose Place",

 ),
 )

 office_type = forms.ChoiceField(
 choices=[ ('SCHOOL','SCHOOL'),
 ('ADMIN','ADMIN'),],
 widget=Selectize,
 )


 default_renderer = FormRenderer(
 form_css_classes='row',
 field_css_classes={
 '*': 'mb-2 col-12',
 "office_code": 'mb-2 col-2',
 "office_name": 'mb-2 col-4',
 "office_mail": 'mb-2 col-3',
 "office_place": 'mb-2 col-3',
  '*': 'mb-2 col-12',
 "office_gender_type": 'mb-2 col-3',
 "office_mgnt_type": 'mb-2 col-3',
 "office_class_level": 'mb-2 col-3',
 "office_type": 'mb-2 col-3',

  '*': 'mb-2 col-12',
 "office_tanno": 'mb-2 col-4',
 "office_udisecode": 'mb-2 col-4',
 "office_logo": 'mb-2 col-4',


 }
 )
 class Meta:
 model = Officedet
 fields = ["office_code",
 "office_name",
 "office_mail",
 "office_place",
 "office_gender_type",
 "office_mgnt_type",
 "office_class_level",
 "office_type",
 'office_tanno',
 'office_udisecode',
 "office_logo",
 ]


 views.py


 class OfficeDetailCreateView(AdminUserTypeAuthMixin,FileUploadMixin,
 FormViewMixin, LoginRequiredMixin, CreateView):
 model = Officedet
 template_name = 'home/crud/crud_template.html'
 form_class = OfficedetForm
 success_url = reverse_lazy('office_list_view')  # or whatever makes
 sense
 extra_context = {
 'pagetitle':'Office Creation'
 }

 page.html

 {% extends "layouts/masterpage-formset.html" %}
 {% block pagecontent %}
 {% load render_form from formsetify %}
 
   {% render_form form %}


   
 Submit
 Reset
 Back to list

 
 
 {% endblock pagecontent %}

-- 
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/010701863a2c9d13-3fa4b941-68a8-4a8d-b7eb-3b0fadcc0671-00%40eu-central-1.amazonses.com.

Re: [Django] #34329: django-formset new app - i am facing the issue Uncaught (in promise) SyntaxError: JSON.parse: unexpected character at line 1 column 1 of the JSON data

2023-02-09 Thread Django 
#34329: django-formset new app - i am facing the issue Uncaught (in promise)
SyntaxError: JSON.parse: unexpected character at line 1 column 1 of the
JSON data
-+--
 Reporter:  Sasikumar K  |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Forms|  Version:  4.1
 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 Sasikumar K):

 * Attachment "error1.png" 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/010701863a2ac927-7c3b5d66-c85e-49b2-973a-bf38f5f8aae6-00%40eu-central-1.amazonses.com.

[Django] #34329: django-formset new app - i am facing the issue Uncaught (in promise) SyntaxError: JSON.parse: unexpected character at line 1 column 1 of the JSON data

2023-02-09 Thread Django 
#34329: django-formset new app - i am facing the issue Uncaught (in promise)
SyntaxError: JSON.parse: unexpected character at line 1 column 1 of the
JSON data
--+
   Reporter:  sasikumar1978k  |  Owner:  nobody
   Type:  Bug | Status:  new
  Component:  Forms   |Version:  4.1
   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   |
--+
 I am new to django . while i am trying to use django-formset third party
 app in my form modelchoice control change event  show the error -
 Uncaught (in promise) SyntaxError: JSON.parse: unexpected character at
 line 1 column 1 of the JSON data - i have spent 6 hours i could not fix
 the error.

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/010701863a2804e6-be1a5c76-ef33-45d1-aa5a-2a3fbd269bd9-00%40eu-central-1.amazonses.com.

Re: [Django] #34324: Django Discord Server is not mentioned in the "Join the Django community ❤️" section in contributing guide

2023-02-09 Thread Django 
#34324: Django Discord Server is not mentioned in the "Join the Django community
❤️" section in contributing guide
-+-
 Reporter:  Vibhakar Solanki |Owner:  Vibhakar
 Type:   |  Solanki
  Cleanup/optimization   |   Status:  closed
Component:  Documentation|  Version:  dev
 Severity:  Normal   |   Resolution:  fixed
 Keywords:   | Triage Stage:  Ready for
 |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-

Comment (by Mariusz Felisiak ):

 In [changeset:"aaacf72c4c5602aa63e102c262617b8de427901b" aaacf72c]:
 {{{
 #!CommitTicketReference repository=""
 revision="aaacf72c4c5602aa63e102c262617b8de427901b"
 [4.2.x] Fixed #34324 -- Mentioned Discord server in contributing index.

 Backport of 358792486e3afd83250364ebc15060820a8a96cc from main
 }}}

-- 
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/0107018639c66784-530ec355-60d5-4818-b5ea-45771548784e-00%40eu-central-1.amazonses.com.

Re: [Django] #34324: Django Discord Server is not mentioned in the "Join the Django community ❤️" section in contributing guide

2023-02-09 Thread Django 
#34324: Django Discord Server is not mentioned in the "Join the Django community
❤️" section in contributing guide
-+-
 Reporter:  Vibhakar Solanki |Owner:  Vibhakar
 Type:   |  Solanki
  Cleanup/optimization   |   Status:  closed
Component:  Documentation|  Version:  dev
 Severity:  Normal   |   Resolution:  fixed
 Keywords:   | Triage Stage:  Ready for
 |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-
Changes (by Mariusz Felisiak ):

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


Comment:

 In [changeset:"358792486e3afd83250364ebc15060820a8a96cc" 35879248]:
 {{{
 #!CommitTicketReference repository=""
 revision="358792486e3afd83250364ebc15060820a8a96cc"
 Fixed #34324 -- Mentioned Discord server in contributing index.
 }}}

-- 
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/0107018639c63def-1081c6a9-73dc-4e63-949c-d630e3f954c9-00%40eu-central-1.amazonses.com.

Re: [Django] #32813: Display development server address after server bind

2023-02-09 Thread Django 
#32813: Display development server address after server bind
-+-
 Reporter:  fmwviormv|Owner:  Dhanush
 Type:  Bug  |   Status:  assigned
Component:  Core (Management |  Version:  dev
  commands)  |
 Severity:  Normal   |   Resolution:
 Keywords:  development server,  | Triage Stage:  Accepted
  automatic port |
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Mariusz Felisiak):

 * 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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/0107018639b51db5-2581c018-4d59-49fd-9706-4b43f2232c25-00%40eu-central-1.amazonses.com.

Re: [Django] #34324: Django Discord Server is not mentioned in the "Join the Django community ❤️" section in contributing guide

2023-02-09 Thread Django 
#34324: Django Discord Server is not mentioned in the "Join the Django community
❤️" section in contributing guide
-+-
 Reporter:  Vibhakar Solanki |Owner:  Vibhakar
 Type:   |  Solanki
  Cleanup/optimization   |   Status:  assigned
Component:  Documentation|  Version:  dev
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Ready for
 |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-
Changes (by Mariusz Felisiak):

 * 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/0107018639af4b39-dfa667e3-eb6b-4ee1-a7b9-c8f177d6b7ac-00%40eu-central-1.amazonses.com.

Re: [Django] #34039: Admin search bar is too small to use on small screens

2023-02-09 Thread Django 
#34039: Admin search bar is too small to use on small screens
-+-
 Reporter:  Thibaud Colas|Owner:  Mia Bajić
 Type:  Bug  |   Status:  assigned
Component:  contrib.admin|  Version:  4.0
 Severity:  Normal   |   Resolution:
 Keywords:  mobile, cross-   | Triage Stage:  Accepted
  browser|
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  1|UI/UX:  1
-+-

Comment (by Syed Sajjad Hussain Shah):

 Hi, how can i reproduce this isse?

-- 
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/0107018638e40214-231636f5-cdf9-4b12-bddb-6c993f85071f-00%40eu-central-1.amazonses.com.

Re: [Django] #30386: Admin foreign key widgets don't quote keys.

2023-02-09 Thread Django 
#30386: Admin foreign key widgets don't quote keys.
-+-
 Reporter:  Joshua Goodwin   |Owner:
 |  Oluwayemisi Ismail
 Type:  Bug  |   Status:  assigned
Component:  contrib.admin|  Version:  dev
 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 Oluwayhemisi):

 * owner:  (none) => Oluwayemisi Ismail
 * 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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/01070186381006ec-3e5c9db9-6ce0-4588-83d2-9d04748be0c4-00%40eu-central-1.amazonses.com.

Re: [Django] #34326: Standardize case for commands

2023-02-09 Thread Django 
#34326: Standardize case for commands
-+-
 Reporter:  Shiva Shane Ramdeen  |Owner:  nobody
 Type:   |   Status:  closed
  Cleanup/optimization   |
Component:  Core (Management |  Version:  dev
  commands)  |
 Severity:  Normal   |   Resolution:  invalid
 Keywords:  Commands, Command| Triage Stage:
  Case   |  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:   => invalid


Comment:

 `django-extensions` is a 3rd-party package. Please report it on their
 [https://github.com/django-extensions/django-extensions/issues issue
 tracker].

-- 
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/0107018637c181bd-54061cc6-6dc6-41a7-bc2e-e8bab99ba74e-00%40eu-central-1.amazonses.com.

Re: [Django] #34326: Standardize case for commands

2023-02-09 Thread Django 
#34326: Standardize case for commands
-+-
 Reporter:  Shiva Shane Ramdeen  |Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |
Component:  Core (Management |  Version:  dev
  commands)  |
 Severity:  Normal   |   Resolution:
 Keywords:  Commands, Command| Triage Stage:
  Case   |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Shiva Shane Ramdeen):

 Core commands are not an issue. they are pretty consistent for the most
 part. The issue really is with djang_extensions. Each project is
 consistent with either snake_case or flatcase but inter inter app commands
 feel inconsistent.

 maybe it might be a good idea to investigate this type of change in the
 django_extensions repo instead, not sure.


 Replying to [comment:1 Tim Graham]:
 > It looks like there are two built-in commands that use underscores
 (snake case): `remove_stale_contenttypes` and `ping_google`. I never
 noticed the inconsistency, and I doubt it causes much confusion. Are you
 really struggling with it? Perhaps commands in third-party packages are
 affected?

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/0107018637bcfb2f-14060ecb-3e68-4e33-9a83-fefacb2c1864-00%40eu-central-1.amazonses.com.

Re: [Django] #34324: Django Discord Server is not mentioned in the "Join the Django community ❤️" section in contributing guide

2023-02-09 Thread Django 
#34324: Django Discord Server is not mentioned in the "Join the Django community
❤️" section in contributing guide
-+-
 Reporter:  Vibhakar Solanki |Owner:  Vibhakar
 Type:   |  Solanki
  Cleanup/optimization   |   Status:  assigned
Component:  Documentation|  Version:  dev
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-
Changes (by Mariusz Felisiak):

 * stage:  Ready for checkin => Accepted


Comment:

 Vibhakar, you [https://docs.djangoproject.com/en/4.1/faq/contributing/#i-m
 -sure-my-ticket-is-absolutely-100-perfect-can-i-mark-it-as-ready-for-
 checkin-myself shouldn't] mark your own patches as "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/0107018637ba235c-bbbc78b7-d21e-4c4b-be54-a6ac5d8271b9-00%40eu-central-1.amazonses.com.

Re: [Django] #34248: sdist is missing tox.ini

2023-02-09 Thread Django 
#34248: sdist is missing tox.ini
-+-
 Reporter:  Marcel Telka |Owner:  Syed
 Type:   |  Sajjad Hussain Shah
  Cleanup/optimization   |   Status:  closed
Component:  Packaging|  Version:  4.1
 Severity:  Normal   |   Resolution:  fixed
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-
Changes (by GitHub ):

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


Comment:

 In [changeset:"3fa83906739e95fe5fd8eb3661234ba43247f74d" 3fa8390]:
 {{{
 #!CommitTicketReference repository=""
 revision="3fa83906739e95fe5fd8eb3661234ba43247f74d"
 Fixed #34248 -- Added tox.ini to MANIFEST.in.

 Co-authored-by: Syed Sajjad  Hussain Shah 
 }}}

-- 
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/0107018637b8bc21-eb7b821f-6087-4312-bc22-158e67a4a896-00%40eu-central-1.amazonses.com.

Re: [Django] #34324: Django Discord Server is not mentioned in the "Join the Django community ❤️" section in contributing guide

2023-02-09 Thread Django 
#34324: Django Discord Server is not mentioned in the "Join the Django community
❤️" section in contributing guide
-+-
 Reporter:  Vibhakar Solanki |Owner:  Vibhakar
 Type:   |  Solanki
  Cleanup/optimization   |   Status:  assigned
Component:  Documentation|  Version:  dev
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Ready for
 |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-
Changes (by Vibhakar Solanki):

 * 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/0107018637a95d5f-0bdf1dbb-230a-40bd-9b5f-ded1991a12e8-00%40eu-central-1.amazonses.com.

Re: [Django] #34325: Clarify PercentRank() description. (was: PercentRank confusion)

2023-02-09 Thread Django 
#34325: Clarify PercentRank() description.
--+
 Reporter:  dvg   |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  Documentation |  Version:  4.1
 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):

 * type:  Uncategorized => Cleanup/optimization
 * stage:  Unreviewed => Accepted


Comment:

 Agreed, "relative rank" is less confusing. Would you like to prepare a
 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/0107018637a66a82-f92fe512-0f49-41e9-b479-5887756d2674-00%40eu-central-1.amazonses.com.

Re: [Django] #34324: Django Discord Server is not mentioned in the "Join the Django community ❤️" section in contributing guide

2023-02-09 Thread Django 
#34324: Django Discord Server is not mentioned in the "Join the Django community
❤️" section in contributing guide
-+-
 Reporter:  Vibhakar Solanki |Owner:  Vibhakar
 Type:   |  Solanki
  Cleanup/optimization   |   Status:  assigned
Component:  Documentation|  Version:  dev
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-
Changes (by Vibhakar Solanki):

 * has_patch:  0 => 1


Comment:

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

-- 
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/0107018637a11c95-aedd38fd-63c3-47f7-8d79-4f0082a6203a-00%40eu-central-1.amazonses.com.

Re: [Django] #33586: Cannot delete object (A) referenced by another object (B) if said object (A) has a foreign key to a custom user.

2023-02-09 Thread Django 
#33586: Cannot delete object (A) referenced by another object (B) if said object
(A) has a foreign key to a custom user.
---+
 Reporter:  Jeremy Poulin  |Owner:  (none)
 Type:  Bug|   Status:  new
Component:  Migrations |  Version:  4.0
 Severity:  Normal |   Resolution:
 Keywords: | Triage Stage:  Accepted
Has patch:  1  |  Needs documentation:  0
  Needs tests:  1  |  Patch needs improvement:  1
Easy pickings:  0  |UI/UX:  0
---+

Comment (by Mariusz Felisiak):

 > Is this issue fixed?

 No.

-- 
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/01070186379d03e6-81784b46-ecd5-4e01-b290-d02420b0f40a-00%40eu-central-1.amazonses.com.

Re: [Django] #33586: Cannot delete object (A) referenced by another object (B) if said object (A) has a foreign key to a custom user.

2023-02-09 Thread Django 
#33586: Cannot delete object (A) referenced by another object (B) if said object
(A) has a foreign key to a custom user.
---+
 Reporter:  Jeremy Poulin  |Owner:  (none)
 Type:  Bug|   Status:  new
Component:  Migrations |  Version:  4.0
 Severity:  Normal |   Resolution:
 Keywords: | Triage Stage:  Accepted
Has patch:  1  |  Needs documentation:  0
  Needs tests:  1  |  Patch needs improvement:  1
Easy pickings:  0  |UI/UX:  0
---+

Comment (by madhuri2):

 Is this issue fixed?
 I was working on this issue and I found this error **ValueError: Cannot
 query "A object(1)": Must be "A" instance.
 **
 Then I tried this
 I removed the migrations file.
 Then applied migrations.
 Unapplied all migrations using: ''python manage.py migrate rmigrate zero''
 and it worked!

 {{{
 (venv) PS C:\Users\Madhu\Desktop\Django\ticket33586\rmigration_bug> python
 manage.py makemigrations
 ←[36;1mMigrations for 'rmigrate':←[0m
   ←[1mrmigrate\migrations\0001_initial.py←[0m
 - Create model User
 - Create model A
 - Create model B


 (venv) PS C:\Users\Madhu\Desktop\Django\ticket33586\rmigration_bug> python
 manage.py migrate
 ←[36;1mOperations to perform:←[0m
 ←[1m  Apply all migrations: ←[0madmin, auth, contenttypes, rmigrate,
 sessions
 ←[36;1mRunning migrations:←[0m
   No migrations to apply.


 (venv) PS C:\Users\Madhu\Desktop\Django\ticket33586\rmigration_bug> python
 manage.py migrate rmigrate zero
 ←[36;1mOperations to perform:←[0m
 ←[1m  Unapply all migrations: ←[0mrmigrate
 ←[36;1mRunning migrations:←[0m
   Rendering model states...←[32;1m DONE←[0m
   Unapplying admin.0003_logentry_add_action_flag_choices...←[32;1m OK←[0m
   Unapplying admin.0002_logentry_remove_auto_add...←[32;1m OK←[0m
   Unapplying admin.0001_initial...←[32;1m OK←[0m
   Unapplying rmigrate.0001_initial...←[32;1m OK←[0m



 (venv) PS C:\Users\Madhu\Desktop\Django\ticket33586\rmigration_bug> python
 manage.py migrate
 ←[36;1mOperations to perform:←[0m
 ←[1m  Apply all migrations: ←[0madmin, auth, contenttypes, rmigrate,
 sessions
 ←[36;1mRunning migrations:←[0m
   Applying rmigrate.0001_initial...←[32;1m OK←[0m
   Applying admin.0001_initial...←[32;1m OK←[0m
   Applying admin.0002_logentry_remove_auto_add...←[32;1m OK←[0m
   Applying admin.0003_logentry_add_action_flag_choices...←[32;1m OK←[0m
 (venv) PS C:\Users\Madhu\Desktop\Django\ticket33586\rmigration_bug> python
 manage.py makemigrations
 No changes detected


 (venv) PS C:\Users\Madhu\Desktop\Django\ticket33586\rmigration_bug> python
 manage.py migrate
 ←[36;1mOperations to perform:←[0m
 ←[1m  Apply all migrations: ←[0madmin, auth, contenttypes, rmigrate,
 sessions
 ←[36;1mRunning migrations:←[0m
   No migrations to apply.
 }}}

-- 
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/0107018637901ce7-e3cba9f3-840a-49aa-bc30-ad7e3605199b-00%40eu-central-1.amazonses.com.

Re: [Django] #34328: Class-based async-only middleware not detected as coroutine in MiddlewareMixin

2023-02-09 Thread Django 
#34328: Class-based async-only middleware not detected as coroutine in
MiddlewareMixin
-+-
 Reporter:  Sergei   |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Uncategorized|  Version:  4.1
 Severity:  Normal   |   Resolution:
 Keywords:  middleware async | Triage Stage:
  asyncio MiddlewareMixin|  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Sergei):

 I'm not even sure if it's a documentation issue - i.e. should it mention
 adding `asgiref.sync.markcoroutinefunction(self)` call to your own class-
 based middleware? Or is it async detection issue in `MiddlewareMixin`? Or
 possibly `asgiref`'s?

 By the way, I'm willing to work on this issue.

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/01070186378f8815-19261ee0-8ec8-49b8-9a88-51cc56707b44-00%40eu-central-1.amazonses.com.

[Django] #34328: Class-based async-only middleware not detected as coroutine in MiddlewareMixin

2023-02-09 Thread Django 
#34328: Class-based async-only middleware not detected as coroutine in
MiddlewareMixin
-+-
   Reporter:  Sergei |  Owner:  nobody
   Type:  Bug| Status:  new
  Component: |Version:  4.1
  Uncategorized  |   Keywords:  middleware async
   Severity:  Normal |  asyncio MiddlewareMixin
   Triage Stage: |  Has patch:  0
  Unreviewed |
Needs documentation:  0  |Needs tests:  0
Patch needs improvement:  0  |  Easy pickings:  0
  UI/UX:  0  |
-+-
 If an async middleware is implemented in class-based manner, other
 middleware in a chain may fail to recognize it as async. Stock Django
 middlewares use `MiddlewareMixin`, and it does not check for this kind of
 implementation.

 This results in coroutines leaking to sync code, and `AttributeError`'s
 raised for accessing things like `.status_code` on a coroutine object
 instead of a response.

 `MiddlewareMixin._async_check()` uses `asgiref.sync.iscoroutinefunction()`
 for checking.

 Small example (Python 3.10):

 {{{
 #!python

 >>> class TestMiddleware:
 ... async def __call__(self, request):
 ... pass

 >>> import asgiref.sync
 >>> import inspect
 >>> t = TestMiddleware()
 >>> asgiref.sync.iscoroutinefunction(t)
 False
 >>> inspect.iscoroutinefunction(t)
 False
 }}}

-- 
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/010701863788909b-45e1a62e-e305-4776-bc4c-ee27c5561164-00%40eu-central-1.amazonses.com.

Re: [Django] #34324: Django Discord Server is not mentioned in the "Join the Django community ❤️" section in contributing guide

2023-02-09 Thread Django 
#34324: Django Discord Server is not mentioned in the "Join the Django community
❤️" section in contributing guide
-+-
 Reporter:  Vibhakar Solanki |Owner:  Vibhakar
 Type:   |  Solanki
  Cleanup/optimization   |   Status:  assigned
Component:  Documentation|  Version:  dev
 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 Vibhakar Solanki):

 Great, i'll open a PR soon

-- 
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/01070186375f84fb-52c910e2-90c2-46aa-a686-bdd74b62c559-00%40eu-central-1.amazonses.com.

Re: [Django] #34327: Test client session does not work as described when using signed cookie engine

2023-02-09 Thread Django 
#34327: Test client session does not work as described when using signed cookie
engine
-+-
 Reporter:  Sergei   |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Testing framework|  Version:  dev
 Severity:  Normal   |   Resolution:
 Keywords:  session  | Triage Stage:
  signed_cookies |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Sergei):

 Also, can I fix this and do a PR?

 I think it's possible to make a test client API like this:

 {{{
 #!python

 # introduce setter for session
 # short-circuit if passing SessionBase type
 client.session = session_store

 # if not SessionBase, then assume it's a map type -> .items()
 # completely replace session data
 client.session = {'foo': 'bar'}

 # update
 session = client.session
 session.update({'foo': 'bar'})
 client.session = session
 }}}

 Old way from the docs would continue to work (if not signed cookies
 store).

-- 
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/0107018637568835-d5c26b5b-7627-4b7c-bf67-6e8380233b5b-00%40eu-central-1.amazonses.com.

[Django] #34327: Test client session does not work as described when using signed cookie engine

2023-02-09 Thread Django 
#34327: Test client session does not work as described when using signed cookie
engine
-+-
   Reporter:  Sergei |  Owner:  nobody
   Type:  Bug| Status:  new
  Component:  Testing|Version:  dev
  framework  |   Keywords:  session
   Severity:  Normal |  signed_cookies
   Triage Stage: |  Has patch:  0
  Unreviewed |
Needs documentation:  0  |Needs tests:  0
Patch needs improvement:  0  |  Easy pickings:  0
  UI/UX:  0  |
-+-
 The following snippet from
 
[https://docs.djangoproject.com/en/dev/topics/testing/tools/#django.test.Client.session
 the documentation] does not work when using
 `django.contrib.sessions.backends.signed_cookies`:

 {{{
 #!python
 def test_something(self):
 session = self.client.session
 session['somekey'] = 'test'
 session.save()
 }}}

 `session.save()` is not enough in this case: session key is session data
 itself and test client cookies need to be updated.
 Like `session` getter does when creating session store object
 (`django/test/client.py:732`):

 {{{
 #!python
 self.cookies[settings.SESSION_COOKIE_NAME] = session.session_key
 }}}

-- 
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/01070186374efe9b-7d3a193a-b800-4ed1-bdd3-49888b023e91-00%40eu-central-1.amazonses.com.

Re: [Django] #31920: ASGI/ASYNC SessionMiddleware - SynchronousOnlyOperation exception if request.user is not unwrapped in sync code

2023-02-09 Thread Django 
#31920: ASGI/ASYNC SessionMiddleware - SynchronousOnlyOperation exception if
request.user is not unwrapped in sync code
--+
 Reporter:  Michael Galler|Owner:  lirontb
 Type:  New feature   |   Status:  assigned
Component:  contrib.sessions  |  Version:  3.1
 Severity:  Normal|   Resolution:
 Keywords:  async | Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  1
  Needs tests:  0 |  Patch needs improvement:  1
Easy pickings:  0 |UI/UX:  0
--+

Comment (by Carlton Gibson):

 I think Adam is likely right here. We should likely have a separate
 `auser()`, similarly to elsewhere.

 > ''To await, or not await, 'tis the question''

-- 
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/0107018636ecfcba-7991fecc-f6f7-433e-82ed-8ae499671e86-00%40eu-central-1.amazonses.com.

Re: [Django] #34248: sdist is missing tox.ini

2023-02-09 Thread Django 
#34248: sdist is missing tox.ini
-+-
 Reporter:  Marcel Telka |Owner:  Syed
 Type:   |  Sajjad Hussain Shah
  Cleanup/optimization   |   Status:  assigned
Component:  Packaging|  Version:  4.1
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-
Changes (by Syed Sajjad Hussain Shah):

 * has_patch:  0 => 1


Comment:

 PR: https://github.com/django/django/pull/16536

-- 
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/0107018636de0820-71a634a4-16bf-43f0-94c7-771b9d40a7ac-00%40eu-central-1.amazonses.com.

Re: [Django] #34248: sdist is missing tox.ini

2023-02-09 Thread Django 
#34248: sdist is missing tox.ini
-+-
 Reporter:  Marcel Telka |Owner:  Syed
 Type:   |  Sajjad Hussain Shah
  Cleanup/optimization   |   Status:  assigned
Component:  Packaging|  Version:  4.1
 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 Syed Sajjad Hussain Shah):

 Resolved it on my branch:
 https://github.com/syedsajjadkazmii/django/tree/ticket_34248

-- 
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/0107018636daa0e7-1e620021-32b1-4b5e-859b-f902e64cfeee-00%40eu-central-1.amazonses.com.

Re: [Django] #34326: Standardize case for commands

2023-02-09 Thread Django 
#34326: Standardize case for commands
-+-
 Reporter:  Shiva Shane Ramdeen  |Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |
Component:  Core (Management |  Version:  dev
  commands)  |
 Severity:  Normal   |   Resolution:
 Keywords:  Commands, Command| Triage Stage:
  Case   |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Tim Graham):

 It looks like there are two built-in commands that use underscores (snake
 case): `remove_stale_contenttypes` and `ping_google`. I never noticed the
 inconsistency, and I doubt it causes much confusion. Are you really
 struggling with it? Perhaps commands in third-party packages are affected?

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/0107018636c3a344-40fd-6d46-4a05-8f9a-ca979d0d22ef-00%40eu-central-1.amazonses.com.

Re: [Django] #34248: sdist is missing tox.ini

2023-02-09 Thread Django 
#34248: sdist is missing tox.ini
-+-
 Reporter:  Marcel Telka |Owner:
 Type:   |  syedsajjadkazmii
  Cleanup/optimization   |   Status:  assigned
Component:  Packaging|  Version:  4.1
 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 syedsajjadkazmii):

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


Comment:

 I would like to work on 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/0107018636ae0103-6f5e7b47-2b26-4855-a2bf-8f9c32264c79-00%40eu-central-1.amazonses.com.

[Django] #34326: Standardize case for commands

2023-02-09 Thread Django 
#34326: Standardize case for commands
-+-
   Reporter: |  Owner:  nobody
  shivaRamdeen   |
   Type: | Status:  new
  Cleanup/optimization   |
  Component:  Core   |Version:  dev
  (Management commands)  |   Keywords:  Commands, Command
   Severity:  Normal |  Case
   Triage Stage: |  Has patch:  0
  Unreviewed |
Needs documentation:  0  |Needs tests:  0
Patch needs improvement:  0  |  Easy pickings:  0
  UI/UX:  0  |
-+-
 Are there any plans to standardize the case of commands in django?

 As an alternative the ability to automatically match snake_case to
 flatcase command names would be 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/0107018636a140f6-69463a76-5680-4cf9-a22d-dcb9d2dcc16e-00%40eu-central-1.amazonses.com.

Re: [Django] #34325: PercentRank confusion

2023-02-09 Thread Django 
#34325: PercentRank confusion
---+--
 Reporter:  dvg|Owner:  nobody
 Type:  Uncategorized  |   Status:  new
Component:  Documentation  |  Version:  4.1
 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 dvg:

Old description:

> The [https://docs.djangoproject.com/en/4.1/ref/models/database-
> functions/#percentrank documentation for the PercentRank window function]
> says:
>
>   Computes the 'percentile rank' of the rows in the frame clause.
> This computation is equivalent to evaluating:
>   {{{
>   (rank - 1) / (total rows - 1)
>   }}}
>
> (my emphasis)
>
> However, I'm not so sure
> "[https://en.wikipedia.org/w/index.php?title=Percentile&oldid=1114275310
> percentile] rank" is the correct term.
>
> If you look up the (statistical) term "percentile rank" online, you'll
> find various definitions,
> [https://en.wikipedia.org/w/index.php?title=Percentile_rank&oldid=1136815121
> ranging from]
>
> {{{
> (CF - 0.5 * F) / N
> }}}
>
>   where CF—the cumulative frequency—is the count of all scores less than
> or equal to the score of interest, F is the frequency for the score of
> interest, and N is the number of scores in the distribution.
>
> [https://www.geo.fu-berlin.de/en/v/soga/Basics-of-statistics/Descriptive-
> Statistics/Measures-of-Position/Percentiles-and-Percentile-
> Rank/index.html to something like]
>
> {{{
>  /  values in the data set>
> }}}
>
> (equivalent to `(CF - F) / N`)
>
> Similar definitions are also used e.g. by
> [https://github.com/scipy/scipy/blob/dde50595862a4f9cede24b5d1c86935c30f1f88a/scipy/stats/_stats_py.py#L2190
> scipy].
>
> The latter definition is similar to that in the Django docs, but still
> subtly different in the denominator.
>
> Note also that the documentation for the `percent_rank` function in the
> [https://www.sqlite.org/windowfunctions.html#built_in_window_functions
> SQLite] and [https://www.postgresql.org/docs/15/functions-window.html
> PostgreSQL] database backends does '''not''' mention "percentile rank" at
> all. Instead, they use the term '''"relative rank."'''
>
> To prevent confusion, wouldn't it be better to use the same terminology
> as the database backends?

New description:

 The [https://docs.djangoproject.com/en/4.1/ref/models/database-
 functions/#percentrank documentation for the PercentRank window function]
 says:

   Computes the 'percentile rank' of the rows in the frame clause.
 This computation is equivalent to evaluating:
   {{{
   (rank - 1) / (total rows - 1)
   }}}

 (my emphasis)

 However, I'm not so sure
 "[https://en.wikipedia.org/w/index.php?title=Percentile&oldid=1114275310
 percentile] rank" is the correct term.

 If you look up the (statistical) term "percentile rank" online, you'll
 find various definitions,
 [https://en.wikipedia.org/w/index.php?title=Percentile_rank&oldid=1136815121
 ranging from]

 {{{
 (CF - 0.5 * F) / N
 }}}

   where CF—the cumulative frequency—is the count of all scores less than
 or equal to the score of interest, F is the frequency for the score of
 interest, and N is the number of scores in the distribution.

 [https://www.geo.fu-berlin.de/en/v/soga/Basics-of-statistics/Descriptive-
 Statistics/Measures-of-Position/Percentiles-and-Percentile-Rank/index.html
 to something like]

 {{{
  / 
 }}}

 (equivalent to `(CF - F) / N`)

 Both definitions are also used e.g. by
 
[https://github.com/scipy/scipy/blob/dde50595862a4f9cede24b5d1c86935c30f1f88a/scipy/stats/_stats_py.py#L2190
 scipy].

 The latter definition is similar to that in the Django docs, but still
 subtly different in the denominator.

 Note also that the documentation for the `percent_rank` function in the
 [https://www.sqlite.org/windowfunctions.html#built_in_window_functions
 SQLite] and [https://www.postgresql.org/docs/15/functions-window.html
 PostgreSQL] database backends does '''not''' mention "percentile rank" at
 all. Instead, they use the term '''"relative rank."'''

 To prevent confusion, wouldn't it be better to use the same terminology as
 the database backends?

--

-- 
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

Re: [Django] #34325: PercentRank confusion

2023-02-09 Thread Django 
#34325: PercentRank confusion
---+--
 Reporter:  dvg|Owner:  nobody
 Type:  Uncategorized  |   Status:  new
Component:  Documentation  |  Version:  4.1
 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 dvg:

Old description:

> The [https://docs.djangoproject.com/en/4.1/ref/models/database-
> functions/#percentrank documentation for the PercentRank window function]
> says:
>
>   Computes the 'percentile rank' of the rows in the frame clause.
> This computation is equivalent to evaluating:
>   {{{
>   (rank - 1) / (total rows - 1)
>   }}}
>
> (my emphasis)
>
> However, I'm not so sure
> "[https://en.wikipedia.org/w/index.php?title=Percentile&oldid=1114275310
> percentile] rank" is the correct term.
>
> If you look up the (statistical) term "percentile rank" online, you'll
> find various definitions,
> [https://en.wikipedia.org/w/index.php?title=Percentile_rank&oldid=1136815121
> ranging from]
>
> {{{
> (CF - 0.5 * F) / N
> }}}
>
>   where CF—the cumulative frequency—is the count of all scores less than
> or equal to the score of interest, F is the frequency for the score of
> interest, and N is the number of scores in the distribution.
>
> [https://www.geo.fu-berlin.de/en/v/soga/Basics-of-statistics/Descriptive-
> Statistics/Measures-of-Position/Percentiles-and-Percentile-
> Rank/index.html to something like]
>
> {{{
>  /  values in the data set>
> }}}
>
> (equivalent to `(CF - F) / N`)
>
> Similar definitions are also used e.g. by
> [https://github.com/scipy/scipy/blob/dde50595862a4f9cede24b5d1c86935c30f1f88a/scipy/stats/_stats_py.py#L2182
> scipy].
>
> The latter definition is similar to that in the Django docs, but still
> subtly different in the denominator.
>
> Note also that the documentation for the `percent_rank` function in the
> [https://www.sqlite.org/windowfunctions.html#built_in_window_functions
> SQLite] and [https://www.postgresql.org/docs/15/functions-window.html
> PostgreSQL] database backends does '''not''' mention "percentile rank" at
> all. Instead, they use the term '''"relative rank."'''
>
> To prevent confusion, wouldn't it be better to use the same terminology
> as the database backends?

New description:

 The [https://docs.djangoproject.com/en/4.1/ref/models/database-
 functions/#percentrank documentation for the PercentRank window function]
 says:

   Computes the 'percentile rank' of the rows in the frame clause.
 This computation is equivalent to evaluating:
   {{{
   (rank - 1) / (total rows - 1)
   }}}

 (my emphasis)

 However, I'm not so sure
 "[https://en.wikipedia.org/w/index.php?title=Percentile&oldid=1114275310
 percentile] rank" is the correct term.

 If you look up the (statistical) term "percentile rank" online, you'll
 find various definitions,
 [https://en.wikipedia.org/w/index.php?title=Percentile_rank&oldid=1136815121
 ranging from]

 {{{
 (CF - 0.5 * F) / N
 }}}

   where CF—the cumulative frequency—is the count of all scores less than
 or equal to the score of interest, F is the frequency for the score of
 interest, and N is the number of scores in the distribution.

 [https://www.geo.fu-berlin.de/en/v/soga/Basics-of-statistics/Descriptive-
 Statistics/Measures-of-Position/Percentiles-and-Percentile-Rank/index.html
 to something like]

 {{{
  / 
 }}}

 (equivalent to `(CF - F) / N`)

 Similar definitions are also used e.g. by
 
[https://github.com/scipy/scipy/blob/dde50595862a4f9cede24b5d1c86935c30f1f88a/scipy/stats/_stats_py.py#L2190
 scipy].

 The latter definition is similar to that in the Django docs, but still
 subtly different in the denominator.

 Note also that the documentation for the `percent_rank` function in the
 [https://www.sqlite.org/windowfunctions.html#built_in_window_functions
 SQLite] and [https://www.postgresql.org/docs/15/functions-window.html
 PostgreSQL] database backends does '''not''' mention "percentile rank" at
 all. Instead, they use the term '''"relative rank."'''

 To prevent confusion, wouldn't it be better to use the same terminology as
 the database backends?

--

-- 
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.

Re: [Django] #34325: PercentRank confusion

2023-02-09 Thread Django 
#34325: PercentRank confusion
---+--
 Reporter:  dvg|Owner:  nobody
 Type:  Uncategorized  |   Status:  new
Component:  Documentation  |  Version:  4.1
 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 dvg:

Old description:

> The [https://docs.djangoproject.com/en/4.1/ref/models/database-
> functions/#percentrank documentation for the PercentRank window function]
> says:
>
>   Computes the 'percentile rank' of the rows in the frame clause.
> This computation is equivalent to evaluating:
>   {{{
>   (rank - 1) / (total rows - 1)
>   }}}
>
> (my emphasis)
>
> However, I'm not so sure
> "[https://en.wikipedia.org/w/index.php?title=Percentile&oldid=1114275310
> percentile] rank" is the correct term.
>
> If you look up the (statistical) term "percentile rank" online, you'll
> find various definitions,
> [https://en.wikipedia.org/w/index.php?title=Percentile_rank&oldid=1136815121
> ranging from]
>
> {{{
> (CF - 0.5 * F) / N
> }}}
>
>   where CF—the cumulative frequency—is the count of all scores less than
> or equal to the score of interest, F is the frequency for the score of
> interest, and N is the number of scores in the distribution.
>
> [https://www.geo.fu-berlin.de/en/v/soga/Basics-of-statistics/Descriptive-
> Statistics/Measures-of-Position/Percentiles-and-Percentile-
> Rank/index.html to something like]
>
> {{{
>  /  values in the data set>
> }}}
>
> (equivalent to `(CF - F) / N`)
>
> Both of these definitions are also used e.g. by
> [https://github.com/scipy/scipy/blob/dde50595862a4f9cede24b5d1c86935c30f1f88a/scipy/stats/_stats_py.py#L2182
> scipy].
>
> The latter definition is similar to that in the Django docs, but still
> subtly different in the denominator.
>
> Note also that the documentation for the `percent_rank` function in the
> [https://www.sqlite.org/windowfunctions.html#built_in_window_functions
> SQLite] and [https://www.postgresql.org/docs/15/functions-window.html
> PostgreSQL] database backends does '''not''' mention "percentile rank" at
> all. Instead, they use the term '''"relative rank."'''
>
> To prevent confusion, wouldn't it be better to use the same terminology
> as the database backends?

New description:

 The [https://docs.djangoproject.com/en/4.1/ref/models/database-
 functions/#percentrank documentation for the PercentRank window function]
 says:

   Computes the 'percentile rank' of the rows in the frame clause.
 This computation is equivalent to evaluating:
   {{{
   (rank - 1) / (total rows - 1)
   }}}

 (my emphasis)

 However, I'm not so sure
 "[https://en.wikipedia.org/w/index.php?title=Percentile&oldid=1114275310
 percentile] rank" is the correct term.

 If you look up the (statistical) term "percentile rank" online, you'll
 find various definitions,
 [https://en.wikipedia.org/w/index.php?title=Percentile_rank&oldid=1136815121
 ranging from]

 {{{
 (CF - 0.5 * F) / N
 }}}

   where CF—the cumulative frequency—is the count of all scores less than
 or equal to the score of interest, F is the frequency for the score of
 interest, and N is the number of scores in the distribution.

 [https://www.geo.fu-berlin.de/en/v/soga/Basics-of-statistics/Descriptive-
 Statistics/Measures-of-Position/Percentiles-and-Percentile-Rank/index.html
 to something like]

 {{{
  / 
 }}}

 (equivalent to `(CF - F) / N`)

 Similar definitions are also used e.g. by
 
[https://github.com/scipy/scipy/blob/dde50595862a4f9cede24b5d1c86935c30f1f88a/scipy/stats/_stats_py.py#L2182
 scipy].

 The latter definition is similar to that in the Django docs, but still
 subtly different in the denominator.

 Note also that the documentation for the `percent_rank` function in the
 [https://www.sqlite.org/windowfunctions.html#built_in_window_functions
 SQLite] and [https://www.postgresql.org/docs/15/functions-window.html
 PostgreSQL] database backends does '''not''' mention "percentile rank" at
 all. Instead, they use the term '''"relative rank."'''

 To prevent confusion, wouldn't it be better to use the same terminology as
 the database backends?

--

-- 
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.g

Re: [Django] #34325: PercentRank confusion

2023-02-09 Thread Django 
#34325: PercentRank confusion
---+--
 Reporter:  dvg|Owner:  nobody
 Type:  Uncategorized  |   Status:  new
Component:  Documentation  |  Version:  4.1
 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 dvg:

Old description:

> The [https://docs.djangoproject.com/en/4.1/ref/models/database-
> functions/#percentrank documentation for the PercentRank window function]
> says:
>
>   Computes the 'percentile rank' of the rows in the frame clause.
> This computation is equivalent to evaluating:
>   {{{
>   (rank - 1) / (total rows - 1)
>   }}}
>
> (my emphasis)
>
> However, I'm not so sure
> "[https://en.wikipedia.org/w/index.php?title=Percentile&oldid=1114275310
> percentile] rank" is the correct term.
>
> If you look up the (statistical) term "percentile rank" online, you'll
> find various definitions,
> [https://en.wikipedia.org/w/index.php?title=Percentile_rank&oldid=1136815121
> ranging from]
>
> {{{
> (CF - 0.5 * F) / N
> }}}
>
>   where CF—the cumulative frequency—is the count of all scores less than
> or equal to the score of interest, F is the frequency for the score of
> interest, and N is the number of scores in the distribution.
>
> [https://www.geo.fu-berlin.de/en/v/soga/Basics-of-statistics/Descriptive-
> Statistics/Measures-of-Position/Percentiles-and-Percentile-
> Rank/index.html to something like]
>
> {{{
>  /  values in the data set>
> }}}
>
> However, none exactly matches the definition in the Django docs.
>
> Note also that the documentation for the `percent_rank` function in the
> [https://www.sqlite.org/windowfunctions.html#built_in_window_functions
> SQLite] and [https://www.postgresql.org/docs/15/functions-window.html
> PostgreSQL] database backends does '''not''' mention "percentile rank".
> Instead, they use the term "relative rank."
>
> To prevent confusion, wouldn't it be better to use the same terminology
> as the database backends?

New description:

 The [https://docs.djangoproject.com/en/4.1/ref/models/database-
 functions/#percentrank documentation for the PercentRank window function]
 says:

   Computes the 'percentile rank' of the rows in the frame clause.
 This computation is equivalent to evaluating:
   {{{
   (rank - 1) / (total rows - 1)
   }}}

 (my emphasis)

 However, I'm not so sure
 "[https://en.wikipedia.org/w/index.php?title=Percentile&oldid=1114275310
 percentile] rank" is the correct term.

 If you look up the (statistical) term "percentile rank" online, you'll
 find various definitions,
 [https://en.wikipedia.org/w/index.php?title=Percentile_rank&oldid=1136815121
 ranging from]

 {{{
 (CF - 0.5 * F) / N
 }}}

   where CF—the cumulative frequency—is the count of all scores less than
 or equal to the score of interest, F is the frequency for the score of
 interest, and N is the number of scores in the distribution.

 [https://www.geo.fu-berlin.de/en/v/soga/Basics-of-statistics/Descriptive-
 Statistics/Measures-of-Position/Percentiles-and-Percentile-Rank/index.html
 to something like]

 {{{
  / 
 }}}

 (equivalent to `(CF - F) / N`)

 Both of these definitions are also used e.g. by
 
[https://github.com/scipy/scipy/blob/dde50595862a4f9cede24b5d1c86935c30f1f88a/scipy/stats/_stats_py.py#L2182
 scipy].

 The latter definition is similar to that in the Django docs, but still
 subtly different in the denominator.

 Note also that the documentation for the `percent_rank` function in the
 [https://www.sqlite.org/windowfunctions.html#built_in_window_functions
 SQLite] and [https://www.postgresql.org/docs/15/functions-window.html
 PostgreSQL] database backends does '''not''' mention "percentile rank" at
 all. Instead, they use the term '''"relative rank."'''

 To prevent confusion, wouldn't it be better to use the same terminology as
 the database backends?

--

-- 
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/010701863692ba51-25190d0c-3f7d-4670-a5b2-8196522b9382-00%40eu-central-1.amazonses.com.

[Django] #34325: PercentRank confusion

2023-02-09 Thread Django 
#34325: PercentRank confusion
-+
   Reporter:  dvg|  Owner:  nobody
   Type:  Uncategorized  | Status:  new
  Component:  Documentation  |Version:  4.1
   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  |
-+
 The [https://docs.djangoproject.com/en/4.1/ref/models/database-
 functions/#percentrank documentation for the PercentRank window function]
 says:

   Computes the 'percentile rank' of the rows in the frame clause.
 This computation is equivalent to evaluating:
   {{{
   (rank - 1) / (total rows - 1)
   }}}

 (my emphasis)

 However, I'm not so sure
 "[https://en.wikipedia.org/w/index.php?title=Percentile&oldid=1114275310
 percentile] rank" is the correct term.

 If you look up the (statistical) term "percentile rank" online, you'll
 find various definitions,
 [https://en.wikipedia.org/w/index.php?title=Percentile_rank&oldid=1136815121
 ranging from]

 {{{
 (CF - 0.5 * F) / N
 }}}

   where CF—the cumulative frequency—is the count of all scores less than
 or equal to the score of interest, F is the frequency for the score of
 interest, and N is the number of scores in the distribution.

 [https://www.geo.fu-berlin.de/en/v/soga/Basics-of-statistics/Descriptive-
 Statistics/Measures-of-Position/Percentiles-and-Percentile-Rank/index.html
 to something like]

 {{{
  / 
 }}}

 However, none exactly matches the definition in the Django docs.

 Note also that the documentation for the `percent_rank` function in the
 [https://www.sqlite.org/windowfunctions.html#built_in_window_functions
 SQLite] and [https://www.postgresql.org/docs/15/functions-window.html
 PostgreSQL] database backends does '''not''' mention "percentile rank".
 Instead, they use the term "relative rank."

 To prevent confusion, wouldn't it be better to use the same terminology as
 the database backends?

-- 
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/010701863666ec17-5b3186ec-7ceb-4320-9697-51b513fc4f06-00%40eu-central-1.amazonses.com.

Re: [Django] #25706: Support CSP default-src 'self' on Django Admin GIS

2023-02-09 Thread Django 
#25706: Support CSP default-src 'self' on Django Admin GIS
-+-
 Reporter:  Thomas Grainger  |Owner:  Claude
 Type:   |  Paroz
  Cleanup/optimization   |   Status:  assigned
Component:  GIS  |  Version:  dev
 Severity:  Normal   |   Resolution:
 Keywords:  CSP inline   | Triage Stage:  Accepted
  javascript |
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Mariusz Felisiak):

 Claude, Is there anything left for this ticket 🤔 ?

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/0107018636436179-795bd028-79f8-4be4-9913-1d8cbb7c0ed8-00%40eu-central-1.amazonses.com.

Re: [Django] #33537: Cloning test databases should reraise errors on MySQL.

2023-02-09 Thread Django 
#33537: Cloning test databases should reraise errors on MySQL.
-+-
 Reporter:  Stephen Finucane |Owner:  Stephen
 Type:   |  Finucane
  Cleanup/optimization   |   Status:  assigned
Component:  Database layer   |  Version:  4.1
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Mariusz Felisiak):

 * owner:  nobody => Stephen Finucane
 * needs_better_patch:  0 => 1
 * has_patch:  0 => 1
 * status:  new => assigned


Comment:

 [https://github.com/django/django/pull/16170 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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/01070186363b06b4-cfd9efdb-9b12-408c-9f66-963f4031411a-00%40eu-central-1.amazonses.com.

Re: [Django] #34322: ManifestStaticFilesStorage crashes on commented JavaScript import statements

2023-02-09 Thread Django 
#34322: ManifestStaticFilesStorage crashes on commented JavaScript import
statements
-+
 Reporter:  Adam Johnson |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  contrib.staticfiles  |  Version:  4.2
 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 Adam Johnson):

 I think it's worth noting that this kind of failure was always possible
 with the other replaced regexes. Commented `url()` or `@import` lines in a
 CSS file could always fail in a similar way. It seems that the TypeScript
 syntax has made it way more likely that there will be commented
 unresolvable imports in JavaScript files.

-- 
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/0107018635e272ce-b740bc38-fe93-4712-a2a4-521caccf377c-00%40eu-central-1.amazonses.com.

Re: [Django] #34322: ManifestStaticFilesStorage crashes on commented JavaScript import statements

2023-02-09 Thread Django 
#34322: ManifestStaticFilesStorage crashes on commented JavaScript import
statements
-+
 Reporter:  Adam Johnson |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  contrib.staticfiles  |  Version:  4.2
 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
-+

Old description:

> #32319 added module support to `ManifestStaticFilesStorage`. It can crash
> with imports in comments, which bundlers like Webpack can leave in.
>
> Example:
>
> {{{
> //** @type {import("./htmx").HtmxApi} */
> }}}
>
> Leads to:
>
> {{{
> whitenoise.storage.MissingFileError: The file 'example/dist/htmx' could
> not be found with
>  0x16ff630a0>.
>
> The JS file 'example/dist/app.js' references a file which could not be
> found:
>   example/dist/htmx
>
> Please check the URL references in this JS file, particularly any
> relative paths which might be pointing to the wrong location.
> }}}
>
> The regex should be adjusted to only select imports that are alone on a
> line, with whitespace.

New description:

 #32319 added module support to `ManifestStaticFilesStorage`. It can crash
 with imports in comments, which are used for Typescript
 ([https://www.typescriptlang.org/docs/handbook/jsdoc-supported-types.html
 #import-types docs]) but don't necessarily resolve when code is bundled.

 Example [https://github.com/bigskysoftware/htmx/blob/master/src/htmx.js
 from htmx]:

 {{{
 //** @type {import("./htmx").HtmxApi} */
 }}}

 Leads to:

 {{{
 whitenoise.storage.MissingFileError: The file 'example/dist/htmx' could
 not be found with .

 The JS file 'example/dist/app.js' references a file which could not be
 found:
   example/dist/htmx

 Please check the URL references in this JS file, particularly any
 relative paths which might be pointing to the wrong location.
 }}}

 The regex should be adjusted to only select imports that are alone on a
 line, with whitespace.

 This may be a challenge as comments can be multi-line like:

 {{{
 /**
  * @param {HTMLElement} elt
  * @returns {import("./htmx").HtmxTriggerSpecification[]}
  */
 }}}

--

Comment (by Adam Johnson):

 Added more detail to description about possible failures

-- 
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/0107018635dff19a-ce51e75d-3171-4088-86e6-2bc4714657e0-00%40eu-central-1.amazonses.com.

Re: [Django] #22887: unique_for_date error message in Field has untranslated param lookup_type

2023-02-09 Thread Django 
#22887: unique_for_date error message in Field has untranslated param 
lookup_type
--+
 Reporter:  Vlada Macek   |Owner:  (none)
 Type:  Cleanup/optimization  |   Status:  new
Component:  Internationalization  |  Version:  dev
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  1
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  1
--+
Changes (by Mariusz Felisiak):

 * status:  assigned => new


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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/0107018635c761c1-15ff3c05-894d-4a39-82e4-1b7156b66464-00%40eu-central-1.amazonses.com.

Re: [Django] #22887: unique_for_date error message in Field has untranslated param lookup_type

2023-02-09 Thread Django 
#22887: unique_for_date error message in Field has untranslated param 
lookup_type
--+
 Reporter:  Vlada Macek   |Owner:  (none)
 Type:  Cleanup/optimization  |   Status:  assigned
Component:  Internationalization  |  Version:  dev
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  1
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  1
--+
Changes (by Mariusz Felisiak):

 * owner:  Federico Frenguelli => (none)
 * 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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/0107018635c752a5-c021bbfd-4e5f-4668-bd66-09d618a1a9b1-00%40eu-central-1.amazonses.com.

Re: [Django] #32539: Support accessing the current filtered queryset from within SimpleListFilter.lookups()

2023-02-09 Thread Django 
#32539: Support accessing the current filtered queryset from within
SimpleListFilter.lookups()
+---
 Reporter:  Simon Willison  |Owner:  Sarah Boyce
 Type:  New feature |   Status:  assigned
Component:  contrib.admin   |  Version:  3.1
 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 Mariusz Felisiak):

 * needs_better_patch:  0 => 1


Comment:

 See [https://github.com/django/django/pull/16495#issuecomment-1419546008
 comment].

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/0107018635a7f68a-66856845-a0f4-4a06-8c30-d1796bfde9a7-00%40eu-central-1.amazonses.com.

Re: [Django] #34045: Admin changelist checkboxes do not have labels

2023-02-09 Thread Django 
#34045: Admin changelist checkboxes do not have labels
---+---
 Reporter:  Tom Carrick|Owner:  Durval Carvalho
 Type:  Bug|   Status:  assigned
Component:  contrib.admin  |  Version:  dev
 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
---+---
Changes (by Mariusz Felisiak):

 * needs_better_patch:  0 => 1


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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/0107018635979ac3-4180f34f-3d87-47e0-8e88-e82e09e03b65-00%40eu-central-1.amazonses.com.

Re: [Django] #34045: Admin changelist checkboxes do not have labels

2023-02-09 Thread Django 
#34045: Admin changelist checkboxes do not have labels
---+---
 Reporter:  Tom Carrick|Owner:  Durval Carvalho
 Type:  Bug|   Status:  assigned
Component:  contrib.admin  |  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:  1
---+---
Changes (by Mariusz Felisiak):

 * has_patch:  0 => 1


Comment:

 [https://github.com/django/django/pull/16515 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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/0107018635976037-17aaeaad-08c8-4d40-8307-280435ef822a-00%40eu-central-1.amazonses.com.

Re: [Django] #34324: Django Discord Server is not mentioned in the "Join the Django community ❤️" section in contributing guide

2023-02-09 Thread Django 
#34324: Django Discord Server is not mentioned in the "Join the Django community
❤️" section in contributing guide
-+-
 Reporter:  Vibhakar Solanki |Owner:  Vibhakar
 Type:   |  Solanki
  Cleanup/optimization   |   Status:  assigned
Component:  Documentation|  Version:  dev
 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 Mariusz Felisiak):

 * type:  Bug => Cleanup/optimization


-- 
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/01070186358aa7c9-bef69ebb-c61b-4cca-8a1e-c8d1b48009c0-00%40eu-central-1.amazonses.com.

Re: [Django] #470: Add Field.db_default for defining database defaults

2023-02-09 Thread Django 
#470: Add Field.db_default for defining database defaults
-+-
 Reporter:  jws  |Owner:  Lily
 |  Foote
 Type:  New feature  |   Status:  assigned
Component:  Database layer   |  Version:  dev
  (models, ORM)  |
 Severity:  normal   |   Resolution:
 Keywords:  sql schema   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  1
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Mariusz Felisiak):

 * needs_better_patch:  0 => 1
 * version:   => dev
 * needs_docs:  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/010701863548c700-83d706ea-3fa5-4516-bb90-6c61201c980f-00%40eu-central-1.amazonses.com.