-
The "old" Tox had a feature that was helpful to understand (and reproduce) builds: It printed out the packages and their versions that were installed in the newly created virtualenvs. Having installed packages printed out helps to catch test setup mistakes and understand certain execution errors. With the current implementation Tox now doesn't do that anymore, neither with the default verbosity nor any other increased level of verbosity. Interestingly though, in general the verbosity of Tox has increased for the default verbosity. Was that a conscious choice to omit printing out the list of packages Tox gets installed? Are there any plans to build that back in again? |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment
-
Hmmm, I was wrong - at least for the pipeline output. Tox indeed does print out a list of installed packages in pipeline logs (example on GHA), e.g. Run tox -e package
package: install_deps> python -I -m pip install build twine
package: freeze> python -m pip freeze --all
package: bleach==6.0.0,build==0.10.0,certifi==2022.12.7,cffi==1.15.1,charset-normalizer==3.1.0,cryptography==40.0.2,docutils==0.19,idna==3.4,importlib-metadata==6.6.0,jaraco.classes==3.2.3,jeepney==0.8.0,keyring==23.13.1,markdown-it-py==2.2.0,mdurl==0.1.2,more-itertools==9.1.0,packaging==23.1,pip==23.1.2,pkginfo==1.9.6,pycparser==2.21,Pygments==2.15.1,pyproject_hooks==1.0.0,readme-renderer==37.3,requests==2.29.0,requests-toolbelt==1.0.0,rfc3986==2.0.0,rich==13.3.5,SecretStorage==3.3.3,setuptools==67.7.2,six==1.16.0,tomli==2.0.1,twine==4.0.2,urllib3==1.26.15,webencodings==0.5.1,wheel==0.40.0,zipp==3.15.0
package: commands[0]> python -m build
... That behavior is described exactly like this in the configuration section of the Tox documentation. The related code is in |
Beta Was this translation helpful? Give feedback.
Hmmm, I was wrong - at least for the pipeline output. Tox indeed does print out a list of installed packages in pipeline logs (example on GHA), e.g.