| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
Sorry, something went wrong.
|
I renamed utility functions for testing to conform with PEP8. Also I added URLs in comments to documentation on COM specifications for developers who may have limited experience with COM and may review or maintain this code in the future. |
Sorry, something went wrong.
There was a problem hiding this comment.
Thank you for the tests!
I only have a slight idea of how COM works, but, they look good to me!
However, I would like to simplify the supporting Python code, though: we don't need to test CPython internal types, or custom descriptors using __get_name__.
Sorry, something went wrong.
|
In #126686, COMError became public, but I would like this test to be backported to 3.13 and 3.12, where COMError remains private. If possible, I would appreciate it if we could merge this as is, and after the backport PR is submitted by the bot, I will prepare a follow-up PR reflecting the fact that COMError is now public. |
Sorry, something went wrong.
There was a problem hiding this comment.
Can we have assertion equality being tested as actual == expected instead of expected == actual? I think we usually do the first form rather than the second one.
Sorry, something went wrong.
There was a problem hiding this comment.
Looks good, thank you!
I don't think it's worth it to reorder assertion arguments, but if you want to do it I won't stop you :)
Sorry, something went wrong.
|
[Edit: I deleted a misguided suggestion] |
Sorry, something went wrong.
|
!buildbot Windows |
Sorry, something went wrong.
|
🤖 New build scheduled with the buildbot fleet by @encukou for commit cc07c44 🤖 The command will test the builders whose names match following regular expression: Windows The builders matched are:
|
Sorry, something went wrong.
|
I don’t have a strong preference for the order of actual == expected or expected == actual. In my native language, Japanese, the equivalent concept is expressed as “予実” (yojitsu), with the characters for “expected” and “actual” written in that order. |
Sorry, something went wrong.
There was a problem hiding this comment.
Let's not burden ourselves with an additional commit. I was just surprised to see it written like that but I won't die from it :) (and since it's a new file anyway, it can have its own style).
By the way, do we need a if __name__ == '__main__' block executing the unittest as is?
Sorry, something went wrong.
|
I added the block. |
Sorry, something went wrong.
|
Ah thank you. I wasn't sure whether it was needed or not. But one build bot is failing I think? |
Sorry, something went wrong.
|
I’m not sure which bot you’re referring to, but all the CI checks have passed, and there’s a green ✔ as well. |
Sorry, something went wrong.
|
!buildbot Windows |
Sorry, something went wrong.
|
🤖 New build scheduled with the buildbot fleet by @picnixz for commit 6c60512 🤖 The command will test the builders whose names match following regular expression: Windows The builders matched are:
|
Sorry, something went wrong.
|
I misunderstood the type of bot running in CI. I’m not sure why the bot is failing. |
Sorry, something went wrong.
|
!buildbot Windows |
Sorry, something went wrong.
|
You don't have write permissions to trigger a build |
Sorry, something went wrong.
|
Sorry, I had to step away yesterday.
No, that's not necessary in new tests. But it doesn't hurt.
The Buildbot tests run after merge, as they can be slow or unreliable. And they run on volunteer-maintained hardware; for security we only run them on reviewed code. |
Sorry, something went wrong.
…s. (pythonGH-126610) (cherry picked from commit 7725c03) Co-authored-by: Jun Komoda <45822440+junkmd@users.noreply.github.com>
…s. (pythonGH-126610) (cherry picked from commit 7725c03) Co-authored-by: Jun Komoda <45822440+junkmd@users.noreply.github.com>
|
GH-127159 is a backport of this pull request to the 3.13 branch. |
Sorry, something went wrong.
|
GH-127160 is a backport of this pull request to the 3.12 branch. |
Sorry, something went wrong.
| Back | FazBrowse Home | New Git URL |
I would like to backport this to 3.12 and 3.13 as well.
This is internal-only, so I don’t think it needs a NEWS entry.