| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
Sorry, something went wrong.
|
|
||
| See bpo-43916. | ||
| """ | ||
| msg = f"cannot create '{tp.__module__}\.{tp.__name__}' instances" |
There was a problem hiding this comment.
You should use f"xxx\.xxx" or fr"xxx.xxx". Or maybe use re.escape().
Sorry, something went wrong.
There was a problem hiding this comment.
Since these tests are decorated with cpython_only, it should be ok to match the exact string, as produced by Objects/typeobject.c? Just matching the type module/name could in theory generate wrong result; maybe not in practice though.
Sorry, something went wrong.
There was a problem hiding this comment.
What about setting the match pattern depending on what test.support.check_impl_detail() says?
Sorry, something went wrong.
|
Enough nitpicking, you can always enhance the code later ;-) I merged your PR, thanks. I guess that the next step is to modify existing tests to use it. |
Sorry, something went wrong.
|
Backport to 3.10? I guess not. |
Sorry, something went wrong.
It seems like more changes are coming. Once they all landed into main, maybe write a backport to 3.10 PR including all of them at once (git cherry-pick -x all commits in the right order). Or we can leave 3.10 as it is: it's more up to you. |
Sorry, something went wrong.
|
Lets leave 3.10 as it is. |
Sorry, something went wrong.
|
@pablogsal, should we backport this? grep -r disallow_insta Lib/test | wc -l gives me 14 hits on the 3.10 branch, including the recently backported sqlite3 test. |
Sorry, something went wrong.
I would prefer to backport it, yep |
Sorry, something went wrong.
…thonGH-25757). (cherry picked from commit 4f72526) Co-authored-by: Erlend Egeberg Aasland <erlend.aasland@innova.no>
@vstinner: I've opened GH-26885 which is a backport of this PR, GH-26394 (docs for this PR), and GH-26392 (apply this PR to Lib/test). |
Sorry, something went wrong.
| Back | FazBrowse Home | New Git URL |
https://bugs.python.org/issue43988