[Python-Dev] PEP 362: 4th edition (original) (raw)
Nick Coghlan ncoghlan at gmail.com
Tue Jun 19 04:06:40 CEST 2012
- Previous message: [Python-Dev] PEP 362: 4th edition
- Next message: [Python-Dev] PEP 362: 4th edition
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On Tue, Jun 19, 2012 at 12:00 PM, Yury Selivanov <yselivanov.ml at gmail.com> wrote:
On 2012-06-18, at 9:36 PM, Nick Coghlan wrote:
So keep the current copying semantics for Signature objects (i.e. creating new copies of the Parameter objects as well), but call it a shallow copy rather than a deep copy. Make it clear in the documentation that any defaults and annotations are still shared with the underlying callable. So, 'Signature.deepcopy()' -> 'Signature.shallowcopy()'? Or make it private - 'Signature.shallowcopy()'?
I'd just call it Signature.copy :)
You're not doing anything unusual here, just declaring that the list of parameters is a part of the Signature object's state, and thus even a shallow copy shouldn't share the parameter objects.
Cheers, Nick.
-- Nick Coghlan | ncoghlan at gmail.com | Brisbane, Australia
- Previous message: [Python-Dev] PEP 362: 4th edition
- Next message: [Python-Dev] PEP 362: 4th edition
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]