调用 copy.copy 得到深度拷贝的结果！
#11
Comments
2018-11-27
pushed a commit
that referenced
this issue
May 13, 2023
1. Fix issue where a new `gdict` instance was still created even when the value being assigned as a key-value pair was already an instance of `gdict`. #10 2. Fix issue where calling `copy.copy` did not result in a deep copy. #11 3. Add extensive and detailed functionality descriptions to the `gdict` class. 4. Adjust the functionality description of the `deepcopy` method. 5. Refactor (improve) the method of obtaining version information in `setup` by directly extracting it from `package.__doc__`, rather than opening a file. 6. Adjust the classification information of the open-source library on PyPi. 7. Update the README file to provide detailed explanations of the functionality and usage of `gdict`. 1.修复问题：设置键值对时，如果值已经是 `gdict` 实例，仍然会创建新的 `gdict`实例。#10 2.修复问题：调用 `copy.copy` 得到深度拷贝的结果。#11 3.对 `gdict` 类添加了大量的详细的功能描述。 4.调整 `deepcopy` 方法的功能描述。 5.重构（改进） `setup` 中获得版本信息的方案，直接从 `package.__doc__` 中提取，而不再打开文件。 6.调整在PyPi上的开源库分类信息。 7.更新自述文件，详细地讲解 `gdict` 的功能和用法。
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
经分析，确认原因在于
gdict类初始化的逻辑与常规类不同，gdict类初始化过程可以说是一个（不完全的）深度拷贝。而
copy.copy调用过程就是直接创建一个相同类的对象，这样就像如上所述得到深度拷贝的结果。The text was updated successfully, but these errors were encountered: