micropipenv as an alternative for pipenv for S2I images
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 20/100
- Issue type
- Feature
- Clarity
- Needs clarification
- Activity status
- Stale
- Domain
- devops, infrastructure
Research direction
Review the current Pipenv setup for the S2I images and compare it with micropipenv's Python 2 and Python 3 support. Define whether and how micropipenv can replace Pipenv without abandoning Python 2 support; completion would require an agreed approach rather than the unresolved alternatives listed here.
Written by the indexing model from the issue text.
Description
It seems that micropipenv might be a good alternative for pipenv in S2I images because it's a light piece of software and pipenv seems to be unmaintained for a while.
The main problem is that micropipenv does not support Python 2 which means that we can:
- either make it Python 2 compatible which does not seems to be an easy task (https://github.com/thoth-station/micropipenv/pull/18) and its maintainers obviously don't want to support EOL Python in the new fresh software
- or use it only for Python 3 images which would make our images different in another aspect and can possibly cause problems
- or install Python 3 on Python 2 images and create a virtual environment just for micropipenv which would make our images way bigger
We discussed this today on SCL meeting and decided that we'll keep this open. There are no issues related to older or buggy version of Pipenv in S2I containers. We can wait for a while and when any issue comes we can solve them by using micropipenv only for Python 3 or any other way we'll discover in the meantime.
- Dominant language
- Shell
- Stars
- 271
- Forks
- 329
- PR merge metrics
- No merged PRs in 30d
Contributor guide
No contributing guide indexed for this repository
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 sclorg/s2i-python-container
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
sclorg/s2i-python-container#813 · 4 comments ·
-
Difficulty 3/5 1-2 days Newbie friendliness 35/100
sclorg/s2i-python-container#747 ·
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
sclorg/s2i-python-container#540 · 1 comment ·
-
enhancement P3
Difficulty 5/5 Over a week Newbie friendliness 15/100
sclorg/s2i-python-container#304 · 8 comments · 2 reactions ·
-
help wanted openshift
Difficulty 4/5 3-5 days Newbie friendliness 35/100
sclorg/s2i-python-container#280 · 12 comments ·
All issues in sclorg/s2i-python-container
Similar issues
-
out-of-date
Difficulty 1/5 Under an hour Newbie friendliness 82/100
CachyOS/CachyOS-PKGBUILDS#1894 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
community-scripts/ProxmoxVE#17396 · 1 comment ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
mattpocock/skills#1099 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100