This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author p-ganssle
Recipients asvetlov, eli.bendersky, gphemsley, mdk, p-ganssle, scoder, thatiparthy
Date 2017-12-28.21:48:48
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1514497728.85.0.213398074469.issue32424@psf.upfronthosting.co.za>
In-reply-to
Content
> I mean dropping `.copy()` breaks not only compatibility between pure python versions but also between pypy releases and pypy/CPython code.
That's why I suggest to keep `.copy()` as an alias for `__copy__()`.

If the main issue is that pypy users have been using this, can't pypy just keep an alias for `copy` around, possibly with a DeprecationWarning?
History
Date User Action Args
2017-12-28 21:48:48p-gansslesetrecipients: + p-ganssle, scoder, eli.bendersky, asvetlov, thatiparthy, mdk, gphemsley
2017-12-28 21:48:48p-gansslesetmessageid: <1514497728.85.0.213398074469.issue32424@psf.upfronthosting.co.za>
2017-12-28 21:48:48p-gansslelinkissue32424 messages
2017-12-28 21:48:48p-gansslecreate