Re: [Django] #29049: Add slicing notation to F expressions

[Django]

#29049: Add slicing notation to F expressions
-+-
 Reporter:  Matthew Pava |Owner:  Abhinav
 |  Yadav
 Type:  New feature  |   Status:  assigned
Component:  Database layer   |  Version:  dev
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  slice F  | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Abhinav Yadav):

 * needs_better_patch:  1 => 0


Comment:

 [https://github.com/django/django/pull/16310 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/010701848ca112f5-9a8eb43d-c12f-4fd1-a2bf-5d5c91698137-00%40eu-central-1.amazonses.com.

Re: [Django] #29062: "database table locked errors" when using sqlite in-memory database with LiveServerTestCase

[Django]

#29062: "database table locked errors" when using sqlite in-memory database with
LiveServerTestCase
-+-
 Reporter:  Juozas Masiulis  |Owner:
 |  Christophe Baldy
 Type:  Bug  |   Status:  assigned
Component:  Testing framework|  Version:  2.0
 Severity:  Normal   |   Resolution:
 Keywords:  sqlite, testing, | Triage Stage:  Accepted
  databases  |
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Mariusz Felisiak):

 * has_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/010701848bf2cbbf-4a1c6cdf-ec1a-435a-9e3e-ba29e24ad5c6-00%40eu-central-1.amazonses.com.

Re: [Django] #29062: "database table locked errors" when using sqlite in-memory database with LiveServerTestCase

[Django]

#29062: "database table locked errors" when using sqlite in-memory database with
LiveServerTestCase
-+-
 Reporter:  Juozas Masiulis  |Owner:
 |  Christophe Baldy
 Type:  Bug  |   Status:  assigned
Component:  Testing framework|  Version:  2.0
 Severity:  Normal   |   Resolution:
 Keywords:  sqlite, testing, | Triage Stage:  Accepted
  databases  |
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Christophe Baldy):

 * owner:  nobody => Christophe Baldy
 * status:  new => assigned


Comment:

 I posted a PR for this ticket
 (https://github.com/django/django/pull/16309) following Chris Jerdonek
 previous fix

-- 
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/010701848bd50441-fff4c159-24db-4726-a537-613220446d6a-00%40eu-central-1.amazonses.com.

Re: [Django] #34119: ModelForm fields with callable defaults don't correctly propagate default values

[Django]

#34119: ModelForm fields with callable defaults don't correctly propagate 
default
values
-+-
 Reporter:  Benjamin Rigaud  |Owner:  David
 |  Sanders
 Type:  Bug  |   Status:  closed
Component:  Forms|  Version:  4.1
 Severity:  Normal   |   Resolution:  fixed
 Keywords:  modelform| Triage Stage:  Ready for
 |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Mariusz Felisiak ):

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


Comment:

 In [changeset:"25904db9154c5be3ecda9585d96f536841af9126" 25904db9]:
 {{{
 #!CommitTicketReference repository=""
 revision="25904db9154c5be3ecda9585d96f536841af9126"
 Fixed #34119 -- Prevented callable default hidden widget value from being
 overridden.

 Thanks to Benjamin Rigaud 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/010701848af3d0c0-02d3f277-8899-48e1-9186-cc02e150bd5d-00%40eu-central-1.amazonses.com.

Re: [Django] #26261: QuerySet.exclude() crashes when referencing related_query_name of GenericRelation

[Django]

#26261: QuerySet.exclude() crashes when referencing related_query_name of
GenericRelation
-+-
 Reporter:  Amir Hadi|Owner:
 |  gorodovoy9000
 Type:  Bug  |   Status:  closed
Component:   |  Version:  1.8
  contrib.contenttypes   |
 Severity:  Normal   |   Resolution:  fixed
 Keywords:  GenericRelation  | Triage Stage:  Ready for
  exclude|  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Mariusz Felisiak ):

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


Comment:

 In [changeset:"04b15022e8d1f49af69d8a1e6cd678f31f1280ff" 04b1502]:
 {{{
 #!CommitTicketReference repository=""
 revision="04b15022e8d1f49af69d8a1e6cd678f31f1280ff"
 Fixed #26261 -- Fixed queryset crash when excluding reverse
 GenericRelation.

 Thanks Amir Hadi 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/010701848a4d5d98-0411262a-1997-478f-93fe-f7123cbd02fd-00%40eu-central-1.amazonses.com.

Re: [Django] #26261: QuerySet.exclude() crashes when referencing related_query_name of GenericRelation

[Django]

#26261: QuerySet.exclude() crashes when referencing related_query_name of
GenericRelation
-+-
 Reporter:  Amir Hadi|Owner:
 |  gorodovoy9000
 Type:  Bug  |   Status:  assigned
Component:   |  Version:  1.8
  contrib.contenttypes   |
 Severity:  Normal   |   Resolution:
 Keywords:  GenericRelation  | Triage Stage:  Ready for
  exclude|  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/0107018489e77899-f51962f4-b1cd-4193-a81e-838753f48ffd-00%40eu-central-1.amazonses.com.

Re: [Django] #34160: Django 4.1 Expression contains mixed types for (Big/Small)IntegerFields.

[Django]

#34160: Django 4.1 Expression contains mixed types for (Big/Small)IntegerFields.
-+-
 Reporter:  Martin Lehoux|Owner:  Martin
 |  Lehoux
 Type:  Bug  |   Status:  assigned
Component:  Database layer   |  Version:  4.1
  (models, ORM)  |
 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 Martin Lehoux):

 If I understand well, you mean that the future vision (given the comment
 you pointed out) is not to try to infer everything, and that I should
 indeed in my code specify this `output_field` in this case?

 Just trying to understand what I should do on my side, and if there's a
 way for me to help you with that

-- 
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/0107018489c782f4-bf320ebf-e7e3-4c3f-9da2-1e14cd04b184-00%40eu-central-1.amazonses.com.