[issue33065] IDLE debugger: problem importing user created module

[ppperry]

Change by ppperry :


--
nosy: +ppperry

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue33065] IDLE debugger: problem importing user created module

[Brett Cannon]

Brett Cannon  added the comment:

Without knowing the exact Python version it's hard to tell as line 59 changed 
between Python 3.5 and where Python 3.6 is now (FYI, the line as it currently 
sits in Python 3.6 is 
https://github.com/python/cpython/blob/e98e3385f2acfc6d98f70f8e66c96b752d003b8f/Lib/importlib/_bootstrap.py#L59).
 But the double-reporting of the same line is a bit odd.

The best I can think of is that IDLE is requesting the __repr__() of `self` 
while still executing `__init__()` but before `self.name` is set, triggering an 
AttributeError (although those lines don't exactly line up with that). 
Otherwise looking at the code for _ModuleLock suggests this really shouldn't 
happen as `self.name` is set in `__init__()` and there's no use of `del` or 
`delattr()` that would cause this.

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue33065] IDLE debugger: problem importing user created module

[Terry J. Reedy]

Terry J. Reedy  added the comment:

We use 'crash' for, on Window, a process stopping either with no explanation or 
a 'Your process has stopped box' from Windows.

In any case, PositionalList.py will not run without _DoublyLinkedBase.py, which 
you did not upload.

The traceback has
  File "...\Python\Python36\lib\bdb.py", line 48, in trace_dispatch
return self.dispatch_line(frame)

Since sometime last summer, that code line is line 51, indicating that you are 
using an old release of 3.6, probably 3.6.2 or earlier.  The current bugfix 
release is 3.6.5.  If possible, upgrade to 3.6.5 and retest.

The traceback does not make much sense to me either.  Neither of the IDLE 
methods userline and interaction obviously access a .name attribute of 
anything.  The '_ModuleLock' object is created by importlib._bootstrap.  
Searching all issues for '_ModuleLock' got 11 hits.  None are obviously about 
import and tracing.

To determine whether the problem has anything to do with IDLE, single-step 
debugging should be repeated with pdb, which is Python's text debugger, and 
also based on bdb.

Brett, can you tell anything from the multiple importlib._bootstrap lines in 
the traceback?

--
nosy: +brett.cannon
type: crash -> behavior

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue33065] IDLE debugger: problem importing user created module

[om364@]

om364@  added the comment:

Traceback (most recent call last):
  File "...\PositionalList.py", line 1, in 
from _DoublyLinkedBase import _DoublyLinkedBase
  File "", line 968, in _find_and_load
  File "", line 148, in __enter__
  File "", line 174, in _get_module_lock
  File "", line 59, in __init__
  File "", line 59, in __init__
  File "...\Python\Python36\lib\bdb.py", line 48, in trace_dispatch
return self.dispatch_line(frame)
  File "...\Python\Python36\lib\bdb.py", line 66, in dispatch_line
self.user_line(frame)
  File "...\Python\Python36\lib\idlelib\debugger.py", line 24, in user_line
self.gui.interaction(message, frame)
AttributeError: '_ModuleLock' object has no attribute 'name'

The file works correctly in PowerShell, but in IDLE debbuger there is a error.

--
nosy: +om364@
type: behavior -> crash
Added file: https://bugs.python.org/file47532/PositionalList.py

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue33065] IDLE debugger: problem importing user created module

[Terry J. Reedy]

Terry J. Reedy  added the comment:

I cannot do anything from this bare description, as I cannot think of any 
reason why stepping should introduce an error.  It sounds like there are two 
files involved.  Try to reduce them to the minimum needed to reproduce the 
issue and then upload.

--
stage:  -> test needed
title: debugger issue concerning importing user created modules into another 
program -> IDLE debugger: problem importing user created module
type: compile error -> behavior

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com