Skip to content

chore(deps): relax docstring_parser version to allow 0.16 #203

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

Closed
wants to merge 1 commit into from

Conversation

mieslep
Copy link

@mieslep mieslep commented Jun 11, 2025

Description

The project is 'incompatible' with those that use docstring_parser>0.16 : docstring_parser is effectively pinned at 0.15 (2022-09-05), this change allows latest 0.16 (2024-03-15) which has "general support for Python 3.12".

Related Issues

none

Documentation PR

n/a

Type of Change

  • Other (please describe): dependency update

[Choose one of the above types of changes]

Testing

I've run the following:

  • hatch fmt --linter
  • hatch fmt --formatter
  • hatch test --all

Checklist

  • I have read the CONTRIBUTING document
  • I have added tests that prove my fix is effective or my feature works
  • I have updated the documentation accordingly
  • I have added an appropriate example to the documentation to outline the feature
  • My changes generate no new warnings
  • Any dependent changes have been merged and published

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

@@ -28,7 +28,7 @@ classifiers = [
dependencies = [
"boto3>=1.26.0,<2.0.0",
"botocore>=1.29.0,<2.0.0",
"docstring_parser>=0.15,<0.16.0",
"docstring_parser>=0.15,<0.17.0",
Copy link
Member

Choose a reason for hiding this comment

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

Hi thanks for this and our apologies for the strict pinning, would you mind increasing upper bound to 1.0, though. The intent here was that we wanted to prevent unexpected behavior because of major version bumps. But a max of 0.16 seems like it was simply a bug and I want to avoid another commit in the future when docstring_parser reaches 0.18

@dbschmigelski dbschmigelski mentioned this pull request Jun 17, 2025
7 tasks
@dbschmigelski
Copy link
Member

Closing this PR in favor of #239 as contributors do not have edit access.

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.

2 participants