[issue38433] 2.7.17rc1 tcl/tk version regression on Windows

Steve Dower added the comment: Confirmed that it was a failed clean/rebuild on my build machine. The current build for 2.7.17 has the newer version. -- resolution: -> not a bug stage: -> resolved status: open -> closed ___ Python tracker

[issue38433] 2.7.17rc1 tcl/tk version regression on Windows

Steve Dower added the comment: Strange, I definitely cleaned up the externals before building 2.7.17rc1, so not sure how it ended up with the previous one. I'll double-check later today on my build machine, but there shouldn't have to be any code changes to deal with this. -- _

[issue38433] 2.7.17rc1 tcl/tk version regression on Windows

Zachary Ware added the comment: Since 8.5.19 is the version specified in the build config, that really ought to be the version we ship. I would guess that it just didn't get rebuilt when Steve built the installer for 2.7.17rc1; should just be a matter of making sure it does for the real thi

[issue38433] 2.7.17rc1 tcl/tk version regression on Windows

Benjamin Peterson added the comment: Unless this actually regresses functionality, it doesn't seem like this needs to block the release. -- ___ Python tracker ___ ___

[issue38433] 2.7.17rc1 tcl/tk version regression on Windows

Ned Deily added the comment: What's the status of this release blocker? Is there something that needs to be done for 2.7.17final which is imminent? -- nosy: +ned.deily ___ Python tracker __

[issue38433] 2.7.17rc1 tcl/tk version regression on Windows

New submission from Terry J. Reedy : In my current 2.7.16+ Windows 10-64 repository build, and on at least one 8.1-64 buildbot, the tcl/tk version is 8.5.19 >>> tk.Tk().tk.call('info', 'patchlevel') '8.5.19' In my installed 2.7.17rc1, it is the older 8.5.15. It would seem to me that we shoul