Reviewed: https://review.openstack.org/311858 Committed: https://git.openstack.org/cgit/openstack/neutron-lib/commit/?id=d33b62b0e785d09ae59b14e18fd183bd7d2fb206 Submitter: Jenkins Branch: master
commit d33b62b0e785d09ae59b14e18fd183bd7d2fb206 Author: Brandon Logan <[email protected]> Date: Mon May 2 16:12:59 2016 -0500 Maintain ATTR_NOT_SPECIFIED constant with deepcopy ATTR_NOT_SPECIFIED needs to always remain the same value, but deepcopy will instantiate a new object() if it encounters ATTR_NOT_SPECIFIED. This ensures any deepcopy of a dict that includes ATTR_NOT_SPECIFIED will always return the same instantiation of object. Change-Id: I9685dfff24e36992e90919bd7c2be2cda6c075f3 Closes-Bug: #1577571 Co-Authored-By: Kevin Benton <[email protected]> ** Changed in: neutron Status: In Progress => Fix Released -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1577571 Title: deepcopy of ATTR_NOT_SPECIFIED creates new object Status in neutron: Fix Released Bug description: ATTR_NOT_SPECIFIED is meant to be a constant value, but since it is just an instance of an object(), doing a copy.deepcopy of it will create a new instantiation of object. To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1577571/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : [email protected] Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
