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 視為可安全處理不受信任的資料；當這兩個頁面給出一致的安全性建議時，工作即告完成。