fisher VS virtualenv

Install with Fisher:

curl -sL https://git.io/fisher | source && fisher install jorgebucaran/fisher

Fisher - Plugin manager

You've got to install Fisher, then get z, sponge and a few others from the awsm.fish list.

Then you get trapped by the utility and struggle when you land on some remote server's bash shell.

https://github.com/jorgebucaran/fisher

https://github.com/jorgebucaran/awsm.fish#readme

If you're running a script, you can use edc/bass to run it from a fish shell. Fisher is one of the first things I install after fish, then bass, z and a few other helper plugins.

https://github.com/edc/bass

https://github.com/jorgebucaran/fisher

As a minimalist plugin manager for Fish, I recommend fisher. I've created a plugin that can be installed via fisher and integrated into any Fish environment. If there are any reasons why you don't want to use Fisher, you can just copy-paste conf.d/autoenv.fish file to your ~/.config/fish/conf.d directory.

Fish is a acronyn for friendly interactive shell. It is a smart and user friendly shell for Unix-like operating systems like Linux. There are a lot of features that make it stand out from other shells like bash. It has a lot of features like autosuggestions, syntax highlighting, tab completions and a lot more. You can read more about it in the documentation. I have been using it for a while now and I it configured to my liking. In terms of plugins I use fisher to manage my plugins. I have a couple of plugins that I use on a daily basis. I have listed them below:

stay away from Oh-My-Fish - you probably don’t need it - Fish is pretty awesome out of the box, and if you do want a plugin or two Fisher is a much better route.

Agreed. I personally like Fisher (https://github.com/jorgebucaran/fisher) with this theme based on Powerlevel10k (https://github.com/IlanCosman/tide)

Virtualenv package

If you’ve been managing Python projects long enough, you’ve probably dealt with a mess of tools: pip, pip-tools, poetry, virtualenv, conda, maybe even pdm.

For more information visit: virtualenv documentation.

Python's venv module is officially recommended for creating virtual environments since Python 3.5 comes packaged with your Python installation. While there still are additional older tools available, such as conda and virtualenv, if you are new to virtual environments, it is best to use venv now.

Despite these attractive attributes, many developers I've come across don't prefer Fish shell, primarily due to integration gaps with tools like Python's virtualenv. So, in this article, I'm offering a simple solution for automatic virtualenv activation for Fish shell, steering clear of resource-intensive frameworks like oh-my-fish that often slow down the shell.

`virtualenv` still exists and is still actively developed. It's true that Python 3 ships with `venv` but I think `virtualenv` offers some additional features.

https://github.com/pypa/virtualenv

virtualenv is a tool that creates an isolated Python environment for each of your projects.

Python is the chosen language for this tutorial and as you can guess some precautions should be done to make sure that the environment is setup correctly and the main OS I'll use is Ubuntu(a Linux distro) virtual environment is a tool that helps you to isolate your code from the rest of the system. It is a good idea to create a virtual environment for your project.

$ curl -O https://github.com/pypa/virtualenv/raw/master/virtualenv.py$ python virtualenv.py my_new_env$ . my_new_env/bin/activate(my_new_env)$ pip install ... Or something entirely different?