Should `print_debug_info` also include the commit hash of the latest commit?

[oddbookworm]

I was thinking it might be worthwhile to include the commit hash of the most recent commit in the build for debugging purposes

[robotsnh]

I think that it's a good idea, but would it be the most recent commit from the git repo or for the current build that you're using?

[oddbookworm]

I think that it's a good idea, but would it be the most recent commit from the git repo or for the current build that you're using?

The build. It would be pretty useless to include something that's not part of the build that's currently being run

[ankith26]

+1 from my side for this.

The pygame.version.rev has been an empty string since ages. I believe in the pre-git days of OG pygame this attribute was exactly that. I propose that this attribute maps to the hash of latest commit at build time (but only for "odd patch" AKA "dev" releases, for pre releases and full releases this field could be empty). I think tracking branch name along with this is also good for readability.

Another related attribute I would like to track is "whether the build was CI generated or not" because this mainly affects what kind of dependencies are used during the build.