[mypyc] Derive .c file name from full module name if using multi_file #19278
+1
−1
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Don't shorten the module name prefixes, so that the names of output files are more predictable. This can help if integrating with build systems, and it arguably also makes it easier to inspect the output manually. Now the file name could be `__native_pkg___mod.c` instead of `__native_mod.c` for the module `pkg.mod`.
jhance
approved these changes
Jun 11, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Don't shorten the module name prefixes, so that the names of output files are more predictable. This can help if integrating with build systems, and it arguably also makes it easier to inspect the output manually.
Now the file name could be
__native_pkg___mod.cinstead of__native_mod.cfor the modulepkg.mod.