-
OVERVIEWThe The following output is available when running the build manually not in github, notice that the
REPRODUCTIONFilestox.ini[tox]
isolated_build = True
envlist = test
requires =
# tox==3.*
# tox-gh-actions==2.*
tox-gh-actions==3.*
[testenv]
extras = dev
commands =
pre-commit run --all-files {posargs} setup.cfg[metadata]
name = test_project
long_description = file: README.md
long_description_content_type = text/markdown
[options]
packages = find_namespace:
setup_requires =
setuptools
[options.extras_require]
dev =
pre-commit
[egg_info]
tag_date = 0 pyproject.toml[build-system]
requires = [
"setuptools",
"wheel",
]
build-backend = "setuptools.build_meta"
[project]
name = "test-project"
requires-python = ">=3.10"
version = "0.0.0"
dynamic = [
"readme",
]
[[project.authors]]
name = "Test"
email = "[email protected]" .pre-commit-config.yamlrepos:
- repo: https://github.com/psf/black
rev: 22.8.0
hooks:
- id: black test_project/init.pyInvocation
Please play with the dependencies at
SUSPECTED CAUSEThe EXPECTED BEHAVIOR
|
Beta Was this translation helpful? Give feedback.
Replies: 3 comments
-
Hello @alonbl, thanks for filing an issue. Let me share the result of my initial investigation. I tried to reproduce the issue on my machine using the given example and I found that we get the same error even when tox-gh-actions is not installed. At this point, I feel this is not an issue with tox-gh-actions. This may be rather an issue with tox 3 -> 4 upgrade or your tox configuration is not compatible with tox v4. |
Beta Was this translation helpful? Give feedback.
-
Oh, I am sorry, I just removed and added the |
Beta Was this translation helpful? Give feedback.
-
@alonbl, no worries at all! |
Beta Was this translation helpful? Give feedback.
Hello @alonbl, thanks for filing an issue. Let me share the result of my initial investigation.
I tried to reproduce the issue on my machine using the given example and I found that we get the same error even when tox-gh-actions is not installed.
At this point, I feel this is not an issue with tox-gh-actions. This may be rather an issue with tox 3 -> 4 upgrade or your tox configuration is not compatible with tox v4.