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 neologix
Recipients neologix, pitrou, python-dev, tshepang, vstinner
Date 2013-05-21.09:53:19
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <CAH_1eM3JTfDSxisC6HJvZYsknMbX-Ot9_VJDBgQSuMX_+AnhpQ@mail.gmail.com>
In-reply-to <1369129605.29.0.548686720549.issue17917@psf.upfronthosting.co.za>
Content
> I don't understand "This is a lot of code churn, but it touches code that is unlikely to be modified otherwise, so I guess it's ok.". What does it mean it's okay when it touches on code that's unlikely to be modified?

The problem with refactoring is that it can complicate further merges
between branches. In this case, the code is nearly never touched, so
it's unlikely to be an issue.
History
Date User Action Args
2013-05-21 09:53:19neologixsetrecipients: + neologix, pitrou, vstinner, tshepang, python-dev
2013-05-21 09:53:19neologixlinkissue17917 messages
2013-05-21 09:53:19neologixcreate