Re: [Django] #26168: BooleanField is forced to be blank=True

[Django]

#26168: BooleanField is forced to be blank=True
-+-
 Reporter:  fengyehong   |Owner:  Lynn
 Type:   |  Cyrin
  Cleanup/optimization   |   Status:  closed
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:  fixed
 Keywords:  BooleanField | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Tim Graham):

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


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

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

Re: [Django] #26168: BooleanField is forced to be blank=True

[Django]

#26168: BooleanField is forced to be blank=True
-+-
 Reporter:  fengyehong   |Owner:  Lynn
 Type:   |  Cyrin
  Cleanup/optimization   |   Status:  assigned
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  BooleanField | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Kamil Gałuszka):

 * cc: Kamil Gałuszka (added)


Comment:

 I think this was fixed with https://github.com/django/django/pull/8467 and
 #29227 . This ticket can be close then?

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

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

Re: [Django] #26168: BooleanField is forced to be blank=True

[Django]

#26168: BooleanField is forced to be blank=True
-+-
 Reporter:  fengyehong   |Owner:  Lynn
 Type:   |  Cyrin
  Cleanup/optimization   |   Status:  assigned
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  BooleanField | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Lynn Cyrin):

 * status:  new => assigned
 * owner:  nobody => Lynn Cyrin


Comment:

 The WIP PR https://github.com/django/django/pull/9016 I made for
 https://code.djangoproject.com/ticket/23130 addresses this

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

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

Re: [Django] #26168: BooleanField is forced to be blank=True

[Django]

#26168: BooleanField is forced to be blank=True
-+-
 Reporter:  fengyehong   |Owner:
 Type:   |  insomniac12
  Cleanup/optimization   |   Status:  assigned
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  BooleanField | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by insomniac12):

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


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

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

Re: [Django] #26168: BooleanField is forced to be blank=True

[Django]

#26168: BooleanField is forced to be blank=True
-+-
 Reporter:  fengyehong   |Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  BooleanField | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by jonashaag):

 * cc: jonas@… (added)


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

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

Re: [Django] #26168: BooleanField is forced to be blank=True

[Django]

#26168: BooleanField is forced to be blank=True
-+-
 Reporter:  fengyehong   |Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  BooleanField | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by jonashaag):

 There's an outdated patch in #23130, which I still think is the best
 solution to this problem. Somehow, I've never gotten around to finishing
 the patch, but I think it should take no more than an hour of time to get
 it up to date and pass the test suite.

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

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

Re: [Django] #26168: BooleanField is forced to be blank=True (was: Django forcibly allow BooleanField blank)

[Django]

#26168: BooleanField is forced to be blank=True
-+-
 Reporter:  fengyehong   |Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  BooleanField | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by timgraham):

 * needs_better_patch:   => 0
 * needs_tests:   => 0
 * needs_docs:   => 0
 * type:  Uncategorized => Cleanup/optimization
 * stage:  Unreviewed => Accepted


Comment:

 See #22282 and #23130 for some related discussion. I'm not sure what the
 proper resolution is, but I'll accept the ticket since this this has come
 up several time. We can at least document the reasons for this if it can't
 be changed for backwards compatibility reasons.

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

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