Problem we run into with Django's DateField is that it sends Python date object, which pybossa-client don't know how to handle (because JSON doesn't standardize dates).
We were thinking about implementing in pybossa-client date serialization as proposed on SO, but clients in general may want different serialization. Do you want timezone or not, client should dictate that.
I'm thinking the best solution would be to override Django DateField to_python method and consciously convert it to string (using SO solution).
Problem we run into with Django's DateField is that it sends Python
date
object, whichpybossa-client
don't know how to handle (because JSON doesn't standardize dates).We were thinking about implementing in pybossa-client date serialization as proposed on SO, but clients in general may want different serialization. Do you want timezone or not, client should dictate that.
I'm thinking the best solution would be to override Django DateField
to_python
method and consciously convert it to string (using SO solution).