-
-
Notifications
You must be signed in to change notification settings - Fork 654
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
Update comtypes to version 1.4.6 #17061
Conversation
WalkthroughThe recent updates involve modifications to the Changes
Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media? TipsChatThere are 3 ways to chat with CodeRabbit:
Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments. CodeRabbit Commands (invoked as PR comments)
Additionally, you can add Documentation and Community
|
Oops, something went wrong! Please try again later. 🐰 💔 |
@coderabbitai you'wrote:
You're erroneously suggesting that this info is part of this pr. |
Tip For best results, initiate chat on the files or code changes. @LeonarddeR, my apologies for the mistake. I incorrectly suggested that the PR includes notes on breaking changes in the Add-on API. Thank you for pointing this out, and I will ensure that this error is not repeated in the future. Learnings added
|
How are these files generated / where are you adding them from? can you please add this to the dev approach and/or docs somewhere |
Any suggestions where I should add this? |
@LeonarddeR either in projectDocs\dev\createDevEnvironment.md or in a separate doc referenced by this |
Actually, probably |
That file reads:
I wonder whether we should reconsider this position for two reasons:
|
Note that you suggested this in #15522 (comment), but then @lukaszgo1 pointed out in #15522 (review) that Server 2019 contained an outdated version. However, appveyor is on server 2022 now. |
See test results for failed build of commit cfb74ff2c6 |
@LeonarddeR - you are right, as far as we are aware the UIA interface should be fairly stable now. Lets use AppVeyor now |
Can you please fix up the git excludes and ruff format? https://results.pre-commit.ci/run/github/45885732/1724844260.36kQ5pFwQpmFQXxO-uMqNw |
Link to issue number:
None
Summary of the issue:
There have been many updates to Comtypes since last time we updated.
Description of user facing changes
None
Description of development approach
Testing strategy:
Should be tested during daily use.
Known issues with pull request:
None known
Code Review Checklist:
Summary by CodeRabbit
New Features
Bug Fixes
Documentation