Repository navigation
fix: Set Development Status from component_lifecycle - #391
Open
AlexanderWells-diamond wants to merge 1 commit into
Open
AlexanderWells-diamond wants to merge 1 commit into
AlexanderWells-diamond wants to merge 1 commit into
Conversation
AlexanderWells-diamond
force-pushed
the
fix_development_status_classifier
branch
from
October 1, 2026 10:52
7c8bb6a to
6f7de40
Compare
AlexanderWells-diamond
changed the title
Contributor
Author
|
I believe the tests are failing due to https://docs.python.org/ currently being unreachable with an HTTP 503 error. |
Contributor
Author
|
Tests are now passing as it looks like Python's docs site is back. |
This branch has not been deployed
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
This automatically sets the Python "Development Status" classifier as per the list found here based on the answer to the "component lifecycle" Copier question.
From my understanding this classifier is not required, just a nice to have. So I'm not too worried about the potential for a misalignment between the
component_lifecyclelist of answers resulting in a lack ofDevelopment Status, but I am also open to tweaking the template to always default to "Alpha" status (as it was set to before)