You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It appears that the changes added in #749 have the potential to break usage of build when the terminal size cannot be determined.
In our CI pipeline on Buildkite, we call python -m build -w on a python:3.8 Docker container. Since the release of build==1.2.0 this is failing with the following error:
The call to shutil.get_terminal_size().columns is evidently returning zero in this case and, as per the docs, when using Python < 3.11 the default fallback value will not be used.
Changed in version 3.11: The fallback values are also used if os.get_terminal_size() returns zeroes.
While it is possible to work around the issue in our pipeline, I think this scenario should be better handled by build.
The text was updated successfully, but these errors were encountered:
Hi there,
It appears that the changes added in #749 have the potential to break usage of
build
when the terminal size cannot be determined.In our CI pipeline on Buildkite, we call
python -m build -w
on apython:3.8
Docker container. Since the release ofbuild==1.2.0
this is failing with the following error:The call to
shutil.get_terminal_size().columns
is evidently returning zero in this case and, as per the docs, when using Python < 3.11 the defaultfallback
value will not be used.While it is possible to work around the issue in our pipeline, I think this scenario should be better handled by
build
.The text was updated successfully, but these errors were encountered: