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

Spaces missing in Requirement string representation #654

Open
avylove opened this issue Jan 7, 2023 · 0 comments
Open

Spaces missing in Requirement string representation #654

avylove opened this issue Jan 7, 2023 · 0 comments

Comments

@avylove
Copy link

avylove commented Jan 7, 2023

Given the example, Requirement('enlighten >= 1.10.2')
The string output of this is 'enlighten>=1.10.2' rather than 'enlighten >= 1.10.2'

I believe the lack of spaces between the specifier operators and versions as well as the requirement components reduces readability.

While the lack of spaces could be considered a stylistic choice, there's no option to modify it without additional code and it's inconsistent with the examples in PEP 440 and PEP 508. And while this isn't Python code, it's not consistent with the recommendation in PEP 8 that binary operators are surrounded by single spaces.

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

No branches or pull requests

3 participants