A RetroSearch Logo

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Search Query:

Showing content from https://mail.python.org/pipermail/python-dev/2003-October/039717.html below:

[Python-checkins] python/nondist/peps pep-0323.txt, NONE, 1.1 pep-0000.txt, 1.254, 1.255

[Python-Dev] RE: [Python-checkins] python/nondist/peps pep-0323.txt, NONE, 1.1 pep-0000.txt, 1.254, 1.255Guido van Rossum guido at python.org
Tue Oct 28 12:51:59 EST 2003
> 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/)

More information about the Python-Dev mailing list

RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4