➜

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-07.21:49:24
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <CAMpsgwZ+sySP=7Mx9A4W_s+zO4oGGv3kx7Rc2HCahyZhaHBLjg@mail.gmail.com>
In-reply-to <1486495877.89.0.337883087198.issue29465@psf.upfronthosting.co.za>
Content 
Serhiy Storchaka added the comment:
> Isn't the Python directory more appropriate place for call.c?

I moved code from other .c files in Objects/, so for me it seems more
natural to add the code in Objects/ as well. It seems like most of the
code in Python/ is not "aware" of types defined in Objects/. But I
don't have a strong opinion on the right directory.

Objects/call.c is 1500 lines long. IMHO the code became big enough to
justify to move it to a new file ;-)
History
Date User Action Args
2017-02-07 21:49:25vstinnersetrecipients: + vstinner, methane, serhiy.storchaka
2017-02-07 21:49:25vstinnerlinkissue29465 messages
2017-02-07 21:49:24vstinnercreate