I really appreciate this. Will subscribe immediately. I've been on windows for 25 years. But just started to use Mint cinnamon this week. And now i want to learn as much as I can. You have a great way of explaining, and a good voice to listen to. Keep it up.
What video should I make next? Any suggestions? *Write me in comments!* Follow me @: Telegram: t.me/red_eyed_coder_club Twitter: twitter.com/CoderEyed Facebook: fb.me/redeyedcoderclub Help the channel grow! Please Like the video, Comment, SHARE & Subscribe!
Amazing, apparently atom is not being actively developed anymore? So in the 'vva' alias creation i replaced atom with code after installing visual studio and --classic code from snap. Everything else worked perfectly, thanks man!!
Hello again....Can you a video on pipenv and explain the difference between virtualenv and pipenv.....and ofcourse which is better.....with visual studio code
Pipenv - is a Python package manager like the Pip and also it creates virtual environments - 2 in 1. Better use Poetry. Virtualenv is a tool for creation and management of Python virtual environments only. To install Python packages you have to use Pip. Right now I use Poetry as the package manager and for virtual environments.
Thank you! To install neo-vim type in a terminal: sudo apt install neovim And to customize it for Python development see this video: th-cam.com/video/wzrZPcwh-bE/w-d-xo.html But I'll probably make a video about installing neovim
What a coincidence ... I started using the Mint distribution yesterday, and you come with this tutorial. It hasn't been long since I migrated from windows to Linux, and I felt a huge difference in cursor sensitivity ... Do you know any way to permanently disable mouse acceleration in mint?
Try to look at System Settings > Hardware section > Mouse and Touchpad. There are options: Custom Acceleration and Custom Sensitivity. But actually I had no issues with it. It's weird.
@@RedEyedCoderClub The problem is that when I adjust the sensitivity, the acceleration is adjusted as well. Maybe I just need to get used to it. And thanks for the tutorial, this will be of great help.
Помогите. 11:39 сделал точно как вы только не ставил гит(т.к. он стоит) но python вызывает версию 3.8.10 а pip не распознаёт. Я начинающий пользователь линукса, думаю что-то у меня с символическими сылками.Буду рад любой помощи.
Проблему решил. просто в конец .bashrc пишете export PATH="$HOME/.pyenv/bin:$PATH" eval "$(pyenv init --path)" eval "$(pyenv virtualenv-init -)" сохраняете, заходите в консоль выполняете команду exec $SHELL P.S. До этого я в .bashrc записывал код как в видео там /home/mrx(это я)/.pyenv/ и т.д. Уж не знаю почему сработало, если кто знает напише пожалуйста в комменты)
Отлично! Хорошо, что сами разобрались. +100 exp, как обычно. Я написал "установщик" Pyenv для Ubuntu-based дистрибутивов: github.com/zaemiel/ubuntu-pyenv-installer
New to linux as I want to learn more in technology and I know linux and python are the foundation. Installed linux mint mate 20 and followed your video on installing python here, everything worked well up untill opening the Nemo text document as it's empty. I tried going to preferences and doing what you said but is still empty. Any suggestions? Thanks and great video I feel more confident now in learning starting programming and development.
Hello, unfortunately the Mate desktop environment uses the Caja file manager instead of the Nemo. I used the Cinnamon DE. I don't use Mate, and can't help you with it. Sorry. Updated the description.
@@RedEyedCoderClub thanks anyways, other than that I figure I installed python correctly from your video, just a couple commands prompted me with the "additional space will be used do you wish to continue?" I put yes Ofcourse but do not know why I got that? Thanks again
this is what appears to me when iI install pyenv WARNING: seems you still have not added 'pyenv' to the load path. # (The below instructions are intended for common # shell setups. See the README for more guidance # if they don't apply and/or don't work for you.) # Add pyenv executable to PATH and # enable shims by adding the following # to ~/.profile: export PYENV_ROOT="$HOME/.pyenv" export PATH="$PYENV_ROOT/bin:$PATH" eval "$(pyenv init --path)" # If your ~/.profile sources ~/.bashrc, # the lines need to be inserted before the part # that does that. See the README for another option. # If you have ~/.bash_profile, make sure that it # also executes the above lines -- e.g. by # copying them there or by sourcing ~/.profile # Load pyenv into the shell by adding # the following to ~/.bashrc: eval "$(pyenv init -)" # Make sure to restart your entire logon session # for changes to profile files to take effect. # Load pyenv-virtualenv automatically by adding # the following to ~/.bashrc: eval "$(pyenv virtualenv-init -)" Could you help me with that?
Did you use github.com/pyenv/pyenv-installer ? In my .bashrc I use only these three lines: export PATH="/home/oleg/.pyenv/bin:$PATH" eval "$(pyenv init -)" eval "$(pyenv virtualenv-init -)"
This command alias vva="virtualenv venv && source venv/bin/activate && mkdir app && cd app && atom ."in to the .bashrc file found in the home directory did not work so I had to use this instead Try to create the virtual environment using directly on to the terminal already opened from folder python3 -m venv my_env which creates a folder called my_env in the desktop folder you created. All at around 18.14
PyEnv installs virtualenv by default. And this alias should work. If you didn't install pyenv so you have to install virtualenv manually. "Doesn't work" - it's too vague. There is no context of your actions - wheather you used pyenv or not and so on. But anyway you can install virtual environment in any way you like.
@@RedEyedCoderClub Do i then work in my created folder as in python3 -m venv venv_name with venv_name being my named folder as... say...hair? or is that my created virtual environment in to which I do not work? if so, what folder do I use and where to work on.
virtual environment - it's just a concept. Technically a virtual environment is just a folder (a directory) where a Python interpreter and its packages will be installed. You can examing the folder of your virtual environment and you will see a Python interpreter, and installed packages (like requests or bs4 etc). The name of the virtual environment doesn't matter. Also you don't work with the files in it directly - it's not your project. It's just a folder to store dependencies of your own project.
I really appreciate this. Will subscribe immediately. I've been on windows for 25 years. But just started to use Mint cinnamon this week. And now i want to learn as much as I can. You have a great way of explaining, and a good voice to listen to. Keep it up.
Thank you very much!
This is amazing! I'm a rookie when it comes to Linux.. Your video is top notch. Thank you!
SO clearly explained.....thanks a lot.....you should start teaching "Linux" and "Python" as a course.....
Thank you!
@@RedEyedCoderClub if a new python version comes...then is the process same?
Now to install PyEnv and Python I use my script:
github.com/zaemiel/ubuntu-pyenv-installer
It's very handy. The rest is the same
@@RedEyedCoderClub vva command doesn't work
it's not a command it's an alias of several commands. How to create it I said in this video. @@urgot-bo1lz
Hands down THE best tutorial I found this year. Sub.
Thanks for comment :)
Your videos are excellent. I think you should consider writing a book at some point. You have a talent for teaching/explaining things.
What video should I make next? Any suggestions? *Write me in comments!*
Follow me @:
Telegram: t.me/red_eyed_coder_club
Twitter: twitter.com/CoderEyed
Facebook: fb.me/redeyedcoderclub
Help the channel grow! Please Like the video, Comment, SHARE & Subscribe!
Parabéns, super didático.
Very nice -- thank you.
Thanks for watching! And for you comment!
Amazing, apparently atom is not being actively developed anymore? So in the 'vva' alias creation i replaced atom with code after installing visual studio and --classic code from snap.
Everything else worked perfectly, thanks man!!
Hello again....Can you a video on pipenv and explain the difference between virtualenv and pipenv.....and ofcourse which is better.....with visual studio code
Pipenv - is a Python package manager like the Pip and also it creates virtual environments - 2 in 1. Better use Poetry.
Virtualenv is a tool for creation and management of Python virtual environments only. To install Python packages you have to use Pip.
Right now I use Poetry as the package manager and for virtual environments.
Great explanation, can you do a tutorial how to setup neovim instead of atom,regards
Thank you!
To install neo-vim type in a terminal:
sudo apt install neovim
And to customize it for Python development see this video:
th-cam.com/video/wzrZPcwh-bE/w-d-xo.html
But I'll probably make a video about installing neovim
Thank you very much for useful videos!
Thank you very much. Have a nice day!
What a coincidence ... I started using the Mint distribution yesterday, and you come with this tutorial. It hasn't been long since I migrated from windows to Linux, and I felt a huge difference in cursor sensitivity ... Do you know any way to permanently disable mouse acceleration in mint?
Try to look at System Settings > Hardware section > Mouse and Touchpad.
There are options: Custom Acceleration and Custom Sensitivity.
But actually I had no issues with it. It's weird.
@@RedEyedCoderClub The problem is that when I adjust the sensitivity, the acceleration is adjusted as well. Maybe I just need to get used to it. And thanks for the tutorial, this will be of great help.
This was amazing
Thank you
Помогите. 11:39 сделал точно как вы только не ставил гит(т.к. он стоит) но python вызывает версию 3.8.10 а pip не распознаёт. Я начинающий пользователь линукса, думаю что-то у меня с символическими сылками.Буду рад любой помощи.
Проблему решил. просто в конец .bashrc пишете
export PATH="$HOME/.pyenv/bin:$PATH"
eval "$(pyenv init --path)"
eval "$(pyenv virtualenv-init -)"
сохраняете, заходите в консоль выполняете команду
exec $SHELL
P.S.
До этого я в .bashrc записывал код как в видео там /home/mrx(это я)/.pyenv/ и т.д. Уж не знаю почему сработало, если кто знает напише пожалуйста в комменты)
Отлично! Хорошо, что сами разобрались. +100 exp, как обычно.
Я написал "установщик" Pyenv для Ubuntu-based дистрибутивов:
github.com/zaemiel/ubuntu-pyenv-installer
Это перестало работать с августа 2021, они что-то изменили и у многих возникла такая проблема. Поэтому я написал свой "установщик" pyenv.
@@RedEyedCoderClub Спасибо
New to linux as I want to learn more in technology and I know linux and python are the foundation.
Installed linux mint mate 20 and followed your video on installing python here, everything worked well up untill opening the Nemo text document as it's empty. I tried going to preferences and doing what you said but is still empty. Any suggestions?
Thanks and great video I feel more confident now in learning starting programming and development.
Hello, unfortunately the Mate desktop environment uses the Caja file manager instead of the Nemo. I used the Cinnamon DE. I don't use Mate, and can't help you with it. Sorry.
Updated the description.
@@RedEyedCoderClub thanks anyways, other than that I figure I installed python correctly from your video, just a couple commands prompted me with the "additional space will be used do you wish to continue?" I put yes Ofcourse but do not know why I got that? Thanks again
Thanks for watching!
this is what appears to me when iI install pyenv
WARNING: seems you still have not added 'pyenv' to the load path.
# (The below instructions are intended for common
# shell setups. See the README for more guidance
# if they don't apply and/or don't work for you.)
# Add pyenv executable to PATH and
# enable shims by adding the following
# to ~/.profile:
export PYENV_ROOT="$HOME/.pyenv"
export PATH="$PYENV_ROOT/bin:$PATH"
eval "$(pyenv init --path)"
# If your ~/.profile sources ~/.bashrc,
# the lines need to be inserted before the part
# that does that. See the README for another option.
# If you have ~/.bash_profile, make sure that it
# also executes the above lines -- e.g. by
# copying them there or by sourcing ~/.profile
# Load pyenv into the shell by adding
# the following to ~/.bashrc:
eval "$(pyenv init -)"
# Make sure to restart your entire logon session
# for changes to profile files to take effect.
# Load pyenv-virtualenv automatically by adding
# the following to ~/.bashrc:
eval "$(pyenv virtualenv-init -)"
Could you help me with that?
Did you use github.com/pyenv/pyenv-installer ?
In my .bashrc I use only these three lines:
export PATH="/home/oleg/.pyenv/bin:$PATH"
eval "$(pyenv init -)"
eval "$(pyenv virtualenv-init -)"
а почему не python -m venv venv?
because 'virtualenv venv' is faster, almost instant
This command alias vva="virtualenv venv && source venv/bin/activate && mkdir app && cd app && atom ."in to the .bashrc file found in the home directory did not work so I had to use this instead Try to create the virtual environment using directly on to the terminal already opened from folder python3 -m venv my_env which creates a folder called my_env in the desktop folder you created. All at around 18.14
PyEnv installs virtualenv by default. And this alias should work.
If you didn't install pyenv so you have to install virtualenv manually.
"Doesn't work" - it's too vague. There is no context of your actions - wheather you used pyenv or not and so on.
But anyway you can install virtual environment in any way you like.
@@RedEyedCoderClub Do i then work in my created folder as in python3 -m venv venv_name with venv_name being my named folder as... say...hair? or is that my created virtual environment in to which I do not work? if so, what folder do I use and where to work on.
virtual environment - it's just a concept. Technically a virtual environment is just a folder (a directory) where a Python interpreter and its packages will be installed.
You can examing the folder of your virtual environment and you will see a Python interpreter, and installed packages (like requests or bs4 etc).
The name of the virtual environment doesn't matter. Also you don't work with the files in it directly - it's not your project. It's just a folder to store dependencies of your own project.