Skip to content

lazy import of doctest in pdb breaks debugging if the environment makes doctest unimportable #295

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.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Closed
pytestbot opened this issue Apr 11, 2013 · 4 comments
Closed

lazy import of doctest in pdb breaks debugging if the environment makes doctest unimportable #295

pytestbot opened this issue Apr 11, 2013 · 4 comments
Labels
good first issue easy issue that is friendly to new contributor type: enhancement new feature or API change, should be merged into features branch

Comments

@pytestbot
Copy link
Contributor

Originally reported by: Ronny Pfannschmidt (BitBucket: RonnyPfannschmidt, GitHub: RonnyPfannschmidt)

happens when debugging a half broken pypy
@pytestbot
Copy link
Contributor Author

Original comment by Ronny Pfannschmidt (BitBucket: RonnyPfannschmidt, GitHub: RonnyPfannschmidt):

Issue #296 was marked as a duplicate of this issue.

@pytestbot
Copy link
Contributor Author

Original comment by holger krekel (BitBucket: hpk42, GitHub: hpk42):

i'd like to have more information on this issue and put it to invalid until then. We need something to reproduce.

@pytestbot
Copy link
Contributor Author

Original comment by Ronny Pfannschmidt (BitBucket: RonnyPfannschmidt, GitHub: RonnyPfannschmidt):

to recreate that doctest import problem
create test.py and doctest.py containing

#!python

raise

run pytest

see internal-error in pdb

@pytestbot
Copy link
Contributor Author

Original comment by holger krekel (BitBucket: hpk42, GitHub: hpk42):

i consider it an enhancement to treat this edge case. Breaking import of standard lib modules is bound to lead to bad effects in general.

@pytestbot pytestbot added the type: enhancement new feature or API change, should be merged into features branch label Jun 15, 2015
@pytestbot pytestbot mentioned this issue Jun 15, 2015
Closed
@RonnyPfannschmidt RonnyPfannschmidt added the good first issue easy issue that is friendly to new contributor label Jul 25, 2015
@pytestbot pytestbot mentioned this issue May 15, 2018
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
good first issue easy issue that is friendly to new contributor type: enhancement new feature or API change, should be merged into features branch
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@RonnyPfannschmidt @pytestbot