bpo-23882: Doc: Clarify unittest discovery document by methane · Pull Request #21560 · python/cpython (original) (raw)
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 andprivacy statement. We’ll occasionally send you account related emails.
Already on GitHub?Sign in to your account
Conversation4 Commits1 Checks0 Files changed
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.Learn more about bidirectional Unicode characters
[ Show hidden characters]({{ revealButtonHref }})
Unittest discovery support namespace package as start
directory. But it doesn't find namespace package in
the start directory automatically.
Otherwise, unittest discovery search into unexpected
directories like vendor/ or node_modules/.
https://bugs.python.org/issue23882
Unittest discovery support namespace package as start directory. But it doesn't find namespace package in the start directory automatically.
Otherwise, unittest discovery search into unexpected
directories like vendor/ or node_modules/.
Thanks @methane for the PR 🌮🎉.. I'm working now to backport this PR to: 3.7, 3.8, 3.9.
🐍🍒⛏🤖
miss-islington pushed a commit to miss-islington/cpython that referenced this pull request
Unittest discovery support namespace package as start directory. But it doesn't find namespace package in the start directory automatically.
Otherwise, unittest discovery search into unexpected
directories like vendor/ or node_modules/.
(cherry picked from commit 5a4aa4c)
Co-authored-by: Inada Naoki songofacandy@gmail.com
miss-islington pushed a commit to miss-islington/cpython that referenced this pull request
Unittest discovery support namespace package as start directory. But it doesn't find namespace package in the start directory automatically.
Otherwise, unittest discovery search into unexpected
directories like vendor/ or node_modules/.
(cherry picked from commit 5a4aa4c)
Co-authored-by: Inada Naoki songofacandy@gmail.com
miss-islington pushed a commit to miss-islington/cpython that referenced this pull request
Unittest discovery support namespace package as start directory. But it doesn't find namespace package in the start directory automatically.
Otherwise, unittest discovery search into unexpected
directories like vendor/ or node_modules/.
(cherry picked from commit 5a4aa4c)
Co-authored-by: Inada Naoki songofacandy@gmail.com
miss-islington added a commit that referenced this pull request
Unittest discovery support namespace package as start directory. But it doesn't find namespace package in the start directory automatically.
Otherwise, unittest discovery search into unexpected
directories like vendor/ or node_modules/.
(cherry picked from commit 5a4aa4c)
Co-authored-by: Inada Naoki songofacandy@gmail.com
miss-islington added a commit that referenced this pull request
Unittest discovery support namespace package as start directory. But it doesn't find namespace package in the start directory automatically.
Otherwise, unittest discovery search into unexpected
directories like vendor/ or node_modules/.
(cherry picked from commit 5a4aa4c)
Co-authored-by: Inada Naoki songofacandy@gmail.com
adorilson pushed a commit to adorilson/cpython that referenced this pull request
Unittest discovery support namespace package as start directory. But it doesn't find namespace package in the start directory automatically.
Otherwise, unittest discovery search into unexpected
directories like vendor/ or node_modules/.