Revisit "nested virtualenvs" problem
A pull request for this has already been merged.
- #444 by @Krishnabhuvan — merged
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 30/100
Research direction
Start by validating nested virtualenv creation across the relevant Python versions and environment-handling methods. Then review the existing checks and the README: done means preserving the restrictions if the problem remains, or removing them and documenting supported nested environments and the validated pipx install fades usage if it now works.
Written by the indexing model from the issue text.
Description
At some point in time, with some Python versions and ways to handle environments, if you created a virtualenv being already inside another virtualenv, that creation was broken.
To avoid this situation biting users, we added a couple of checks that will alert early that the situation was there.
Fast forward several years. Today it may work. We need to check if this is the case.
If not, everything remain as before.
If now it's possible to have a virtualenv created while you were in other virtualenv, then:
- check the README and verify if we're saying something about this, and fix
- annotate also in the README that
pipx install fadesis a proper way of using the project (validate first!) - remove those restrictions that we added to alert the user
- Dominant language
- Python
- Stars
- 223
- Forks
- 45
- PR merge metrics
- No merged PRs in 30d
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
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 PyAr/fades
-
Difficulty 3/5 1-2 days Newbie friendliness 45/100
-
Difficulty 4/5 3-5 days Newbie friendliness 52/100
-
Difficulty 5/5 Over a week Newbie friendliness 42/100
-
PEP 723 supportOpenenhancement
Difficulty 4/5 3-5 days Newbie friendliness 45/100
-
Difficulty 3/5 1-2 days Newbie friendliness 38/100
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
Maintainers usually reply within 3 days
-
Negation with "not" and "no" is ignored during sentiment analysisPossibly taken @vivek-3728 claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
techcsispit/mess-mood#11 · 1 comment ·
-
changelog investigate
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
ramnes/notion-sdk-py#408 ·
-
good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 83/100
btclib-org/btclib-wallet#267 ·
Maintainers usually reply within 1 day
-
good first issue tech-debt
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
knnmelprop/YAADO#111 ·