This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

classification
Title: test_pydoc fails if build is in sub-directory
Type: behavior Stage: resolved
Components: Tests Versions: Python 3.6
process
Status: closed Resolution: duplicate
Dependencies: Superseder: test_pydoc fails when run directly
View: 31028
Assigned To: r.david.murray Nosy List: nascheme, r.david.murray
Priority: high Keywords:

Created on 2016-12-08 19:10 by nascheme, last changed 2022-04-11 14:58 by admin. This issue is now closed.

Files
File name Uploaded Description Edit
test_pydoc_fix.txt nascheme, 2016-12-08 19:10 review
Pull Requests
URL Status Linked Edit
PR 2043 closed nascheme, 2017-06-09 21:44
Messages (2)
msg282728 - (view) Author: Neil Schemenauer (nascheme) * (Python committer) Date: 2016-12-08 19:10
test_pydoc is failing for me for 3.6rc1.  I build in a sub-directory, e.g. Python-3.6.0rc1/build-opt.  The root of the issue is that pydoc getdocloc() is broken.  It cannot build 'basedir' as it does and assume that is the location of standard modules.  Fixing that is tricky though, I will open a separate issue for that.

For this issue, I think the test_mixed_case_module_names_are_lower_cased() function needs to be fixed to handle that case that get_pydoc_link() returns None.  I.e. it thinks that the module is not a standard module and so returns no link.

Attached is a patch.  It is trivial and I think should go into 3.6.
msg305670 - (view) Author: Neil Schemenauer (nascheme) * (Python committer) Date: 2017-11-06 19:31
Pretty sure the fix for bug 31028 also fixed this.  Closing.
History
Date User Action Args
2022-04-11 14:58:40adminsetgithub: 73093
2017-11-06 19:31:42naschemesetstatus: open -> closed
superseder: test_pydoc fails when run directly
messages: + msg305670

resolution: duplicate
stage: patch review -> resolved
2017-06-09 21:44:34naschemesetpull_requests: + pull_request2104
2016-12-08 19:10:18naschemecreate