[Python-Dev] RE: [Python-checkins] python/nondist/peps pep-0323.txt, NONE, 1.1 pep-0000.txt, 1.254, 1.255
Guido van Rossum
guido at python.org
Tue Oct 28 12:51:59 EST 2003
More information about the Python-Dev mailing list
Tue Oct 28 12:51:59 EST 2003
- Previous message: [Python-Dev] RE: [Python-checkins] python/nondist/pepspep-0323.txt, NONE, 1.1 pep-0000.txt, 1.254, 1.255
- Next message: [Python-Dev] RE: [Python-checkins] python/nondist/peps pep-0323.txt, NONE, 1.1 pep-0000.txt, 1.254, 1.255
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
> Yes, the use case of __deepcopy__ is indeed quite different (and > to be honest it doesn't appear in my actual experience -- I can "imagine" > some as well as the next man, but they'd be made out of whole cloth:-). > But I was under the impression that you wanted them in PEP 323 too? > Maybe I misunderstood your words. Should I take them out of PEP 323? > In that case somebody else can later PEP that if they want, and I can > basically wash my hands of them -- what do you think? I think it would be better of PEP 323 only did __copy__, so you can remove all traces of __deepcopy__. I don't recall what I said, maybe I wasn't clear. --Guido van Rossum (home page: http://www.python.org/~guido/)
- Previous message: [Python-Dev] RE: [Python-checkins] python/nondist/pepspep-0323.txt, NONE, 1.1 pep-0000.txt, 1.254, 1.255
- Next message: [Python-Dev] RE: [Python-checkins] python/nondist/peps pep-0323.txt, NONE, 1.1 pep-0000.txt, 1.254, 1.255
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Python-Dev mailing list