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
{{ message }}
This repository was archived by the owner on Aug 15, 2026. It is now read-only.
Repository navigation
This repository was archived by the owner on Aug 15, 2026. It is now read-only.
Vroom fails in non-ANSI terminals with errors about missing color constants #112
If I try to run vroom or its tests in a limited terminal that doesn't support ANSI color codes such as shelling out from gvim, it fails hard with errors about missing color constants:
:!vroom
Traceback (most recent call last):
File "/home/dbarnett/.virtualenvs/py37/bin/vroom", line 5, in <module>
import vroom.__main__
File "/home/dbarnett/.virtualenvs/py37/lib/python3.7/site-packages/vroom/__main__.py", line 9, in <module>
import vroom.output
File "/home/dbarnett/.virtualenvs/py37/lib/python3.7/site-packages/vroom/output.py", line 27, in <module>
STATUS.PASS: vroom.color.GREEN,
AttributeError: module 'vroom.color' has no attribute 'GREEN'
shell returned 1
The problem is that color.py silently falls back to COLORED=False mode if it can't invoke tput to configure those constants, but other parts of the code assume unconditionally that those constants will be defined.
Activity
Fix errors for undefined constants like colors.GREEN in non-ANSI terms
Fix errors for undefined constants like colors.GREEN in non-ANSI terms
Bump version to 0.14.0