Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Allow P4 filenames containing spaces #3242

Merged
merged 1 commit into from
Apr 22, 2022
Merged

Conversation

mihaibudiu
Copy link
Contributor

Signed-off-by: Mihai Budiu [email protected]

Fixes #3240
I hope...

@mihaibudiu mihaibudiu requested a review from rst0git April 22, 2022 01:00
Copy link
Member

@rst0git rst0git left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@mihaibudiu mihaibudiu merged commit 4ad859c into p4lang:main Apr 22, 2022
@mihaibudiu mihaibudiu deleted the issue3240 branch April 22, 2022 15:27
@Abe149
Copy link
Contributor

Abe149 commented Apr 24, 2022

Fixing this in C++ is nice, but maybe the Python[3] code should also be fixed, for a “belt and suspenders” type of approach. OTOH, maybe this is a rarely-occurring enough corner case that one fix is enough. 😉

Please see my long comment [with code-and-data tarball attachment] at #3240 (comment) for details about how this does not seem to be an inherent flaw/limitation in/of Python3`s argparse library.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

the C preprocessor is being invoked in such a way that ASCII spaces in pathnames of P4 files are unacceptable
3 participants