We should have an evergreen task that collects wheels/eggs from release tasks and uploads them to PyPI using Twine. The automation of the upload to PyPI should ONLY be done if we can configure the release task to only run when manually scheduled - i.e a new tag on the GitHub repo should not automatically trigger a release as this could result in mistakenly releasing something to the PyPI index if a commit gets incorrectly tagged.