{"id":16632,"date":"2019-12-23T16:29:09","date_gmt":"2019-12-24T00:29:09","guid":{"rendered":"http:\/\/compositecode.blog\/?p=16632"},"modified":"2020-04-16T09:16:51","modified_gmt":"2020-04-16T16:16:51","slug":"getting-started-with-python-right","status":"publish","type":"post","link":"https:\/\/compositecode.blog\/2019\/12\/23\/getting-started-with-python-right\/","title":{"rendered":"Getting Started With Python Right!"},"content":{"rendered":"

UPDATE POST<\/a>\u00a0Added details about virtualenv to complement this post, per Thomas’ comment in the comments section below! Read this post for MacOS specific system Python setup, then read that for more options on how to set things up right!<\/p><\/blockquote>\n

Recently I sat down to get started on some Python work, specifically on MacOS. I’ve written code in Python before and tried out 2.x and 3.x before. I’m going with 3.x for this and upcoming articles but one thing became apparent. The Python tech stack is still ferociously fragmented in a number of ways, and this post is to provide some clarity if this is your first endeavor into the stack.<\/p>\n

First off, 2.7 and 3.8 are the versions that exist in some state as the\u00a0latest versions<\/em>. 2.7 is obviously not the latest but is still installed, coded in, and used in a vast number of projects where Python is used. On MacOS for example, it’s the default still, and it should be left alone and the latest installed with appropriate Python environment, PIP for dependency, and related ecosystem necessities. As I walk through these steps, that’s important to know.<\/p>\n

Whatever the system environment starting, check out what is on the machine. If on Windows, it’s safe to bet there is nothing on the machine. On Linux or MacOS there will be some version of Python already installed. Running\u00a0python --version<\/code>\u00a0to determine which version of the language is installed.<\/p>\n

If you have a version you can then check out\u00a0which python<\/code>\u00a0to figure out where it is installed. This can come in handy if things get a bit confusing, or verifying where the install is currently setup or pointing to within the file structure.<\/p>\n

<\/a>First Step: Get a tool to install Python<\/h2>\n

On MacOS get\u00a0brew<\/a>\u00a0before doing anything else. For details on Windows check out the\u00a0docs here<\/a>. There’s also a great Digital Ocean post by Lisa Tagliaferri “How to Install python 3 and Set Up a Local Programming Environment on Windows 10<\/a>” if you’re installig Python 3 on Windows 10. For Linux specifically check out these\u00a0docs<\/a>.<\/p>\n

Once brew is installed issue the command to install the “Simple Python Version Management”\u00a0pyenv<\/a>. If this app gives flashbacks to Ruby, it is indeed forked from\u00a0rbenv<\/a>\u00a0so there’s that.<\/p>\n

\n
brew install pyenv\n<\/code><\/pre>\n<\/div>\n
<\/a>Second Step: Install the Latest Python<\/h2>\n
With pyenv install a sepcific version of Python with the following command.<\/p>\n
\n
pyenv install 3.8.0\n<\/code><\/pre>\n<\/div>\n
If there is a new version, install that version instead. On MacOS there is also, of course, already version 2.7 but with pyenv it’ll get the appropriate pieces remapped so that this latest can become the defacto used Python version to work with. To get pyenv to setup this latest installed version us the CLI to set it as the global Python.<\/p>\n
\n
pyenv global 3.8.0\n<\/code><\/pre>\n<\/div>\n
One final step to ensure pyenv can be used when and where necessary, now and ongoing in development needs, set the following in your .zshrc.<\/p>\n
\n
echo -e 'if command -v pyenv 1>\/dev\/null 2>&1; then\\n  eval \"$(pyenv init -)\"\\nfi' >> ~\/.zshrc\n<\/code><\/pre>\n<\/div>\n
If you’re using bash still, make the change accordingly to your\u00a0~\/.bash_profile<\/code>.<\/p>\n
\n
echo -e 'if command -v pyenv 1>\/dev\/null 2>&1; then\\n  eval \"$(pyenv init -)\"\\nfi' >> ~\/.bash_profile\n<\/code><\/pre>\n<\/div>\n
<\/a>Third Step: Get PIP Installed.<\/h2>\n
To check the version of\u00a0pip<\/code>\u00a0run\u00a0pip -V<\/code>. This command not only shows you which version of pip is installed, but also what version of Python pip is installed to oeprate on (with\/on\/at\/to??). The command and result would look something like this.<\/p>\n
\n
pip -V\npip 19.0.3 from \/Users\/adron\/.pyenv\/versions\/3.7.3\/lib\/python3.7\/site-packages\/pip (python 3.7)\n<\/code><\/pre>\n<\/div>\n
Technically, when brew (Homebrew) installed the latest Python has also installed pip and it should be mapped accordingly as shown above in the\u00a0pip -V<\/code>\u00a0command. However this can be set correctly if it isn’t mapped already. Get the path where pip3 is installed by issuing a which command.<\/p>\n
\n
which pip3\n<\/code><\/pre>\n<\/div>\n
The path returned, likely\u00a0\/usr\/local\/bin\/pip3<\/code>, add it to a command to echo it into the startup script of your choice. For example, to add it to the zshrc file.<\/p>\n
\n
echo \"alias pip=\/usr\/local\/bin\/pip3\" >> ~\/.zshrc \n<\/code><\/pre>\n<\/div>\n
If using bash add it as such.<\/p>\n
\n
echo \"alias pip=\/usr\/local\/bin\/pip3\" >> ~\/.bash_profile\n<\/code><\/pre>\n<\/div>\n
<\/a>Fourth Step: Run Some Python Code!<\/h2>\n
Alright, now that this is done, let’s run some actual Python code and make sure things are installed and setup correctly. For this I created a directory I simply called\u00a0python-examples.py<\/code>. Then added the first line of code, a simple print statement.<\/p>\n
\n
print<\/span>(<\/span>\"Hello World! BOOM!\"<\/span>)<\/span>\n\nprint<\/span>(<\/span>\"These examples point out how these variables can be declared and printed.\"<\/span>)<\/span>\n<\/code><\/pre>\n<\/div>\n
Executing that, just by executing the file\u00a0python python_examples.py<\/code>\u00a0and the following results display.<\/p>\n
\n
Hello World! BOOM!\nThese examples point out how these variables can be declared and printed.\n<\/code><\/pre>\n<\/div>\n
Alright, with that confirmed, we’re all set for further Python development! Enjoy!<\/p>\n
<\/a>References:<\/h4>\n