starred/netbox
1
0
Fork 0
mirror of https://github.com/netbox-community/netbox.git synced 2026-01-11 21:10:29 +01:00
Code Issues 273 Packages Projects Releases 10 Wiki Activity

Create pyproject.toml to define linter rules #6950

New Issue
Closed
opened 2025-12-29 19:47:07 +01:00 by adam · 1 comment
adam commented 2025-12-29 19:47:07 +01:00
Owner
Copy Link

Originally created by @jeremystretch on GitHub (Sep 8, 2022).

Originally assigned to: @jsenecal on GitHub.

Proposed Changes

A proposal was raised during today's maintainers' meeting to introduce a pyproject.toml (see PEP 518) file to define the linting rules used in the project. We currently have a pre-commit hook which (among other things) runs pycodestyle with a few arguments to control the rules being applied. The goal here is to document these rules for discovery by a contributor's IDE.

Justification

Lowers development friction for contributors using different IDEs and tool sets.

Originally created by @jeremystretch on GitHub (Sep 8, 2022). Originally assigned to: @jsenecal on GitHub. ### Proposed Changes A proposal was raised during today's maintainers' meeting to introduce a `pyproject.toml` (see [PEP 518](https://peps.python.org/pep-0518/)) file to define the linting rules used in the project. We currently have a pre-commit hook which (among other things) runs `pycodestyle` with a few arguments to control the rules being applied. The goal here is to document these rules for discovery by a contributor's IDE. ### Justification Lowers development friction for contributors using different IDEs and tool sets.
adam added the status: acceptedtype: housekeeping labels 2025-12-29 19:47:07 +01:00
adam closed this issue 2025-12-29 19:47:07 +01:00
adam commented 2025-12-29 19:47:07 +01:00
Author
Owner
Copy Link

@jsenecal commented on GitHub (Sep 9, 2022):

Turns out that pycodestyle rejected the idea of supporting pyproject.toml file for configuration as noted in this pinned issue (Thanks Jeremy)

This may end up bigger than expected if we have to move to something else?

@jsenecal commented on GitHub (Sep 9, 2022): Turns out that pycodestyle rejected the idea of supporting pyproject.toml file for configuration as noted in [this pinned issue](https://github.com/PyCQA/pycodestyle/issues/813) (Thanks Jeremy) This may end up bigger than expected if we have to move to something else?
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
beta
breaking change
complexity: high
complexity: low
complexity: medium
needs milestone
netbox
pending closure
plugin candidate
pull-request
Mirrored from GitHub Pull Request
 severity: high
severity: low
severity: medium
status: accepted
status: backlog
status: blocked
status: duplicate
status: needs owner
status: needs triage
status: revisions needed
status: under review
topic: GraphQL
topic: Internationalization
topic: OpenAPI
topic: UI/UX
topic: cabling
topic: event rules
topic: htmx navigation
topic: industrialization
topic: migrations
topic: plugins
topic: scripts
topic: templating
topic: testing
type: bug
type: deprecation
type: documentation
type: feature
type: housekeeping
type: translation
No Label status: accepted type: housekeeping
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
adam
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/netbox#6950
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?