Skip to content

Lint fixes#193

Open
shreyasvinaya wants to merge 2 commits intomainfrom
lint-az-py-fixes
Open

Lint fixes#193
shreyasvinaya wants to merge 2 commits intomainfrom
lint-az-py-fixes

Conversation

@shreyasvinaya
Copy link
Copy Markdown
Collaborator

@shreyasvinaya shreyasvinaya commented Apr 6, 2026

Description

Fix #(issue)

fixes a bunch of linting, typecheck and ports az.py to the new cache system
to be merged in after #192

NOTE: the large PR size is due to a uv.lock file that is required by CI to install correct versions of the packages (it accounts for 5500+ lines)
another uv.lock update changes ~800 lines of code to update versions of packages to the latest versions

Type of change

Please check the option that is related to your PR.

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to not work as expected)
    • In this case, we recommend to discuss your modification on GitHub issues before creating the PR
  • Documentations (modification for documents)

Checklist

  • I have performed a self-review of my own code
  • I have commented my code, particularly in hard-to-understand areas
  • I have made corresponding changes to the documentation
  • I have added tests that prove my fix is effective or that my feature works
  • New unit tests pass locally with my changes
  • I have checked my code and corrected any misspellings

Copy link
Copy Markdown
Contributor

@rbharath rbharath left a comment

Choose a reason for hiding this comment

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

Please separate into two PRs. One for lint, one for az. Don't have different changes in same PR

@shreyasvinaya
Copy link
Copy Markdown
Collaborator Author

Split done: #193 now contains only the lint/docs-import cleanup, and the AZ changes were moved to #196.

@shreyasvinaya shreyasvinaya changed the title Lint az py fixes Lint fixes Apr 13, 2026
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