Bump pandas from 1.0.1 to 1.1.0 in /python

[dependabot-preview]

Bumps pandas from 1.0.1 to 1.1.0.

Release notes

Sourced from pandas's releases.

Pandas 1.1.0

This is a minor release which includes some new features, bug fixes, and performance improvements. We recommend that all users upgrade to this version.

See the whatsnew for a list of all the changes.

The release can be installed from PyPI

python -m pip install --upgrade pandas==1.1.0

Or from conda-forge

conda install -c conda-forge pandas==1.1.0

Please report any issues with the release candidate on the pandas issue tracker.

Pandas 1.1.0rc0

This is the first release candidate for 1.1.0rc0. If all goes well, we'll release pandas 1.1.0 in about two weeks.

See the whatsnew for a list of all the changes.

The release can be installed from PyPI

python -m pip install --upgrade --pre pandas==1.1.0rc0

Or from conda-forge

conda install -c conda-forge/label/pandas_rc pandas==1.1.0rc0

Please report any issues with the release candidate on the pandas issue tracker.

Pandas 1.0.5

This is a minor bug-fix release in the 1.0.x series and includes some regression fixes and bug fixes. We recommend that all users upgrade to this version.

See the full whatsnew for a list of all the changes.

The release will be available on the defaults and conda-forge channels:

conda install pandas

Or via PyPI:

python3 -m pip install --upgrade pandas

Please report any issues with the release on the pandas issue tracker.

Commits

• d9fff27 RLS: 1.1.0
• 7f3502d DOC: 1.1.0 release date (#35435)
• 6302f7b REGR: revert ExtensionBlock.set to be in-place (#35271)
• 04e9e0a DOC: Fixed formatting and errors in whatsnew v1.1.0 (#35398)
• 8f54d14 Remove leftover partial-result code (#35397)
• 00ea10c Matplotlib 3.3 compatibility fixups (#35393)
• d3343d9 PKG: Set max pin for Cython (#35396)
• 06e2793 Change defaults for rolling/expanding.apply engine kwargs to None (#35374)
• 3e88e17 REGR: MultiIndex Indexing (#35353)
• e673b69 CI: pin matplotlib for doc build (#35358)
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
• @dependabot badge me will comment on this PR with code to add a "Dependabot enabled" badge to your readme

Additionally, you can set the following in the .dependabot/config.yml file in this repo:

• Update frequency
• Out-of-range updates (receive only lockfile updates, if desired)
• Security updates (receive only security updates, if desired)

[seldondev]

Hi @dependabot-preview[bot]. Thanks for your PR.

I'm waiting for a SeldonIO member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the jenkins-x/lighthouse repository.

[axsaucedo]

This seems only used in tests
/ok-to-test

[seldondev]

Mon Aug 3 12:21:25 UTC 2020
The logs for [pr-build] [1] will show after the pipeline context has finished.
https://github.com/SeldonIO/seldon-core/blob/gh-pages/jenkins-x/logs/SeldonIO/seldon-core/PR-2232/1.log

impatient try
jx get build logs SeldonIO/seldon-core/PR-2232 --build=1

[seldondev]

Mon Aug 3 12:22:09 UTC 2020
The logs for [lint] [2] will show after the pipeline context has finished.
https://github.com/SeldonIO/seldon-core/blob/gh-pages/jenkins-x/logs/SeldonIO/seldon-core/PR-2232/2.log

impatient try
jx get build logs SeldonIO/seldon-core/PR-2232 --build=2

[axsaucedo]

/approve

[seldondev]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: axsaucedo

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [axsaucedo]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment