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 nascheme
Recipients nascheme
Date 2019-07-30.23:23:49
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1564529029.65.0.599090827857.issue37725@roundup.psfhosted.org>
In-reply-to
Content
I find it annoying and surprising that "make clean" does not remove the PGO data.  If you change a source file, running "make clean" and "make" should result in a newly built executable, IMHO.  As it is now, you usually get a confusing build failure (PGO data is out of date).

The fix is fairly easy.  Make a new target that does what "clean" currently does.  Have the PGO build call that when it needs to preserve the PGO data.  Introduce a new "clean" target that does what the old clean did and also removes the PGO data.

Changing the build system is fraught with danger but I think this is a fairly safe change.  The current behavior is quite annoying, IMHO.
History
Date User Action Args
2019-07-30 23:23:49naschemesetrecipients: + nascheme
2019-07-30 23:23:49naschemesetmessageid: <1564529029.65.0.599090827857.issue37725@roundup.psfhosted.org>
2019-07-30 23:23:49naschemelinkissue37725 messages
2019-07-30 23:23:49naschemecreate