pyvenv is no longer compatible with Python built from source
還沒有人認領這個 Issue。
評估
研究方向
Start at the ::python::pyvenv resource entry point and trace how it installs the python3.7-venv package. Verify the behavior for a Python 3.7 interpreter built from source, then make completion avoid the package step when the venv module is already available. Done means the virtualenv is created without requiring an unavailable apt package.
由索引模型根據 Issue 內容生成。
描述
Affected Puppet, Ruby, OS and module versions/distributions
- Puppet: 5.56
- Ruby: 2.4.4
- Distribution: Ubuntu 16.04
- Module version: 4.0.0
How to reproduce (e.g Puppet code you use)
::python::pyvenv { $venv_path :
version => '3.7.6',
}
What are you seeing
The virtualenv is not created because it cannot install the python3.7-venv package via apt. This is because my version of python3.7 was built from source, and therefore I didn't get the python3.7 package via apt. Since python3.7 is required to install python3.7-venv via apt, this fails.
When built from source, venv is already included, so an additional package containing the venv module is not necessary, so this step should be skipped.
What behaviour did you expect instead
I expected the virtualenv to be correctly created
Output log
Error: Execution of '/usr/bin/apt-get -q -y -o DPkg::Options::=--force-confold install python3.7-venv' returned 100:
Reading package lists...
Building dependency tree...
Reading state information...
E: Unable to locate package python3.7-venv
E: Couldn't find any package by glob 'python3.7-venv'
E: Couldn't find any package by regex 'python3.7-venv'
Any additional information you'd like to impart
I believe that the best way to skip this step if necessary would be to check for the presence of the venv module. This could either be done using something like python3.7 -c "import venv" or pydoc3.7 venv, or checking if the folder exists at /usr/local/lib/python3.7/venv (not sure if this directory changes).
- 主要語言
- Ruby
- 星號
- 196
- 分支
- 371
- 平均合併
- 5 小時 54 分鐘
- 30 天內合併 PR
- 5
環境準備
在瀏覽器裡用你自己的 GitHub 帳號啟動這個專案的開發容器。
- 沒有 Dockerfile 或 Docker Compose 檔案
- 有 Pull Request 範本
- 閱讀貢獻指南
從這裡開始
- 先讀完整個 Issue，再讀專案的貢獻指南。
- 在 Issue 下留言說明你要接手 —— 這能避免兩個人做同樣的事。
- Fork 儲存庫，在一個分支上完成修改。
- 送出 Pull Request，並在描述裡引用這個 Issue 編號。
voxpupuli/puppet-python 的其他 Issue
-
難度 3/5 1-2 天 新手友好度 67/100
voxpupuli/puppet-python#759 ·
-
bug
難度 3/5 1-2 天 新手友好度 45/100
voxpupuli/puppet-python#743 · 1 則留言 ·
-
enhancement
難度 3/5 1-2 天 新手友好度 35/100
voxpupuli/puppet-python#721 · 1 個 reaction ·
-
難度 3/5 1-2 天 新手友好度 35/100
voxpupuli/puppet-python#711 · 1 則留言 ·
-
難度 2/5 1-3 小時 新手友好度 52/100
voxpupuli/puppet-python#673 · 1 則留言 ·
查看 voxpupuli/puppet-python 的全部 Issue
相似的 Issue
-
難度 2/5 1-3 小時 新手友好度 85/100
維護者通常 1 天內回覆
-
難度 2/5 1-3 小時 新手友好度 72/100
維護者通常 1 天內回覆
-
account: profile
難度 2/5 1-3 小時 新手友好度 75/100
維護者通常 5 天內回覆
-
難度 2/5 1-3 小時 新手友好度 82/100
維護者通常 1 天內回覆
-
bug good first issue help wanted
難度 2/5 1-3 小時 新手友好度 90/100
ysb3996-blip/oops#24 ·
維護者通常 1 天內回覆