pyup: Scheduled weekly dependency update for week 33

[pyup-bot]

Update pip from 19.2.1 to 19.2.2.

Changelog

19.2.2

===================

Bug Fixes
---------

- Fix handling of tokens (single part credentials) in URLs. (`6795 <https://github.com/pypa/pip/issues/6795>`_)
- Fix a regression that caused ``~`` expansion not to occur in ``--find-links``
paths. (`6804 <https://github.com/pypa/pip/issues/6804>`_)

Links

• PyPI: https://pypi.org/project/pip
• Changelog: https://pyup.io/changelogs/pip/
• Homepage: https://pip.pypa.io/

Update virtualenv from 16.7.2 to 16.7.3.

Changelog

16.7.3

--------------------

Bugfixes
^^^^^^^^

- upgrade pip from ``19.1.1`` to ``19.2.2`` and setuptools from ``41.0.1`` to ``41.1.0`` (`1404 <https://github.com/pypa/virtualenv/issues/1404>`_)

Links

• PyPI: https://pypi.org/project/virtualenv
• Changelog: https://pyup.io/changelogs/virtualenv/
• Homepage: https://virtualenv.pypa.io/

Update GitPython from 2.1.13 to 3.0.1.

Changelog

3.0.1

=============================================

* Fix a `performance regression <https://github.com/gitpython-developers/GitPython/issues/906>`_ which could make certain workloads 50% slower
* Add `currently_rebasing_on` method on `Repo`, see `the PR <https://github.com/gitpython-developers/GitPython/pull/903/filesdiff-c276fc3c4df38382ec884e59657b869dR1065>`_
* Fix incorrect `requirements.txt` which could lead to broken installations, see this `issue <https://github.com/gitpython-developers/GitPython/issues/908>`_ for details.

3.0.0 - Remove Python 2 support
===============================

Motivation for this is a patch which improves unicode handling when dealing with filesystem paths.
Python 2 compatibility was introduced to deal with differences, and I thought it would be a good idea
to 'just' drop support right now, mere 5 months away from the official maintenance stop of python 2.7.

The underlying motivation clearly is my anger when thinking python and unicode, which was a hassle from the
start, at least in a codebase as old as GitPython, which totally doesn't handle encodings correctly in many cases.

Having migrated to using `Rust` exclusively for tooling, I still see that correct handling of encodings isn't entirely
trivial, but at least `Rust` makes clear what has to be done at compile time, allowing to write software that is pretty
much guaranteed to work once it compiles.

Again, my apologies if removing Python 2 support caused inconveniences, please see release 2.1.13 which returns it.

see the following for (most) details:
https://github.com/gitpython-developers/gitpython/milestone/27?closed=1

or run have a look at the difference between tags v2.1.12 and v3.0.0:
https://github.com/gitpython-developers/GitPython/compare/2.1.12...3.0.0.

2.1.13 - Bring back Python 2.7 support
======================================

My apologies for any inconvenience this may have caused. Following semver, backward incompatible changes
will be introduced in a minor version.

Links

• PyPI: https://pypi.org/project/gitpython
• Changelog: https://pyup.io/changelogs/gitpython/
• Repo: https://github.com/gitpython-developers/GitPython
• Docs: https://pythonhosted.org/GitPython/

Update lxml from 4.4.0 to 4.4.1.

Changelog

4.4.1

==================

Bugs fixed
----------

* LP1838252: The order of an OrderedDict was lost in 4.4.0 when passing it as
attrib mapping during element creation.

* LP1838521: The package metadata now lists the supported Python versions.

Links

• PyPI: https://pypi.org/project/lxml
• Changelog: https://pyup.io/changelogs/lxml/
• Homepage: http://lxml.de/

Update stripe from 2.33.0 to 2.35.0.

Changelog

2.35.0

* [607](https://github.com/stripe/stripe-python/pull/607) Add `SubscriptionItem.create_usage_record` method

2.34.0

* [604](https://github.com/stripe/stripe-python/pull/604) Remove subscription schedule revisions
- This is technically a breaking change. We've chosen to release it as a minor vesion bump because the associated API is unused.

2.33.2

* [601](https://github.com/stripe/stripe-python/pull/601) Add support for passing full objects instead of IDs to custom methods
* [603](https://github.com/stripe/stripe-python/pull/603) Bump vendored six to latest version

2.33.1

* [599](https://github.com/stripe/stripe-python/pull/599) Fix `del` statement to not raise `KeyError`

Links

• PyPI: https://pypi.org/project/stripe
• Changelog: https://pyup.io/changelogs/stripe/
• Repo: https://github.com/stripe/stripe-python

Update recommonmark from 0.5.0 to 0.6.0.

Changelog

Links

• PyPI: https://pypi.org/project/recommonmark
• Changelog: https://pyup.io/changelogs/recommonmark/
• Repo: https://github.com/rtfd/recommonmark

Update execnet from 1.6.1 to 1.7.0.

Changelog

1.7.0

------------------

* `102 <https://github.com/pytest-dev/execnet/pull/102>`__: Show paths in stack traces
generated by ``remote_exec()``.

* `100 <https://github.com/pytest-dev/execnet/pull/100>`__: Fix flaky hangs in ``workerpool.waitall``.

Links

• PyPI: https://pypi.org/project/execnet
• Changelog: https://pyup.io/changelogs/execnet/
• Docs: https://execnet.readthedocs.io/en/latest/

Update yamale from 1.10.0 to 1.10.1.

The bot wasn't able to find a changelog for this release. Got an idea?

Links

• PyPI: https://pypi.org/project/yamale
• Changelog: https://pyup.io/changelogs/yamale/
• Repo: https://github.com/23andMe/Yamale

[stsewd]

This is in replace of #6067 (they are the same actually)

[stsewd]

Merged in #6067