Conversation
Bumps [isort](https://github.com/pycqa/isort) from 5.10.1 to 5.12.0. - [Release notes](https://github.com/pycqa/isort/releases) - [Changelog](https://github.com/PyCQA/isort/blob/main/CHANGELOG.md) - [Commits](PyCQA/isort@5.10.1...5.12.0) --- updated-dependencies: - dependency-name: isort dependency-type: indirect update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com>
|
We cannot use this until we drop Python 3.7 |
|
OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting If you change your mind, just re-open this PR and I'll resolve any conflicts on it. |
|
Which does not make sense btw. Other projects still use Python 3.7 and it worked fine. |
|
:( yeah They should at least wait until 3.7 EOL (06/07) |
|
Sorry I meant that other projects like urllib3 use isort while still supporting Python 3.7 and did not have issues, because they run lint with newer versions of Python. But in our case we don't even use isort for lint, it's just a test dependency because we use pylint in tests. The problem is I don't think the version we have pinned actually builds anymore due to PyCQA/isort#2078! |
|
Oh, my bad! Looking at the PR/linked issue I'm not sure it affects us; we could use isort 3.11.5 if it does, I suppose? |
Bumps isort from 5.10.1 to 5.12.0.
Release notes
Sourced from isort's releases.
... (truncated)
Changelog
Sourced from isort's changelog.
... (truncated)
Commits
e44834bFix changelog / version to a minor bump due to the size of the change82569d9Bump version to 5.11.5e00db96Formatting fixe833931Merge pull request #2078 from jooola/fix_poetry_validation0d219a6fix: poetry pip-shims extras dependencyae0cc1cMerge pull request #1967 from vkomarov-r7/feature/directory-hooks06d8ef5Merge pull request #1948 from timgates42/bugfix_typo_determination0c8a8b8Merge pull request #2076 from marksmayo/main5b63fbaClean upa0cb1b8Fix tmuxp testDependabot 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 rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot mergewill merge this PR after your CI passes on it@dependabot squash and mergewill squash and merge this PR after your CI passes on it@dependabot cancel mergewill cancel a previously requested merge and block automerging@dependabot reopenwill reopen this PR if it is closed@dependabot closewill close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually@dependabot ignore this major versionwill 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 versionwill 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 dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)