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 db3l
Recipients db3l, paul.moore, steve.dower, tim.golden, zach.ware
Date 2021-04-02.21:03:02
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1617397382.95.0.866628947431.issue43709@roundup.psfhosted.org>
In-reply-to
Content
Something like this is a quick 'n dirty minimal fix - at least it seems to solve the problem that arose in issue #27129 on the Win10 buildbot:

--- a/Tools/buildbot/clean.bat
+++ b/Tools/buildbot/clean.bat
@@ -11,6 +11,8 @@ call "%pcbuild%\build.bat" -t Clean -k -d %*
 
 echo Deleting .pyc/.pyo files ...
 del /s "%root%\Lib\*.pyc" "%root%\Lib\*.pyo"
+del /s "%root%\Tools\*.pyc" "%root%\Tools\*.pyo"
+del /s "%root%\Parser\*.pyc" "%root%\Parser\*.pyo"
 
 echo Deleting test leftovers ...
 rmdir /s /q "%root%\build"

but since this only covers the buildbot script, someone working within the regular VS IDE and just using the clean target of the projects could presumably run into the same issue.  Or is there some other way to fully clean a working tree from within the IDE?  Not sure how important that is to address in any event.
History
Date User Action Args
2021-04-02 21:03:02db3lsetrecipients: + db3l, paul.moore, tim.golden, zach.ware, steve.dower
2021-04-02 21:03:02db3lsetmessageid: <1617397382.95.0.866628947431.issue43709@roundup.psfhosted.org>
2021-04-02 21:03:02db3llinkissue43709 messages
2021-04-02 21:03:02db3lcreate