[issue34871] test_site fails if run after test_inspect

2018-10-04 Thread Yury Selivanov
Yury Selivanov added the comment: Thank you Inada-san for taking care of this. -- resolution: -> fixed stage: patch review -> resolved status: open -> closed ___ Python tracker

[issue34871] test_site fails if run after test_inspect

2018-10-04 Thread Yury Selivanov
Yury Selivanov added the comment: New changeset 476c294f260ebe1b44157a168c3dfa4a43724ce3 by Yury Selivanov (Miss Islington (bot)) in branch '3.7': bpo-34871: inspect: Don't pollute sys.modules (GH-9696) (#9701) https://github.com/python/cpython/commit/476c294f260ebe1b44157a168c3dfa4a43724ce3

[issue34871] test_site fails if run after test_inspect

2018-10-04 Thread Yury Selivanov
Yury Selivanov added the comment: New changeset 70a083bc46aea84e3b3ffca2c10c295917a98fec by Yury Selivanov (Miss Islington (bot)) in branch '3.6': bpo-34871: inspect: Don't pollute sys.modules (GH-9696) (GH-9702)

[issue34871] test_site fails if run after test_inspect

2018-10-04 Thread miss-islington
Change by miss-islington : -- pull_requests: +9087 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue34871] test_site fails if run after test_inspect

2018-10-04 Thread miss-islington
Change by miss-islington : -- pull_requests: +9086 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue34871] test_site fails if run after test_inspect

2018-10-04 Thread miss-islington
miss-islington added the comment: New changeset 6f85b826b527e240551613aeec3118a5469e3a33 by Miss Islington (bot) (INADA Naoki) in branch 'master': bpo-34871: inspect: Don't pollute sys.modules (GH-9696) https://github.com/python/cpython/commit/6f85b826b527e240551613aeec3118a5469e3a33

[issue34871] test_site fails if run after test_inspect

2018-10-04 Thread miss-islington
miss-islington added the comment: New changeset c57eb9a336391dc22aa29e9db592fa06d7fb7101 by Miss Islington (bot) (Chih-Hsuan Yen) in branch 'master': bpo-34871: Fix two typos in test_inspect.py (GH-9698) https://github.com/python/cpython/commit/c57eb9a336391dc22aa29e9db592fa06d7fb7101

[issue34871] test_site fails if run after test_inspect

2018-10-04 Thread Chih-Hsuan Yen
Change by Chih-Hsuan Yen : -- pull_requests: +9084 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue34871] test_site fails if run after test_inspect

2018-10-04 Thread INADA Naoki
Change by INADA Naoki : -- keywords: +patch pull_requests: +9083 stage: -> patch review ___ Python tracker ___ ___

[issue34871] test_site fails if run after test_inspect

2018-10-02 Thread Serhiy Storchaka
Change by Serhiy Storchaka : -- nosy: +yselivanov ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue34871] test_site fails if run after test_inspect

2018-10-02 Thread Chih-Hsuan Yen
Chih-Hsuan Yen added the comment: Thanks very much for the test.bisect hint! After some more trials, I guess it's an issue in the `inspect` module rather than the newly-added test in test_site. Here's an example script: import inspect import sys import _testcapi builtin =

[issue34871] test_site fails if run after test_inspect

2018-10-02 Thread Karthikeyan Singaravelan
Karthikeyan Singaravelan added the comment: The failing test was added with d4c76d960b8b286b75c933780416ace9cda682fd commit d4c76d960b8b286b75c933780416ace9cda682fd Author: INADA Naoki Date: Mon Oct 1 21:10:37 2018 +0900 bpo-30167: Add test for module.__cached__ is None (GH-7617)

[issue34871] test_site fails if run after test_inspect

2018-10-02 Thread Karthikeyan Singaravelan
Change by Karthikeyan Singaravelan : -- nosy: +xtreak ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue34871] test_site fails if run after test_inspect

2018-10-02 Thread Chih-Hsuan Yen
New submission from Chih-Hsuan Yen : $ ./python -m test.regrtest test_inspect test_site Run tests sequentially 0:00:00 load avg: 0.03 [1/2] test_inspect 0:00:00 load avg: 0.03 [2/2] test_site test test_site failed -- Traceback (most recent call last): File

[issue34871] test_site fails if run after test_inspect

2018-10-02 Thread STINNER Victor
STINNER Victor added the comment: You can try to limit the number of tests needed to reproduce the bug using: ./python -m test.bisect -n 5 test_inspect test_site -- nosy: +vstinner ___ Python tracker