mintCast 289 – Linux Mint 19
- Isaac has puppies, been playing with Gnome, and still can’t get his Arch box to work correctly.
- Rob’s been on vacation and solved some issues with pip on his Mint 18.3 box.
- Linux Mint 19 “Tara” Released!
- Gentoo GitHub was hacked
- Suicide Linux
- Rob and Isaac installed Linux Mint 19 and talked about everything they liked.
Vibrations from the Ether:
- Contribute to Linux Mint!
- Info about OpenRheinRuhr
Check this out!:
- Finally finished the first four books in the “Singularity” series by David Beers (http://www.davidbeersfiction.com/the-singularity-series/)
- “Yesterday’s Conversation” by Angus Wallace
- “The Red Stone” by Ground & Leaves
- Send us your bumper or intro or outro music.
- We’ll be back in a month everyone!
Hosts: Rob and Isaac
Live Stream every other Sunday 2:00 p.m.(Central): mintcast.org/livestream
- Forum: forums.linuxmint.com (rarely)
- Email: [email protected]
- Twitter: @mintCast @txhawkins @Linux_Mint
- IRC: irc.spotchat.org – #mintcast
- Google+: mintCast
More Linux Mint info: website, blog, forums, community
Podcast Entry and exit music provided by Mark Blasco (podcastthemes.com). Podcast bumpers provided by Oscar.
Podcast: Play in new window | Download
2 Replies to “mintCast 289 – Linux Mint 19”
I’m glad they got rid of the levels feature in the update manager. Security should always be a priority.
I actually first learned about the bash path hash from the Linux from Scratch book. The first command that it recommends putting in ~/.bashrc is `set +h` to disable hashing so that bash will always look up paths and will pick up the new tools as they are compiled (http://www.linuxfromscratch.org/lfs/view/stable-systemd/chapter04/settingenvironment.html).
Rob, I’m not sure what Python versions you were dealing with, but in recent versions pip is built into Python. The pip command is deprecated though. The official recommendation is to use `python -m pip` instead of `pip`. The reason for this recommendation is that there is too much opportunity for confusion between the version of python and the version of pip being used. Using `python -m pip` you always use the pip tied the python binary you are executing.
If I am doing something simple and the Python packages in the repo are sufficient, I will use them, but other I use an environment I manage like Isaac was describing for node. pipenv is a nice tool for managing Python virtual environments. I also like conda (installed with the miniconda installer).