You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Virtual environments is an interesting concept, heavily used by Python programmers. Since I usually use several versions of Java and Scala, I borrowed the concept from the Python ecosystem given that in reality, the benefits apply equally to several other ecosystems, not only Python.
Some time ago, my preferred virtual environments were part of the codebase and were initialized (if necessary) when a new terminal window was opened. The reasons for that are explained in Design Concept below.
Since this project started to become more popular, it became clear that I should never push my virtual environments to users of this project. For this reason, I've moved my virtual environments to somewhere else. However, there are still leftovers around here and, in particular, I'm still forcing a "default" (let's put this way) virtual environment called p3 to users of this project.
Design Concept
Starting from a brand new laptop with only the base operating system installed, I would like to be able to quickly have my environment setup. I would like to download a shell script from the Internet which sets up everything for me. Then I open a new terminal window, all remaining bits and pieces are automagically configured and I'm ready to go.
Requirements
Support for virtual environments is enable only if there's support for Python in the underlying distribution. Even though the vast majority of distributions have some sort of Python version pre-installed, some small distributions don't. And we should accommodate for that.
Given that Python is supported but pip is not available, we should download pip from the Internet and install it.
Given that pip was successfully installed, we then install/upgrade virtualenv and virtualenvwrapper.
Given that virtualenvwrapper was successfully installed, we should source virtualenvwrapper.sh in order to make commands workon and mkvirtualenv available, among other commands.
Additional tasks:
We should NOT enforce or configure any virtual environment, i.e.: p3 should go!
We should make sure that the Downloads folder is configurable.
Related: #23 #36
Background
Virtual environments is an interesting concept, heavily used by Python programmers. Since I usually use several versions of Java and Scala, I borrowed the concept from the Python ecosystem given that in reality, the benefits apply equally to several other ecosystems, not only Python.
Some time ago, my preferred virtual environments were part of the codebase and were initialized (if necessary) when a new terminal window was opened. The reasons for that are explained in Design Concept below.
Since this project started to become more popular, it became clear that I should never push my virtual environments to users of this project. For this reason, I've moved my virtual environments to somewhere else. However, there are still leftovers around here and, in particular, I'm still forcing a "default" (let's put this way) virtual environment called
p3to users of this project.Design Concept
Starting from a brand new laptop with only the base operating system installed, I would like to be able to quickly have my environment setup. I would like to download a shell script from the Internet which sets up everything for me. Then I open a new terminal window, all remaining bits and pieces are automagically configured and I'm ready to go.
Requirements
pipis not available, we should downloadpipfrom the Internet and install it.pipwas successfully installed, we then install/upgradevirtualenvandvirtualenvwrapper.virtualenvwrapperwas successfully installed, we should sourcevirtualenvwrapper.shin order to make commandsworkonandmkvirtualenvavailable, among other commands.Additional tasks:
p3should go!The text was updated successfully, but these errors were encountered: