Update setuptools to 20.10.1

[pyup-bot]

There's a new version of setuptools available.
You are currently using 20.3. I have updated it to 20.10.1

Changelog

20.10.0

---

• 553: egg_info section is now generated in a
  deterministic order, matching the order generated
  by earlier versions of Python. Except on Python 2.6,
  order is preserved when existing settings are present.
• 556: Update to Packaging 16.7, restoring support
  for deprecated python_implmentation marker.
• 555: Upload command now prompts for a password
  when uploading to PyPI (or other repository) if no
  password is present in .pypirc or in the keyring.

20.9.0

---

• 548: Update certify version to 2016.2.28
• 545: Safely handle deletion of non-zip eggs in rotate
  command.

20.8.1

---

• Issue 544: Fix issue with extra environment marker
  processing in WorkingSet due to refactor in v20.7.0.

20.8.0

---

• Issue 543: Re-release so that latest release doesn't
  cause déjà vu with distribute and setuptools 0.7 in
  older environments.

20.7.0

---

• Refactored extra enviroment marker processing
  in WorkingSet.
• Issue 533: Fixed intermittent test failures.
• Issue 536: In msvc9_support, trap additional exceptions
  that might occur when importing
  distutils.msvc9compiler in mingw environments.
• Issue 537: Provide better context when package
  metadata fails to decode in UTF-8.

20.6.8

---

• Issue 523: Restored support for environment markers,
  now honoring 'extra' environment markers.

20.6.7

---

• Issue 523: Disabled support for environment markers
  introduced in v20.5.

20.6.6

---

• Issue 503: Restore support for PEP 345 environment
  markers by updating to Packaging 16.6.

20.6.0

---

• New release process that relies on
  bumpversion <https://github.com/peritus/bumpversion>_
  and Travis CI for continuous deployment.
• Project versioning semantics now follow
  semver <https://semver.org>_ precisely.
  The 'v' prefix on version numbers now also allows
  version numbers to be referenced in the changelog,
  e.g. https://pythonhosted.org/setuptools/history.htmlv20-6-0.

20.5

---

• BB Pull Request 185: Add support for environment markers
  in requirements in install_requires, setup_requires,
  tests_require as well as adding a test for the existing
  extra_requires machinery.

20.4

---

• Issue 422: Moved hosting to
  Github <https://github.com/pypa/setuptools>_
  from Bitbucket <https://bitbucket.org/pypa/setuptools>_.
  Issues have been migrated, though all issues and comments
  are attributed to bb-migration. So if you have a particular
  issue or issues to which you've been subscribed, you will
  want to "watch" the equivalent issue in Github.
  The Bitbucket project will be retained for the indefinite
  future, but Github now hosts the canonical project repository.

20.3.1

---

• Issue 519: Remove import hook when reloading the
  pkg_resources module.
• BB Pull Request 184: Update documentation in pkg_resources
  around new Requirement implementation.

Happy merging! 🤖

[codecov-io]

Current coverage is 93.76%

Merging #45 into master will not change coverage

@@             master        #45   diff @@
==========================================
  Files            14         14          
  Lines          1410       1410          
  Methods           0          0          
  Messages          0          0          
  Branches          0          0          
==========================================
  Hits           1322       1322          
  Misses           88         88          
  Partials          0          0          

Powered by Codecov. Last updated by edae788

[luzfcb]

@jayfk I have got to say this it is so beautiful. it's getting good.

Questions: the bot automatically closed the not-merged previous pull-request in favor of this?
You have any plans, in the distant future, to support gitlab and perhaps gitlab private servers?

[jayfk]

Questions: the bot automatically closed the not-merged previous pull-request in favor of this?

Yes! It auto-closes the previous pull request if

• It is not merged
• Is not closed
• Has no commits (except the bot commit)

You can read more about that here: https://github.com/pyupio/pyup/blob/master/pyup/bot.py#L130-L159

You have any plans, in the distant future, to support gitlab and perhaps gitlab private servers?

Yeah, absolutely. The code is designed to make the git provider easily exchangeable. It's on the roadmap, but I can't promise anything just yet. :)

[pyup-bot]

Closing this in favor of #46