PreRelese 20.05.1

[Scitator]

Before submitting

• Was this discussed/approved via a Github issue? (no need for typos and docs improvements)
• Did you read the contribution guide, Pull Request section?
• Did you check the code style? catalyst-make-codestyle && catalyst-check-codestyle (pip install -U catalyst-codestyle).
• Did you make sure to update the docs? We use Google format for all the methods and classes.
• Did you check the docs with make check-docs?
• Did you write any new necessary tests?
• If you made a notable change (that affects users), did you update the CHANGELOG?

Description

Related Issue

Type of Change

• Examples / docs / tutorials / contributors update
• Bug fix (non-breaking change which fixes an issue)
• Improvement (non-breaking change which improves an existing feature)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)

PR review

Anyone in the community is free to review the PR once the tests have passed.
If we didn't discuss your PR in Github issues there's a high chance it will not be merged.

You can use 'Login as guest' to see Teamcity build logs.

[pep8speaks]

Hello @Scitator! Thanks for updating this PR. We checked the lines you've touched for PEP 8 issues, and found:

• In the file tests/_tests_scripts/cv_z_segmentation.py:

Line 43:1: E402 module level import not at top of file

• In the file tests/_tests_scripts/dl_z_classification.py:

Line 20:1: E402 module level import not at top of file
Line 21:1: E402 module level import not at top of file

Comment last updated at 2020-05-23 14:19:30 UTC