Changes between Initial Version and Version 1 of Ticket #14638, comment 13


Ignore:
Timestamp:
Jul 10, 2014, 10:12:22 AM (10 years ago)
Author:
ANUBHAV JOSHI

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #14638, comment 13

    initial v1  
    55I know that lines haven't been changed, but I felt that this way of representation cleared everything. Whatever the doubt was, it was about the two different usages of `to_python` which is surely mentioned under proper headings now, so I don't think anything else is required.
    66
    7 At max, we can change the link `See converting-database-values-to-python-objects for usage.` to `See converting-database-values-to-python-objects for various usages.` and line `If your custom field needs the to_python method to be called when it is created, you should be using The SubfieldBase metaclass mentioned earlier.` to `If your custom field needs the to_python method to be called everytime it is created along with its usual usage, you should be using The SubfieldBase metaclass mentioned earlier.`
     7At max, we can change the link
     8{{{
     9See converting-database-values-to-python-objects for usage.
     10}}}
     11to
     12{{{
     13See converting-database-values-to-python-objects for various usages.
     14}}}
     15
     16and
     17{{{
     18If your custom field needs the to_python method to be called when it is created, you should be using The SubfieldBase metaclass mentioned earlier.
     19}}}
     20to
     21{{{
     22If your custom field needs the to_python method to be called everytime it is created along with its usual usage, you should be using The SubfieldBase metaclass mentioned earlier.
     23}}}
Back to Top