fix(examples/gccflags): Bytes/String mismatch when parsing GCC output on Python3 #174
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Context
When running the
matrixmultiply.cpporraytracer.cppon Python 3.12-3.13 (tested on 3.12.3, 3.13.3 and 3.13.7), some parts of the GCC flags extraction and compilation parsing fail because of type differences between bytes and string types.These differences caused
TypeError: cannot use a string pattern on a bytes-like objectto get thrown.Changes
--version,--help=params, and--help=optimizersTesting
Reran the examples like normal using new virtual environments running on Python 3.12.3, 3.13.3 and 3.13.7