"import akshare as ak" blocks the debugger after I upgrade to python 3.12.2
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 35/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- python, vscode
- Domain
- developer-experience, tooling
Research direction
Start with the minimal run.py reproduction containing import akshare as ak, using the reported Python 3.12.2, VS Code 1.88.0, and debugpy v2024.4.0 environment. Compare Debug with Run Without Debugging and python -m pdb run.py; done means the import no longer blocks the VS Code debugger.
Written by the indexing model from the issue text.
Description
Environment data
- debugpy version: v2024.4.0
- OS and version: Windows 11 Pro 23H2 22631.3374
- Python version (& distribution if applicable, e.g. Anaconda): 3.12.2(conda 24.3.0)
- Using VS Code or Visual Studio: VS Code 1.88.0
Actual behavior
import akshare as ak
After I upgrade to python 3.12.2, the above sentence blocks the python debugger(other imports work), and "Run Without Debugging" works. It worked well before.
When I use following command to run python debugger in cmd, it works well
pytyon -m pdb run.py
So I think it's a bug of debugger extension of vscode instead of akshare lib.
And the owner of akshare lib suggested me to use pycharm instead of vscode to get around this issue, it costs a lot for me.
Expected behavior
"import akshare as ak" doesn't block debugger extension of vscode.
Steps to reproduce:
- create the following run.py file:
import akshare as ak
if __name__ == "__main__":
print("it works")
-
start debug, the process will be blocked. start "Debug Without Debugging", it works.
-
remove the line: import akshare as ak, everything works well.
- Dominant language
- Python
- Stars
- 2.5k
- Forks
- 202
- Avg merge
- 5d 1h
- Merged PRs (30d)
- 1
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from microsoft/debugpy
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
documentation
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
documentation
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
-
Difficulty 3/5 1-2 days Newbie friendliness 68/100
All issues in microsoft/debugpy
Similar issues
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
xinnan-tech/xiaozhi-fde-talk#263 ·
-
rules
Difficulty 1/5 Under an hour Newbie friendliness 90/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
huggingface/Repo2RLEnv#163 · 1 comment ·
-
Difficulty 1/5 Under an hour Newbie friendliness 95/100
huggingface/sentence-transformers#4074 ·
-
comp/dashboard invalid P3
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
NousResearch/hermes-agent#121143 ·