Getting Started with Python

    Of course, that last part is optional — you are totally free to code Python on your own and chose not to interact with anyone within the community — but, you’ll be missing out on the best part of what makes Python Python!

    Twitter is an excellent way to keep in touch with what’s going on with the Python community. Here is a very non–exhaustive (but evolving) list of some suggetions of who to follow on Twitter, to get started:

    • The Python Software Foundation ()
    • Guido Van Rossum (@gvanrossum) — The creator of Python itself. Doesn’t tweet much, but is occassionally accessable. Very kind soul. Keep in mind, he gets a lot of attention.
    • Nick Coghlan () — Core Python developer, very active on Twitter, has very thoughtful thoughts about Open Source and the direction of Python in general.
    • Lynn Root (@roguelynn) — Closely related to PyLadies.
    • Armin Ronacher () — The creator of Flask, Click, Sphinx, and many other wonderful Python utilities we all know and love. Mostly found writing iOS and Rust code nowadays.
    • Corey Benfield (@Lukasaoz)
    • Alex Gaynor ()
    • Yarko T. (@yarkot)
    • Brett Cannon ()
    • Danny Greenfield (@pydanny)
    • Raymond Hettinger ()
    • Jeff Forcier (@bitprophet) — The creator of Fabric, and maintainer of many open source libraries.

    Getting Python Installed

    Of course, the first thing you need to do is install Python on your machine. If you go to the Python.org website, you may be a bit confused about which version of Python you should be using. The correct answer is:

    Use the latest version of Python 3. As of the time of this writing, that is version 3.7.0.

    Here are some great installation guides for various system types:

    A package manager, like Pipenv (which we’ll cover shortly), or the lower–level pip (in conjunction with virtualenv can be used to install and manage these dependencies, which are typically hosted on either on PyPi (The Python Package Index) or .

    You’ll typically see these required packages (and any specific versions) declared in one of the following files: , requirements.txt, or setup.py.

    Installing Pipenv

    The next step is to install Pipenv, our packaging tool of choice. Package managers allow us to easily manage (resolve, install, uninstall) dependencies and virtual environments for projects.

    Python.org has a great guide available for installing Pipenv that also covers its basic usage.

    If you’re on a Mac, and have installed, the following command will suffice:

    First, into your new project directory (after you $ mkdir and $ git init it, of course), and simply run to install the requests library, which is one of our favorites.

    Then, run $ pipenv shell to run a shell that will have a $ python available in which will function properly. Pretty simple :)

    For further instructions, check out .

    Understanding Source Control

    In the Python community, we typically use git, a version control system. Tools, like git, are used to store all changes to code files, so you can go back to any point in history and reference yourself later if needed. They are also very useful for collaborating with others.

    Git is a bit tricky to get started with, but that will get you setup and teach you the basics. It’s a requirement if you’re ever going to work with Python in a professional environment.