Unicode Problems

[nexttonever]

unicode is not good for some class, like Decimal, unicode will convert it to "Decimal xxx"，but not pure number string. This could cause error. However it can be solved by manually convert that variable to str.
But sometimes it cannot be avoided. For example,
delete just one field:
{
"id": 1,
"fieldToBeDelete": {"set": None}
}

"None" will be serialized to "None" but not null, and Solr server will accept it as a new value，rather than to delete this field. This may be terrible.

Can you fix this problem? or moreover provide a way to replace 'unicode' by some option?

[search5]

Thank you for reporting this. As of solrpy 2.0.8, this has been fully resolved.

• None values are now correctly serialized: in the JSON update path they become null, and in the XML path they produce null="true" attributes. {'set': None} in an atomic update will properly delete the field as expected.
• Decimal values are handled by both update paths: the JSON encoder converts them to native floats, and the XML serializer converts them via str() to produce clean numeric strings like '3.14'.
• The legacy unicode() issue no longer applies — solrpy 2.x requires Python 3.10+ and uses a unified serialize_value() helper for all type conversions across add(), add_many(), atomic_update(), and their async counterparts.