Hacktoberfest 2026:維護者為十月標記出來的 issue,仍然開放、適合新手。 瀏覽 Hacktoberfest issue

Conda environment initialized differently when executing vs debugging unit tests

未關閉
#736 3 則留言 0 個 reaction 已指派 1 人 在 GitHub 檢視

@eleanorjboyd 已經在處理了。

開始於 2025年6月30日。

評估

這個 Issue 還沒有評估資料。

描述

triage-needed

I have to develop my code on a custom python stack that doesn't fully conform to anaconda; many packages are initialized by adding them to PYTHONPATH with a command-line tool. I automated this by creating an activation script that went under etc/conda/activate.d. I also have a .env in the workspace root that sets the same PYTHONPATH. I works but I found the following issue:

  • When a unit test is started without debugging the procedure of running it is: 1) source .env 2) execute conda run ... which will result in sourcing the custom activation scripts under etc/conda/activate.d.
  • When a unit test is started in the debugger, the procedure differs: 1) source .env 2) execute some auto-generated script that will call the debugpy module. The custom activation scripts under etc/conda/activate.d seem not be sourced.

This can be an issue for some. The behavior should be that the conda environment is activated the same way while debugging and just executing unit tests.

主要語言
TypeScript
星號
181
分支
126
平均合併
8 小時 49 分鐘
30 天內合併 PR
1

貢獻指南

開啟貢獻指南

從這裡開始

  1. 先讀完整個 Issue,再讀專案的貢獻指南。
  2. 在 Issue 下留言說明你要接手 —— 這能避免兩個人做同樣的事。
  3. Fork 儲存庫,在一個分支上完成修改。
  4. 送出 Pull Request,並在描述裡引用這個 Issue 編號。

microsoft/vscode-python-debugger 的其他 Issue

查看 microsoft/vscode-python-debugger 的全部 Issue

相似的 Issue

更多 TypeScript Issue

把新 issue 寄到你的電子郵件信箱

精選適合新手參與的 GitHub issue 摘要。