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 vstinner
Recipients methane, serhiy.storchaka, vstinner
Date 2017-02-10.17:13:32
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <CAMpsgwZ4Q-UjifxkcQC5uwBF5f-qBqd4Y8qRYU2rW9yK96SYNQ@mail.gmail.com>
In-reply-to <1486739059.72.0.128352944654.issue29524@psf.upfronthosting.co.za>
Content
Serhiy Storchaka added the comment:
> I would delay pushing this change until CPython repository be converted to Git. I heard Git better supports moving a code between files. And perhaps it might be easier to do this change by several commits -- separately moving a code from different files.

Mercurial requires to use "hg cp file1.c file2.c" to keep file1
history in file2.

Git doesn't care. It is "smarter" (more convenient?). It uses an
heuristic to automatically detect when code is moved between files.

The migration to GitHub is ongoing, we are no more able to push to
Mercurial anyway :-D

Any remark about call.c content itself? Does it look good to you?
History
Date User Action Args
2017-02-10 17:13:32vstinnersetrecipients: + vstinner, methane, serhiy.storchaka
2017-02-10 17:13:32vstinnerlinkissue29524 messages
2017-02-10 17:13:32vstinnercreate