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 gregory.p.smith
Recipients brett.cannon, cstratak, gregory.p.smith, methane, torsava, vstinner, xiang.zhang
Date 2017-05-10.08:06:35
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
Yes, this appears true.

I'm okay with it because I've always considered the make, test, and install as different command invocations.  The package building automation I am aware of tends to do the same.  Our buildbots keep the steps separate.

But we need document this requirement somewhere.

I think if we wanted test and install to accurately figure out if they need to redo the profile build and profiling run, we'd need make to detect that _any_ of its possible profile build+run input files are more recent than the last profiling run.  ugh.
Date User Action Args
2017-05-10 08:06:35gregory.p.smithsetrecipients: + gregory.p.smith, brett.cannon, vstinner, methane, xiang.zhang, cstratak, torsava
2017-05-10 08:06:35gregory.p.smithsetmessageid: <>
2017-05-10 08:06:35gregory.p.smithlinkissue29243 messages
2017-05-10 08:06:35gregory.p.smithcreate