{"id":2113,"date":"2019-12-04T04:24:26","date_gmt":"2019-12-04T04:24:26","guid":{"rendered":"http:\/\/kusuaks7\/?p=1718"},"modified":"2024-02-14T14:17:58","modified_gmt":"2024-02-14T14:17:58","slug":"ten-steps-to-set-up-your-python-project-for-success","status":"publish","type":"post","link":"https:\/\/www.experfy.com\/blog\/bigdata-cloud\/ten-steps-to-set-up-your-python-project-for-success\/","title":{"rendered":"Ten Steps to Set Up Your Python Project for Success"},"content":{"rendered":"\t\t
\n\t\t\t\t\t\t
\n\t\t\t\t\t\t
\n\t\t\t\t\t
\n\t\t\t
\n\t\t\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t

How to add tests, CI, code coverage, and more<\/h2><\/h2>\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t\t\t\t\t

In this guide we\u2019ll walk through adding tests and integrations to speed development and improve code quality and consistency. If don\u2019t have a basic working Python package, check out my guide to building one and then meet right back here.<\/p>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t

\n\t\t\t\t
\n\t\t\t\t\t\t\t\t\t
    \n \t
  1. Install Black<\/li>\n \t
  2. Create .pycache<\/li>\n \t
  3. Install pytest<\/li>\n \t
  4. Create Tests<\/li>\n \t
  5. Sign up for Travis CI and Configure<\/li>\n \t
  6. Create .travis.yaml<\/li>\n \t
  7. Test Travis CI<\/li>\n \t
  8. Add Code Coverage<\/li>\n \t
  9. Add Coveralls<\/li>\n \t
  10. Add PyUp<\/li>\n<\/ol>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t
    \n\t\t\t\t
    \n\t\t\t\t\t\t\t\t\t

    This guide is for macOS with Python 3.7. Everything works as of early 2019, but things change fast.<\/p>\n

    We\u2019ve got work to do. Let\u2019s hop to it!<\/p>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t

    \n\t\t\t\t
    \n\t\t\t\t\t

    Step 1: Install Black<\/h1><\/h1>\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t
    \n\t\t\t\t
    \n\t\t\t\t\t\t\t\t\t\t\t\t\t\t\t\"\"\t\t\t\t\t\t\t\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t
    \n\t\t\t\t
    \n\t\t\t\t\t\t\t\t\t

    Your package code should follows common style conventions.\u00a0Black<\/a>\u00a0is a Python package that automatically formats your code for you so that it meet\u00a0PEP 8<\/a>. Black is relatively new and already has over a million downloads. Using it has quickly become a best practice in Python coding.\u00a0Here\u2019s a good guide<\/a>\u00a0to Black.<\/p>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t

    \n\t\t\t\t
    \n\t\t\t\t\t\t\t\t\t

    I\u2019m using Atom for my editor, so I added the\u00a0Python-Black\u00a0<\/em>package to Atom\u00a0\u2014\u00a0<\/em>install info is\u00a0here<\/a>. Now Atom will reformat your code when you save your file.<\/p>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t

    \n\t\t\t\t
    \n\t\t\t\t\t\t\t\t\t

    While we\u2019re at it, let\u2019s add Black to the development environment for our collaborators. Eventually, anyone who works on the project will adhere to the same style guide, or else their pull request won\u2019t be accepted.<\/p>\n

    Add\u00a0black==18.9b0<\/code>\u00a0to the next empty line of requirements_dev.txt and run\u00a0pip install -r requirements_dev.txt<\/code>.<\/p>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t

    \n\t\t\t\t
    \n\t\t\t\t\t\t\t\t\t

    Black makes 88 characters the default max line length. Some guides and programs require 79 characters, e.g.\u00a0Sphinx style guide<\/a>. In the Black Atom, package you can set the max length.<\/p>\n

    Now that we\u2019re set up to save time writing code, let\u2019s save time pushing our app to PyPI.<\/p>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t

    \n\t\t\t\t
    \n\t\t\t\t\t

    Step 2: Create .pypirc<\/h1><\/h2>\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t
    \n\t\t\t\t
    \n\t\t\t\t\t\t\t\t\t

    When we use\u00a0twine<\/a>\u00a0to push our builds to TestPyPI and PyPI we need to enter our login info manually. See\u00a0my previous article<\/a>\u00a0if you aren\u2019t familiar with twine. Let\u2019s automate that process.<\/p>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t

    \n\t\t\t\t
    \n\t\t\t\t\t\t\t\t\t

    Twine will look for a file named\u00a0.pypirc<\/em>\u00a0in our home directory. It will grab our url, login, and password when uploading our file.<\/p>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t

    \n\t\t\t\t
    \n\t\t\t\t\t\t\t\t\t

    Create your\u00a0.pypirc<\/em>\u00a0file in your home directory with:<\/p>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t

    \n\t\t\t\t
    \n\t\t\t\t\t\t\t\t\t

    touch ~\/.pypirc<\/code><\/p>\n

    Add the following contents to your\u00a0.pypirc<\/em>\u00a0file:<\/p>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t

    \n\t\t\t\t
    \n\t\t\t\t\t\t\t\t\t

    Replace with your username and passwords. Make sure to save this file in your home directory and not your current working directory. If you want to make sure other users are on your machine can\u2019t access this file, you can change its permissions from the command line:<\/p>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t

    \n\t\t\t\t
    \n\t\t\t\t\t\t\t\t\t

    chmod 600 ~\/.pypirc<\/code><\/p>\n

    Now you can upload your package to TestPyPI with the following command:<\/p>\n

    twine upload -r testpypi dist\/*<\/code><\/p>\n

    Upload to the real PyPI with this command:<\/p>\n

    twine upload dist\/*<\/code><\/p>\n

    No more usernames and passwords to enter. Isn\u2019t that nice?<\/p>\n

    Now let\u2019s add some tests to make sure our package works.<\/p>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t

    \n\t\t\t\t
    \n\t\t\t\t\t

    Step 3: Install and Configure pytest<\/h1><\/h1>\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t
    \n\t\t\t\t
    \n\t\t\t\t\t\t\t\t\t

    Pytest<\/a>\u00a0is the most popular, easy-to-use library for testing your Python code. In this example, we\u2019ll add simple tests to our project. If you want to learn about pytest,\u00a0here\u2019s<\/a>\u00a0a nice intro tutorial. Another good guide is\u00a0Brian Okken<\/a>\u2019s book,\u00a0Python Testing with Pytest<\/a>.<\/p>\n\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t

    \n\t\t\t\t
    \n\t\t\t\t\t\t\t\t\t

    Add pytest to your requirements_dev.txt file with<\/p>\n

    pytest==4.3.0<\/code><\/p>\n

    Run\u00a0pip install requirements_dev.txt<\/code><\/p>\n

    Then run the following so that pytest can find your package:<\/p>\n

    pip install -e .<\/code><\/p>\n

    If you deactivate your virtual environment, you\u2019ll need to run both pip commands again to run your tests.<\/p>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t

    \n\t\t\t\t
    \n\t\t\t\t\t\t\t\t\t\t\t\t\t\t\t\"\"\t\t\t\t\t\t\t\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t
    \n\t\t\t\t
    \n\t\t\t\t\t

    Step 4: Create Tests<\/h1><\/h1>\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t
    \n\t\t\t\t
    \n\t\t\t\t\t\t\t\t\t

    Add a\u00a0tests<\/em>\u00a0folder in the top level of your project. Add a file inside it calledtest_your_package_name.py<\/code>. My file is named\u00a0test_notebookc.py<\/code>. Starting the file with\u00a0test_<\/code>\u00a0makes it automatically discoverable by pytest.<\/p>\n

    In\u00a0test_notebookc.py<\/code>\u00a0I added the following test to check whether the correct name prints as part of the function output. Modify to fit your own file and function names.<\/p>\n

    What\u2019s going on here?<\/p>\n

    We first import our module. Then we create a function with\u00a0test_my_function_name<\/code>. This naming convention is helpful for other people and the code coverage package we\u2019ll add soon.<\/p>\n

    Then we call our function,\u00a0convert<\/em>, with\u00a0\u201cJill\u201d<\/em>\u00a0as the argument. Then we capture the output. As a reminder, our\u00a0convert<\/em>\u00a0function is extremely basic \u2014 it takes the parameter\u00a0my_name<\/em>\u00a0and outputs a line:<\/p>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t

    \n\t\t\t\t
    \n\t\t\t\t\t\t\t\t\t

    print(f\u201dI\u2019ll convert a notebook for you some day, {my_name}.\u201d)<\/code><\/p>\n

    Pytest checks to see if the string \u201cJall\u201d is in the output. It shouldn\u2019t be present, because we passed in \u201cJill\u201d. See the pytest documentation on capturing output\u00a0here<\/a>.<\/p>\n

    Run your test by entering\u00a0pytest<\/code>\u00a0on the command line. Your test should fail with red text.<\/p>\n\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t

    \n\t\t\t\t
    \n\t\t\t\t\t\t\t\t\t\t\t\t\t\t\t\"\"\t\t\t\t\t\t\t\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t
    \n\t\t\t\t
    \n\t\t\t\t\t\t\t\t\t

    It\u2019s good practice to make sure your tests fail when they should. Don\u2019t just write them so they are green right away. Otherwise, your tests might not be testing what you think they are.<\/p>\n

    After we have a failing test we can change our expected output from\u00a0Jall<\/code>\u00a0to\u00a0Jill<\/code>, and our tests should pass in green.<\/p>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t

    \n\t\t\t\t
    \n\t\t\t\t\t\t\t\t\t\t\t\t\t\t\t\"\"\t\t\t\t\t\t\t\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t
    \n\t\t\t\t
    \n\t\t\t\t\t\t\t\t\t

    Yep, all good. Now we have a test that ensures that when someone passes a string value to our function, that string is printed.<\/p>\n

    Let\u2019s add a test to check that only a string has been passed to our function. If anything other than a string is passed, then a TypeError should be raised.\u00a0Here\u2019s a good guide<\/a>\u00a0on exceptions and error handling in Python.<\/p>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t

    \n\t\t\t\t
    \n\t\t\t\t\t\t\t\t\t

    When we write the test before we write the code that makes the test pass, we\u2019re doing test-driven development (TDD). TDD is a proven method to write code with fewer errors.\u00a0Here\u2019s a nice article<\/a>\u00a0on TDD.<\/p>\n

    Let\u2019s try something different this time. As an exercise, add your own test and code to ensure only a string can be passed as the argument to\u00a0convert()<\/code>. Hint: integers, lists, and dicts get type-converted to strings. Follow me on Twitter @discdiver and I\u2019ll post the solution there.<\/p>\n

    After we have passing tests we are ready to integrate our package with a CI service.<\/p>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t

    \n\t\t\t\t
    \n\t\t\t\t\t

    Step 5: Sign up for Travis CI and Configure<\/h1><\/h1>\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t
    \n\t\t\t\t
    \n\t\t\t\t\t\t\t\t\t\t\t\t\t\t\t\"\"\t\t\t\t\t\t\t\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t
    \n\t\t\t\t
    \n\t\t\t\t\t\t\t\t\t

    Travis CI<\/a>\u00a0is a \u201chosted, distributed continuous integration service used to build and test software projects\u201d. It was recently acquired by\u00a0Idera<\/a>. There are other CI options, but Travis CI is popular, free for open-source, and well-documented.<\/p>\n

    Travis CI makes it easier to ensure that only code that passes your tests and standards is integrated into your project. Learn more about Travis CI\u00a0here<\/a>\u00a0and more about continuous integration\u00a0here<\/a>.<\/p>\n

    Sign up for an account at\u00a0https:\/\/travis-ci.org\/<\/a>. Click on the\u00a0Review and add your authorized organizations<\/em>\u00a0link from your Travis CI profile page. You\u2019ll be prompted for your GitHub password. Click\u00a0Grant<\/em>\u00a0next to your organization access.<\/p>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t

    \n\t\t\t\t
    \n\t\t\t\t\t\t\t\t\t\t\t\t\t\t\t\"\"\t\t\t\t\t\t\t\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t
    \n\t\t\t\t
    \n\t\t\t\t\t\t\t\t\t

    I had to sync my account for\u00a0notebooktoall<\/em>\u00a0to show as an organization and for the\u00a0notebookc<\/em>\u00a0repository to appear. It often takes a minute or more for data to start flowing. Then toggle your repo to\u00a0on<\/em>.<\/p>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t

    \n\t\t\t\t
    \n\t\t\t\t\t\t\t\t\t\t\t\t\t\t\t\"\"\t\t\t\t\t\t\t\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t
    \n\t\t\t\t
    \n\t\t\t\t\t\t\t\t\t

    Click on\u00a0settings<\/em>. You can choose whether you want Travis to build on pushed pull requests and\/or on pushed branches.<\/p>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t

    \n\t\t\t\t
    \n\t\t\t\t\t\t\t\t\t\t\t\t\t\t\t\"\"\t\t\t\t\t\t\t\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t
    \n\t\t\t\t
    \n\t\t\t\t\t\t\t\t\t

    Now we need to configure a file locally so that Travis will build for each pull request.<\/p>\n\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t

    \n\t\t\t\t
    \n\t\t\t\t\t

    Step 6: Create .travis.yml<\/h1><\/h1>\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t
    \n\t\t\t\t
    \n\t\t\t\t\t\t\t\t\t

    In the top level of your project folder, add a .travis.yml<\/em>\u00a0file with these contents:<\/p>\n

    dist: xenial<\/code>\u00a0is needed to specify that Travis should use Ubuntu Xenial 16.04 for its virtual environment. Xenial must be specified for testing Python 3.7 code. More info\u00a0here<\/a>.<\/p>\n

    Different versions of Python can be specified for testing. We\u2019ll get into that topic in a future article. Follow\u00a0me<\/a>\u00a0to make sure you don\u2019t miss it!<\/p>\n

    The\u00a0install<\/code>\u00a0section ensures our packages for development are installed.\u00a0pip install -e .<\/code>\u00a0installs your package as a wheel into Travis\u2019s virtual environment. Then Travis will find your package when it runs pytest.<\/p>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t

    \n\t\t\t\t
    \n\t\t\t\t\t

    Step 7: Test Travis CI<\/h1><\/h1>\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t
    \n\t\t\t\t
    \n\t\t\t\t\t\t\t\t\t

    Commit your changes, push to GitHub, make a PR. Travis should start to run automatically within a few seconds.<\/p>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t

    \n\t\t\t\t
    \n\t\t\t\t\t\t\t\t\t\t\t\t\t\t\t\"\"\t\t\t\t\t\t\t\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t
    \n\t\t\t\t
    \n\t\t\t\t\t\t\t\t\t

    Here\u2019s what Travis is doing.<\/p>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t

    \n\t\t\t\t
    \n\t\t\t\t\t\t\t\t\t\t\t\t\t\t\t\"\"\t\t\t\t\t\t\t\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t
    \n\t\t\t\t
    \n\t\t\t\t\t\t\t\t\t

    From travis.ci<\/span><\/p>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t

    \n\t\t\t\t
    \n\t\t\t\t\t\t\t\t\t

    Travis will tell you if your PR fails.<\/p>\n

    Note that if a pull request fails, you can push to the same branch and Travis automatically reruns.<\/p>\n

    Go to your repo\u2019s page on Travis and have a look around. There\u2019s lots of info on Travis about your builds. You\u2019ll probably be visiting this site a good bit in the future trying to figure out why your build didn\u2019t pass.<\/p>\n

    Assuming everything is green, you\u2019re good to go!<\/p>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t

    \n\t\t\t\t
    \n\t\t\t\t\t\t\t\t\t\t\t\t\t\t\t\"\"\t\t\t\t\t\t\t\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t
    \n\t\t\t\t
    \n\t\t\t\t\t\t\t\t\t

    If you don\u2019t see any red or green, click on the\u00a0More options\u00a0<\/em>menu and select\u00a0Requests<\/em>\u00a0from the dropdown. If you see red, have a look at the error messages. If you see the error\u00a0Build config file is required,\u00a0<\/em>then Travis isn\u2019t finding your .travis.yml file on GitHub. Make sure it\u2019s in your GitHub repo.<\/p>\n

    Travis sends you emails to let you know when a build fails and when a failed build has been fixed.<\/p>\n

    Remember that you can keep pushing your commits to an open PR and Travis will rerun automatically.<\/p>\n

    Let\u2019s see just how much of our code has test coverage.<\/p>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t

    \n\t\t\t\t
    \n\t\t\t\t\t

    Step 8: Add Code Coverage<\/h1><\/h1>\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t
    \n\t\t\t\t
    \n\t\t\t\t\t\t\t\t\t

    A code coverage report shows you what percentage of your code has at least some test coverage. We\u2019ll add the\u00a0pytest-cov<\/a>\u00a0package to create a report.<\/p>\n

    Add the following line to\u00a0requirements_dev.txt<\/em>:<\/p>\n

    pytest-cov==2.6.1<\/code><\/p>\n

    Run with\u00a0pytest --cov=my_project_name<\/code><\/p>\n

    My output of\u00a0pytest --cov=notebookc<\/code>\u00a0looks like this:<\/p>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t

    \n\t\t\t\t
    \n\t\t\t\t\t\t\t\t\t\t\t\t\t\t\t\"\"\t\t\t\t\t\t\t\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t
    \n\t\t\t\t
    \n\t\t\t\t\t\t\t\t\t

    Sweet, all our code is covered! When you only have a few lines that\u2019s not a high bar. \u00a0But we don\u2019t need to tell the world that \u2014 let\u2019s show them that we\u2019ve got coverage!<\/p>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t

    \n\t\t\t\t
    \n\t\t\t\t\t

    Step 9: Add Coveralls<\/h1><\/h1>\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t
    \n\t\t\t\t
    \n\t\t\t\t\t\t\t\t\t

    Coveralls provides a history of your code coverage for all the world to see.<\/p>\n\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t

    \n\t\t\t\t
    \n\t\t\t\t\t\t\t\t\t\t\t\t\t\t\t\"\"\t\t\t\t\t\t\t\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t
    \n\t\t\t\t
    \n\t\t\t\t\t\t\t\t\t

    Head over to\u00a0https:\/\/coveralls.io\/<\/a>\u00a0and signup for an account using your GitHub credentials. Add your organization and toggle on your repo when it appears.<\/p>\n

    In\u00a0requirements_dev.txt<\/em>\u00a0add\u00a0coveralls==1.6.0<\/code>. Your\u00a0requirements_dev.txt\u00a0<\/em>should now look like this:<\/p>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t

    \n\t\t\t\t
    \n\t\t\t\t\t\t\t\t\t

    Alter your\u00a0.travis.yml<\/em>\u00a0file so it looks like the following (substituting your package name):<\/p>\n

    Now when Travis builds your project, it will install the necessary packages, run your tests, and create a coverage report. Then it sends the coverage report to coveralls.<\/p>\n

    Commit, push to GitHub, and watch the magic happen. It can take a few minutes for your coverage report to flow, so be patient.<\/p>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t

    \n\t\t\t\t
    \n\t\t\t\t\t\t\t\t\t\t\t\t\t\t\t\"\"\t\t\t\t\t\t\t\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t
    \n\t\t\t\t
    \n\t\t\t\t\t\t\t\t\t

    Now coveralls shows in your PR checks. Cool!<\/p>\n

    Over on the Coveralls webpage, we should show 100% coverage.<\/p>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t

    \n\t\t\t\t
    \n\t\t\t\t\t\t\t\t\t\t\t\t\t\t\t\"\"\t\t\t\t\t\t\t\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t
    \n\t\t\t\t
    \n\t\t\t\t\t\t\t\t\t

    Alright, let\u2019s add one more tool to our belt.<\/p>\n\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t

    \n\t\t\t\t
    \n\t\t\t\t\t

    Step 10: Add PyUp<\/h1><\/h1>\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t<\/section>\n\t\t\t\t
    \n\t\t\t\t\t\t
    \n\t\t\t\t\t
    \n\t\t\t
    \n\t\t\t\t\t\t
    \n\t\t\t\t
    \n\t\t\t\t\t\t\t\t\t

    PyUp.io lets you know when package dependencies are out of date or have security vulnerabilities. It automatically makes a pull request to update the package on GitHub.<\/p>\n

    Go to\u00a0https:\/\/pyup.io\/<\/a>, register through GitHub, and connect your organization.<\/p>\n

    When you add your repo, I suggest you toggle your update schedule to every week. Then you won\u2019t get lots of pull requests if you have a bunch of package dependencies.<\/p>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t

    \n\t\t\t\t
    \n\t\t\t\t\t\t\t\t\t\t\t\t\t\t\t\"\"\t\t\t\t\t\t\t\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t
    \n\t\t\t\t
    \n\t\t\t\t\t\t\t\t\t

    Here\u2019s an example of a repository on PyUp that shows some out of date packages.<\/p>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t

    \n\t\t\t\t
    \n\t\t\t\t\t\t\t\t\t\t\t\t\t\t\t\"\"\t\t\t\t\t\t\t\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t
    \n\t\t\t\t
    \n\t\t\t\t\t\t\t\t\t

    Now you\u2019ll know when a package is updated \u2014 and knowing is half the battle. Automated pull requests must be the other half, right?<\/p>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t

    \n\t\t\t\t
    \n\t\t\t\t\t

    Wrap<\/h1>\n<\/h2>\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t
    \n\t\t\t\t
    \n\t\t\t\t\t\t\t\t\t

    In this article, you\u2019ve learned how to add and configure Black, pytest, Travis CI, Coveralls, and PyUp. We\u2019ve set the stage for more secure code with more consistent style.<\/p>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t<\/section>\n\t\t\t\t<\/div>\n\t\t","protected":false},"excerpt":{"rendered":"

    Python is an interpreted, high-level, general-purpose programming language. Python’s design philosophy emphasizes code readability with its notable use of significant whitespace.  In this article, you will learn how to add and configure Black, pytest, Travis CI, Coveralls, and PyUp. We’ve set the stage for more secure code with more consistent style. Here’s our ten-step plan for this article. This guide is for macOS with Python 3.7. Everything works as of early 2019, but things change fast.<\/p>\n","protected":false},"author":369,"featured_media":2960,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"content-type":"","footnotes":""},"categories":[187],"tags":[94],"ppma_author":[2134],"class_list":["post-2113","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-bigdata-cloud","tag-data-science"],"authors":[{"term_id":2134,"user_id":369,"is_guest":0,"slug":"jeff-hale","display_name":"Jeff Hale","avatar_url":"https:\/\/secure.gravatar.com\/avatar\/?s=96&d=mm&r=g","user_url":"","last_name":"Hale","first_name":"Jeff","job_title":"","description":"Jeff Hale is a co-founder of Rebel Desk, where he oversees technology, finance, and operations for this company. He is an experienced entrepreneur who has managed technology, operations, and finances for several companies. "}],"_links":{"self":[{"href":"https:\/\/www.experfy.com\/blog\/wp-json\/wp\/v2\/posts\/2113","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.experfy.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.experfy.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.experfy.com\/blog\/wp-json\/wp\/v2\/users\/369"}],"replies":[{"embeddable":true,"href":"https:\/\/www.experfy.com\/blog\/wp-json\/wp\/v2\/comments?post=2113"}],"version-history":[{"count":5,"href":"https:\/\/www.experfy.com\/blog\/wp-json\/wp\/v2\/posts\/2113\/revisions"}],"predecessor-version":[{"id":36004,"href":"https:\/\/www.experfy.com\/blog\/wp-json\/wp\/v2\/posts\/2113\/revisions\/36004"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.experfy.com\/blog\/wp-json\/wp\/v2\/media\/2960"}],"wp:attachment":[{"href":"https:\/\/www.experfy.com\/blog\/wp-json\/wp\/v2\/media?parent=2113"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.experfy.com\/blog\/wp-json\/wp\/v2\/categories?post=2113"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.experfy.com\/blog\/wp-json\/wp\/v2\/tags?post=2113"},{"taxonomy":"author","embeddable":true,"href":"https:\/\/www.experfy.com\/blog\/wp-json\/wp\/v2\/ppma_author?post=2113"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}