Skip to content
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 and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Traceback doesn't run back all the way #48347

Closed
pinkisntwell mannequin opened this issue Oct 10, 2008 · 3 comments
Closed

Traceback doesn't run back all the way #48347

pinkisntwell mannequin opened this issue Oct 10, 2008 · 3 comments
Labels
type-bug An unexpected behavior, bug, or error

Comments

@pinkisntwell
Copy link
Mannequin

pinkisntwell mannequin commented Oct 10, 2008

BPO 4097
Nosy @vstinner, @florentx

Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.

Show more details

GitHub fields:

assignee = None
closed_at = <Date 2009-11-26.01:54:20.595>
created_at = <Date 2008-10-10.08:53:37.547>
labels = ['type-bug']
title = "Traceback doesn't run back all the way"
updated_at = <Date 2009-11-26.01:54:20.585>
user = 'https://bugs.python.org/pinkisntwell'

bugs.python.org fields:

activity = <Date 2009-11-26.01:54:20.585>
actor = 'benjamin.peterson'
assignee = 'none'
closed = True
closed_date = <Date 2009-11-26.01:54:20.595>
closer = 'benjamin.peterson'
components = ['None']
creation = <Date 2008-10-10.08:53:37.547>
creator = 'pinkisntwell'
dependencies = []
files = []
hgrepos = []
issue_num = 4097
keywords = []
message_count = 3.0
messages = ['74621', '74629', '95722']
nosy_count = 3.0
nosy_names = ['vstinner', 'pinkisntwell', 'flox']
pr_nums = []
priority = 'normal'
resolution = 'duplicate'
stage = None
status = 'closed'
superseder = None
type = 'behavior'
url = 'https://bugs.python.org/issue4097'
versions = ['Python 2.6']

@pinkisntwell
Copy link
Mannequin Author

pinkisntwell mannequin commented Oct 10, 2008

I just got an exception and the traceback wouldn't go all the
way to the statement that threw the exception. I found that out
by using the debugger.

Contrast the traceback:

http://tinyurl.com/5xglde

with the debugger output (notice the arrow pointing to the last
statement the traceback showed and how the execution went on
beyond it):

http://tinyurl.com/3fjgrl

@pinkisntwell pinkisntwell mannequin added the type-bug An unexpected behavior, bug, or error label Oct 10, 2008
@vstinner
Copy link
Member

Can you write an example to reproduce your traceback? You don't give
enough informations to see what is the type of your variable, which
modules are used, etc.

@florentx
Copy link
Mannequin

florentx mannequin commented Nov 25, 2009

It looks similar to bpo-7378, but the latter has more details.

Close as duplicate?

@ezio-melotti ezio-melotti transferred this issue from another repository Apr 10, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type-bug An unexpected behavior, bug, or error
Projects
None yet
Development

No branches or pull requests

2 participants