The pickle module documentation makes confusing statements about secure alternatives

Documentation

The pickle module states that the xmlrpc marshaling API should be used if the users desire a safe alternative to unpickling untrusted data:

https://docs.python.org/3.14/library/pickle.html:

As our examples shows, you have to be careful with what you allow to be unpickled. Therefore if security is a concern, you may want to consider alternatives such as the marshalling API in xmlrpc.client or third-party solutions.

However, the xmlrpc module has right at the top a warning that says the following:

https://docs.python.org/3.14/library/xmlrpc.client.html#module-xmlrpc.client:

The xmlrpc.client module is not secure against maliciously constructed data. If you need to parse untrusted or unauthenticated data see XML vulnerabilities.

These two statements contradict each other and could lead users to falsely believe that they are using a safe alternative.

从 pickle 模块文档中关于 xmlrpc.client 的表述开始，并将其与 xmlrpc.client 文档顶部的安全警告进行比较。修订其中相互冲突的指导，避免用户将 xmlrpc.client 视为可安全处理不可信数据；当这两个页面给出一致的安全建议时，工作即告完成。