sapling/eden/scm/tests/test-ui-color.py

from __future__ import absolute_import, print_function

import os

from edenscm.mercurial import dispatch, ui as uimod
from hghave import require


# ensure errors aren't buffered
testui = uimod.ui()
testui.pushbuffer()
testui.write(("buffered\n"))
testui.warn(("warning\n"))
testui.write_err("error\n")
print(repr(testui.popbuffer()))

# test dispatch.dispatch with the same ui object
hgrc = open(os.environ["HGRCPATH"], "w")
hgrc.write("[extensions]\n")
hgrc.write("color=\n")
hgrc.close()

ui_ = uimod.ui.load()
ui_.setconfig("ui", "assume-tty", "True")

# we're not interested in the output, so write that to devnull
ui_.fout = open(os.devnull, "wb")

# call some arbitrary command just so we go through
# color's wrapped _runcommand twice.
def runcmd():
    dispatch.dispatch(dispatch.request(["version", "-q"], ui_))


runcmd()
print("colored? %s" % (ui_._colormode is not None))
runcmd()
print("colored? %s" % (ui_._colormode is not None))
tests: make test-ui-color use absolute_import 2016-04-13 22:26:08 +03:00			`from __future__ import absolute_import, print_function`

cleanup: remove unused imports detected by pyflakes 2013-06-13 03:36:58 +04:00			`import os`
codemod: join the auto-formatter party Summary: Turned on the auto formatter. Ran `arc lint --apply-patches --take BLACK */.py`. Then run `arc lint` again so some other autofixers like spellchecker etc. looked at the code base. Manually accept the changes whenever they make sense, or use a workaround (ex. changing "dict()" to "dict constructor") where autofix is false positive. Disabled linters on files that are hard (i18n/polib.py) to fix, or less interesting to fix (hgsubversion tests), or cannot be fixed without breaking OSS build (FBPYTHON4). Conflicted linters (test-check-module-imports.t, part of test-check-code.t, test-check-pyflakes.t) are removed or disabled. Duplicated linters (test-check-pyflakes.t, test-check-pylint.t) are removed. An issue of the auto-formatter is lines are no longer guarnateed to be <= 80 chars. But that seems less important comparing with the benefit auto-formatter provides. As we're here, also remove test-check-py3-compat.t, as it is currently broken if `PYTHON3=/bin/python3` is set. Reviewed By: wez, phillco, simpkins, pkaush, singhsrb Differential Revision: D8173629 fbshipit-source-id: 90e248ae0c5e6eaadbe25520a6ee42d32005621b 2018-05-26 07:34:37 +03:00
codemod: import from the edenscm package Summary: D13853115 adds `edenscm/` to `sys.path` and code still uses `import mercurial`. That has nasty problems if both `import mercurial` and `import edenscm.mercurial` are used, because Python would think `mercurial.foo` and `edenscm.mercurial.foo` are different modules so code like `try: ... except mercurial.error.Foo: ...`, or `isinstance(x, mercurial.foo.Bar)` would fail to handle the `edenscm.mercurial` version. There are also some module-level states (ex. `extensions._extensions`) that would cause trouble if they have multiple versions in a single process. Change imports to use the `edenscm` so ideally the `mercurial` is no longer imported at all. Add checks in extensions.py to catch unexpected extensions importing modules from the old (wrong) locations when running tests. Reviewed By: phillco Differential Revision: D13868981 fbshipit-source-id: f4e2513766957fd81d85407994f7521a08e4de48 2019-01-30 03:25:33 +03:00			`from edenscm.mercurial import dispatch, ui as uimod`
py3: make .py tests continue to run on python 2 Summary: Use sed to convert testutil.ddot requires to hghave. ignore-conflict-markers for test-simplemerge.py Reviewed By: simpkins Differential Revision: D19658355 fbshipit-source-id: afae73eb1e43ead79514dfaf9f911f51ac25972e 2020-01-31 11:16:29 +03:00			`from hghave import require`
mark all tests requiring Python 2 Summary: This diff marks ALL mercurial tests requiring Python 2 feature. After you fixes some tests, simply remove the `py2` feature requirement and that tests will be continuously run after your diff is landed. To bypass this feature requirement, run the tests command with `HGTEST_FORCE_PY2=1`. For example: ``` HGTEST_FORCE_PY2=1 buck test //eden/scm/tests:hg_run_tests ``` or ``` HGTEST_FORCE_PY2=1 python run-tests.py ``` ---- Basically this diff are created with the following commands: ``` $ sed -i 's/import feature\(.\)$/import feature\1\n\nfeature.require(["py2"])/' test--t.py $ sed -i '1s/^/#require py2\n/' test-.t $ ls \| grep -P "^test.(?<\!-t)\.py$" > list && vim -p $(cat list) # manually adding feature requires for these Python tests. ``` (Note: this ignores all push blocking failures!) ignore-conflict-markers Reviewed By: singhsrb Differential Revision: D19655148 fbshipit-source-id: 985e3ccb4010cc559049f1d89f8909bc2d9b5e20 2020-01-31 05:40:49 +03:00

color: call correct superclass method in write_err Without this fix, any calls to write_err would go to stdout instead of stderr, and calls during pushbuffer would cause unpack ValueErrors on popbuffer. 2010-08-02 18:48:31 +04:00			`# ensure errors aren't buffered`
color: drop the 'colorui' class Now that all logics formally bared by 'colorui' have been moved to the main ui class, that class is empty and can be dropped. As a nice side effect we can get rid of the baroque Initialization associated to it. There was much rejoicing. 2017-02-20 14:42:35 +03:00			`testui = uimod.ui()`
color: call correct superclass method in write_err Without this fix, any calls to write_err would go to stdout instead of stderr, and calls during pushbuffer would cause unpack ValueErrors on popbuffer. 2010-08-02 18:48:31 +04:00			`testui.pushbuffer()`
codemod: join the auto-formatter party Summary: Turned on the auto formatter. Ran `arc lint --apply-patches --take BLACK */.py`. Then run `arc lint` again so some other autofixers like spellchecker etc. looked at the code base. Manually accept the changes whenever they make sense, or use a workaround (ex. changing "dict()" to "dict constructor") where autofix is false positive. Disabled linters on files that are hard (i18n/polib.py) to fix, or less interesting to fix (hgsubversion tests), or cannot be fixed without breaking OSS build (FBPYTHON4). Conflicted linters (test-check-module-imports.t, part of test-check-code.t, test-check-pyflakes.t) are removed or disabled. Duplicated linters (test-check-pyflakes.t, test-check-pylint.t) are removed. An issue of the auto-formatter is lines are no longer guarnateed to be <= 80 chars. But that seems less important comparing with the benefit auto-formatter provides. As we're here, also remove test-check-py3-compat.t, as it is currently broken if `PYTHON3=/bin/python3` is set. Reviewed By: wez, phillco, simpkins, pkaush, singhsrb Differential Revision: D8173629 fbshipit-source-id: 90e248ae0c5e6eaadbe25520a6ee42d32005621b 2018-05-26 07:34:37 +03:00			`testui.write(("buffered\n"))`
			`testui.warn(("warning\n"))`
			`testui.write_err("error\n")`
py3: make test-ui-color use print_function 2016-03-29 14:11:32 +03:00			`print(repr(testui.popbuffer()))`
color: check if ui is already a subclass of colorui before wrapping it since it's possible to reuse the ui object (see 6772a32edec7) between dispatch calls, the ui might have been wrapped already. we could probably move this test up a bit but leaving it here allows updates to take effect by extstyles() and configstyles(). 2011-06-02 01:43:34 +04:00
			`# test dispatch.dispatch with the same ui object`
codemod: join the auto-formatter party Summary: Turned on the auto formatter. Ran `arc lint --apply-patches --take BLACK */.py`. Then run `arc lint` again so some other autofixers like spellchecker etc. looked at the code base. Manually accept the changes whenever they make sense, or use a workaround (ex. changing "dict()" to "dict constructor") where autofix is false positive. Disabled linters on files that are hard (i18n/polib.py) to fix, or less interesting to fix (hgsubversion tests), or cannot be fixed without breaking OSS build (FBPYTHON4). Conflicted linters (test-check-module-imports.t, part of test-check-code.t, test-check-pyflakes.t) are removed or disabled. Duplicated linters (test-check-pyflakes.t, test-check-pylint.t) are removed. An issue of the auto-formatter is lines are no longer guarnateed to be <= 80 chars. But that seems less important comparing with the benefit auto-formatter provides. As we're here, also remove test-check-py3-compat.t, as it is currently broken if `PYTHON3=/bin/python3` is set. Reviewed By: wez, phillco, simpkins, pkaush, singhsrb Differential Revision: D8173629 fbshipit-source-id: 90e248ae0c5e6eaadbe25520a6ee42d32005621b 2018-05-26 07:34:37 +03:00			`hgrc = open(os.environ["HGRCPATH"], "w")`
			`hgrc.write("[extensions]\n")`
			`hgrc.write("color=\n")`
color: check if ui is already a subclass of colorui before wrapping it since it's possible to reuse the ui object (see 6772a32edec7) between dispatch calls, the ui might have been wrapped already. we could probably move this test up a bit but leaving it here allows updates to take effect by extstyles() and configstyles(). 2011-06-02 01:43:34 +04:00			`hgrc.close()`

ui: factor out ui.load() to create a ui without loading configs (API) This allows us to write doctests depending on a ui object, but not on global configs. ui.load() is a class method so we can do wsgiui.load(). All ui() calls but for doctests are replaced with ui.load(). Some of them could be changed to not load configs later. 2016-10-22 08:35:10 +03:00			`ui_ = uimod.ui.load()`
color: don't disable colors if HGPLAINEXCEPT=color Summary: With `HGPLAINEXCEPT=color`, colors should still be enabled if the terminal is capable of supporting them and output is to the terminal. Currently this doesn't work if `--color=auto` (the default), as `color._modesetup` uses `ui.formatted` to check if the output is a terminal, and thus has colors available, but this is `False` for all `HGPLAIN` modes. Instead, add a new method to `ui` that checks whether `fout` is a terminal, and use that for color autodetection. This function also allows us to add `HGPLAINEXCEPT=pager` as we can use that in the same way. Reviewed By: farnz Differential Revision: D21617170 fbshipit-source-id: 7ee4eaa8963f3d6eb7ed8044a678a4804b9a98f0 2020-05-19 16:11:56 +03:00			`ui_.setconfig("ui", "assume-tty", "True")`
color: check if ui is already a subclass of colorui before wrapping it since it's possible to reuse the ui object (see 6772a32edec7) between dispatch calls, the ui might have been wrapped already. we could probably move this test up a bit but leaving it here allows updates to take effect by extstyles() and configstyles(). 2011-06-02 01:43:34 +04:00
ui: use I/O descriptors internally and as a result: - fix webproto to redirect the ui descriptors instead of sys.stdout/err - fix sshserver to use the ui descriptors 2011-06-08 02:39:20 +04:00			`# we're not interested in the output, so write that to devnull`
py3: only use binary stdin/stdout/stderr Summary: Drop stdoutbytes/stdinbytes. They make things unnecessarily complicated (especially for chg / Rust dispatch entry point). The new idea is IO are using bytes. Text are written in utf-8 (Python 3) or local encoding (Python 2). To make stdout behave reasonably on systems not using utf-8 locale (ex. Windows), we might add a Rust binding to Rust's stdout, which does the right thing: - When writing to stdout console, expect text to be utf-8 encoded and do proper decoding. - Wehn writing to stdout file, write the raw bytes without translation. Note Python's `sys.stdout.buffer` does not do translation when writing to stdout console like Rust's stdout. For now, my main motivation of this change is to fix chg on Python 3. Reviewed By: xavierd Differential Revision: D19702533 fbshipit-source-id: 74704c83e1b200ff66fb3a2d23d97ff21c7239c8 2020-02-04 05:24:33 +03:00			`ui_.fout = open(os.devnull, "wb")`
ui: use I/O descriptors internally and as a result: - fix webproto to redirect the ui descriptors instead of sys.stdout/err - fix sshserver to use the ui descriptors 2011-06-08 02:39:20 +04:00
color: check if ui is already a subclass of colorui before wrapping it since it's possible to reuse the ui object (see 6772a32edec7) between dispatch calls, the ui might have been wrapped already. we could probably move this test up a bit but leaving it here allows updates to take effect by extstyles() and configstyles(). 2011-06-02 01:43:34 +04:00			`# call some arbitrary command just so we go through`
			`# color's wrapped _runcommand twice.`
			`def runcmd():`
codemod: join the auto-formatter party Summary: Turned on the auto formatter. Ran `arc lint --apply-patches --take BLACK */.py`. Then run `arc lint` again so some other autofixers like spellchecker etc. looked at the code base. Manually accept the changes whenever they make sense, or use a workaround (ex. changing "dict()" to "dict constructor") where autofix is false positive. Disabled linters on files that are hard (i18n/polib.py) to fix, or less interesting to fix (hgsubversion tests), or cannot be fixed without breaking OSS build (FBPYTHON4). Conflicted linters (test-check-module-imports.t, part of test-check-code.t, test-check-pyflakes.t) are removed or disabled. Duplicated linters (test-check-pyflakes.t, test-check-pylint.t) are removed. An issue of the auto-formatter is lines are no longer guarnateed to be <= 80 chars. But that seems less important comparing with the benefit auto-formatter provides. As we're here, also remove test-check-py3-compat.t, as it is currently broken if `PYTHON3=/bin/python3` is set. Reviewed By: wez, phillco, simpkins, pkaush, singhsrb Differential Revision: D8173629 fbshipit-source-id: 90e248ae0c5e6eaadbe25520a6ee42d32005621b 2018-05-26 07:34:37 +03:00			`dispatch.dispatch(dispatch.request(["version", "-q"], ui_))`

color: check if ui is already a subclass of colorui before wrapping it since it's possible to reuse the ui object (see 6772a32edec7) between dispatch calls, the ui might have been wrapped already. we could probably move this test up a bit but leaving it here allows updates to take effect by extstyles() and configstyles(). 2011-06-02 01:43:34 +04:00
			`runcmd()`
color: drop the 'colorui' class Now that all logics formally bared by 'colorui' have been moved to the main ui class, that class is empty and can be dropped. As a nice side effect we can get rid of the baroque Initialization associated to it. There was much rejoicing. 2017-02-20 14:42:35 +03:00			`print("colored? %s" % (ui_._colormode is not None))`
color: check if ui is already a subclass of colorui before wrapping it since it's possible to reuse the ui object (see 6772a32edec7) between dispatch calls, the ui might have been wrapped already. we could probably move this test up a bit but leaving it here allows updates to take effect by extstyles() and configstyles(). 2011-06-02 01:43:34 +04:00			`runcmd()`
color: drop the 'colorui' class Now that all logics formally bared by 'colorui' have been moved to the main ui class, that class is empty and can be dropped. As a nice side effect we can get rid of the baroque Initialization associated to it. There was much rejoicing. 2017-02-20 14:42:35 +03:00			`print("colored? %s" % (ui_._colormode is not None))`