Re: [Django] #26807: Document how to replicate SubfieldBase behavior of calling to_python on assignment

[Django]

#26807: Document how to replicate SubfieldBase behavior of calling to_python on
assignment
--+
 Reporter:  akx   |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  closed
Component:  Documentation |  Version:  1.8
 Severity:  Normal|   Resolution:  fixed
 Keywords:| Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+

Comment (by Tim Graham ):

 In [changeset:"3342f24ff6f2314c5fc5352aa61c61bd0f43ca75" 3342f24f]:
 {{{
 #!CommitTicketReference repository=""
 revision="3342f24ff6f2314c5fc5352aa61c61bd0f43ca75"
 [1.10.x] Fixed #26807 -- Documented how to replicate SubfieldBase's
 assignment behavior.

 Backport of 518eaf1fa2d86dc1b0ba7adba22b30bcc8f3a497 from master
 }}}

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To 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/061.599f6c1fc42a8b756f3451a4f5c684bc%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #26807: Document how to replicate SubfieldBase behavior of calling to_python on assignment

[Django]

#26807: Document how to replicate SubfieldBase behavior of calling to_python on
assignment
--+
 Reporter:  akx   |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  closed
Component:  Documentation |  Version:  1.8
 Severity:  Normal|   Resolution:  fixed
 Keywords:| Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+

Comment (by Tim Graham ):

 In [changeset:"717aa8843938035602148bd34f078583399967c5" 717aa884]:
 {{{
 #!CommitTicketReference repository=""
 revision="717aa8843938035602148bd34f078583399967c5"
 [1.8.x] Fixed #26807 -- Documented how to replicate SubfieldBase's
 assignment behavior.

 Backport of 518eaf1fa2d86dc1b0ba7adba22b30bcc8f3a497 from master
 }}}

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To 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/061.53e13ab2e5f061e1be72b5f75c1c94b4%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #26807: Document how to replicate SubfieldBase behavior of calling to_python on assignment

[Django]

#26807: Document how to replicate SubfieldBase behavior of calling to_python on
assignment
--+
 Reporter:  akx   |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  closed
Component:  Documentation |  Version:  1.8
 Severity:  Normal|   Resolution:  fixed
 Keywords:| Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+
Changes (by Tim Graham ):

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


Comment:

 In [changeset:"518eaf1fa2d86dc1b0ba7adba22b30bcc8f3a497" 518eaf1f]:
 {{{
 #!CommitTicketReference repository=""
 revision="518eaf1fa2d86dc1b0ba7adba22b30bcc8f3a497"
 Fixed #26807 -- Documented how to replicate SubfieldBase's assignment
 behavior.
 }}}

--
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/061.f9868895007d8acb168f8591262fe3b7%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #26807: Document how to replicate SubfieldBase behavior of calling to_python on assignment

[Django]

#26807: Document how to replicate SubfieldBase behavior of calling to_python on
assignment
--+
 Reporter:  akx   |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  Documentation |  Version:  1.8
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+
Changes (by timgraham):

 * has_patch:  0 => 1


Comment:

 [https://github.com/django/django/pull/7120 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 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/061.722d16d1f4cb18f337a01eee8a57e1ae%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #26807: Document how to replicate SubfieldBase behavior of calling to_python on assignment (was: Custom fields do not call to_python on assignment)

[Django]

#26807: Document how to replicate SubfieldBase behavior of calling to_python on
assignment
--+
 Reporter:  akx   |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  Documentation |  Version:  1.8
 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 timgraham):

 * needs_better_patch:   => 0
 * component:  Database layer (models, ORM) => Documentation
 * needs_tests:   => 0
 * version:  1.9 => 1.8
 * needs_docs:   => 0
 * type:  Uncategorized => Cleanup/optimization
 * stage:  Unreviewed => Accepted


Comment:

 The [https://groups.google.com/d/topic/django-
 developers/0nauqFFwscU/discussion django-developers thread] that proposed
 the removal of `SubfieldBase` says:

  Django provides a metaclass called `SubfieldBase`, which basically means
 that that field will have it's `to_python()` method called whenever a
 value is assigned to the model, including when it is loaded from the
 database. This really is an abuse of `to_python()` whose primary purpose
 is to convert strings from serialisation and forms into the relevant
 python object.

 The deprecation note in the the 1.8 release notes says, "the new approach
 does not call the `to_python()` method on assignment as was the case with
 `SubfieldBase`." We could say that custom fields can copy the `Creator`
 implementation if they require this behavior.

--
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/061.cf4c188e3431d8885c25226b2b5a9f04%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.