Debugger does not jump to Breakpoint inside a Module

[reneheimbuch]

Environment data

• VS Code version: 1.28.1
• Extension version (available under the Extensions sidebar): 2018.9.0
• OS and version: Windows 7 SP1 64 Bit
• Python version (& distribution if applicable, e.g. Anaconda): 3.6.5
• Type of virtual environment used (N/A | venv | virtualenv | conda | ...): N/A
• Relevant/affected Python packages and their versions: None

Actual behavior

Debugger stops, but behaves as if the breakpoint was set in the callers script.

Expected behavior

Debugger should stop inside the module, exactly at the breakpoint's locoation and show local and global debug information

Steps to reproduce:

1. Create "Caller File" somewhere not in the python path.

import mymodule

2. New folder $python\Lib\site-packages\mymodule

3. New Module File $python\Lib\site-packages\mymodule_init_.py

print("breakpoint")

4. Load both folders into workspace

5. set breakpoint at print statement

6. start debug of caller file.

result: breakpoint will stop at import mymodule not at print ...

Logs

[brettcannon]

This is on purpose so that you don't jump into library code if you don't want to. Please see #2087 for the feature you want that will let you debug into library code.