Allow strings in impl calls #984
Annotations
4 errors, 15 warnings, and 11 notices
Python pypy-2.7
Process completed with exit code 2.
|
Python pypy-3.7
Process completed with exit code 2.
|
Python pypy-3.6
Process completed with exit code 2.
|
Python pypy-3.9
Process completed with exit code 2.
|
Python 3.6
CPython version >=3.6.0 <3.7.0-0 is not supported by actions/setup-python.
This probably means you are using a deprecated version. If this is not the case, you may suppress the warning setting input "allow-build"
to either "info" or "allow".
|
Upgrade to Trusted Publishing
Trusted Publishers allows publishing packages to PyPI from automated environments like GitHub Actions without needing to use username/password combinations or API tokens to authenticate with PyPI. Read more: https://docs.pypi.org/trusted-publishers
|
Python 2.7
CPython version >=2.7.0 <2.8.0-0 is not supported by actions/setup-python.
This probably means you are using a deprecated version. If this is not the case, you may suppress the warning setting input "allow-build"
to either "info" or "allow".
|
Python 2.7
The support for python 2.7 will be removed on June 19. Related issue: https://github.com/actions/setup-python/issues/672
|
Upgrade to Trusted Publishing
Trusted Publishers allows publishing packages to PyPI from automated environments like GitHub Actions without needing to use username/password combinations or API tokens to authenticate with PyPI. Read more: https://docs.pypi.org/trusted-publishers
|
Upgrade to Trusted Publishing
Trusted Publishers allows publishing packages to PyPI from automated environments like GitHub Actions without needing to use username/password combinations or API tokens to authenticate with PyPI. Read more: https://docs.pypi.org/trusted-publishers
|
Python 3.5
CPython version >=3.5.0 <3.6.0-0 is not supported by actions/setup-python.
This probably means you are using a deprecated version. If this is not the case, you may suppress the warning setting input "allow-build"
to either "info" or "allow".
|
Upgrade to Trusted Publishing
Trusted Publishers allows publishing packages to PyPI from automated environments like GitHub Actions without needing to use username/password combinations or API tokens to authenticate with PyPI. Read more: https://docs.pypi.org/trusted-publishers
|
Upgrade to Trusted Publishing
Trusted Publishers allows publishing packages to PyPI from automated environments like GitHub Actions without needing to use username/password combinations or API tokens to authenticate with PyPI. Read more: https://docs.pypi.org/trusted-publishers
|
Upgrade to Trusted Publishing
Trusted Publishers allows publishing packages to PyPI from automated environments like GitHub Actions without needing to use username/password combinations or API tokens to authenticate with PyPI. Read more: https://docs.pypi.org/trusted-publishers
|
Upgrade to Trusted Publishing
Trusted Publishers allows publishing packages to PyPI from automated environments like GitHub Actions without needing to use username/password combinations or API tokens to authenticate with PyPI. Read more: https://docs.pypi.org/trusted-publishers
|
Upgrade to Trusted Publishing
Trusted Publishers allows publishing packages to PyPI from automated environments like GitHub Actions without needing to use username/password combinations or API tokens to authenticate with PyPI. Read more: https://docs.pypi.org/trusted-publishers
|
Upgrade to Trusted Publishing
Trusted Publishers allows publishing packages to PyPI from automated environments like GitHub Actions without needing to use username/password combinations or API tokens to authenticate with PyPI. Read more: https://docs.pypi.org/trusted-publishers
|
Upgrade to Trusted Publishing
Trusted Publishers allows publishing packages to PyPI from automated environments like GitHub Actions without needing to use username/password combinations or API tokens to authenticate with PyPI. Read more: https://docs.pypi.org/trusted-publishers
|
Upgrade to Trusted Publishing
Trusted Publishers allows publishing packages to PyPI from automated environments like GitHub Actions without needing to use username/password combinations or API tokens to authenticate with PyPI. Read more: https://docs.pypi.org/trusted-publishers
|
Python 3.6
Using a user-provided API token for authentication against https://upload.pypi.org/legacy/
|
Python 2.7
Using a user-provided API token for authentication against https://upload.pypi.org/legacy/
|
Python 3.7
Using a user-provided API token for authentication against https://upload.pypi.org/legacy/
|
Python 3.5
Using a user-provided API token for authentication against https://upload.pypi.org/legacy/
|
Python pypy-3.10
Using a user-provided API token for authentication against https://upload.pypi.org/legacy/
|
Python pypy-3.8
Using a user-provided API token for authentication against https://upload.pypi.org/legacy/
|
Python 3.11
Using a user-provided API token for authentication against https://upload.pypi.org/legacy/
|
Python 3.10
Using a user-provided API token for authentication against https://upload.pypi.org/legacy/
|
Python 3.12
Using a user-provided API token for authentication against https://upload.pypi.org/legacy/
|
Python 3.8
Using a user-provided API token for authentication against https://upload.pypi.org/legacy/
|
Python 3.9
Using a user-provided API token for authentication against https://upload.pypi.org/legacy/
|