Skip to content

Further comply with PEP8 naming #3231

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.

Sign up for GitHub

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

Jump to bottom
Open
stefan6419846 opened this issue Apr 1, 2025 · 0 comments
Open

Further comply with PEP8 naming #3231

stefan6419846 opened this issue Apr 1, 2025 · 0 comments
Labels
is-maintenance Anything that is just internal: Simplifying code, syntax changes, updating docs, speed improvements

Comments

@stefan6419846
Copy link
Collaborator

Although we did quite some changes for PEP8 compatibility in the past, we still have some cases which are not compliant which should be changed (if necessary, with a deprecation period).

For this, we might start with enabling rule N806 for ruff. Nevertheless, automated analysis still seems to not catch all cases like PdfReader.xref_objStm for some reason.
@stefan6419846 stefan6419846 added the is-maintenance Anything that is just internal: Simplifying code, syntax changes, updating docs, speed improvements label Apr 1, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
is-maintenance Anything that is just internal: Simplifying code, syntax changes, updating docs, speed improvements
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@stefan6419846