Tests passing locally:
bash (no)daemon C
busybox (no)daemon C
fish (no)daemon C
mksh (no)daemon C
rc (no)daemon C
tcsh (no)daemon C
zsh (no)daemon C
zsh zpython
ipython
pdf module
pdf subclass
dash has problems with job control (bgscript.sh not finished by kill)
Now imports follow the following structure:
1. __future__ line: exactly one line allowed:
from __future__ import (unicode_literals, division, absolute_import, print_function)
(powerline.shell is the only exception due to problems with argparse).
2. Standard python library imports in a form `import X`.
3. Standard python library imports in a form `from X import Y`.
4. and 5. 2. and 3. for third-party (non-python and non-powerline imports).
6. 3. for powerline non-test imports.
7. and 8. 2. and 3. for powerline testing module imports.
Each list entry is separated by exactly one newline from another import. If
there is module docstring it goes between `# vim:` comment and `__future__`
import. So the structure containing all items is the following:
#!/usr/bin/env python
# vim:fileencoding=utf-8:noet
'''Powerline super module'''
import sys
from argparse import ArgumentParser
import psutil
from colormath.color_diff import delta_e_cie2000
from powerline.lib.unicode import u
import tests.vim as vim_module
from tests import TestCase
.
There are some problems with a number of spaces on travis: it differs. Cannot
use the same code as for fish because output looks like
{prompt}{spaces}^[0m ^[[{number}D
and both `{spaces}` and `{number}` differ on my machine and in travis.
This commit strips CRs from *.ok files and test output. Test failure used to be
not recognized due to pipe: `cat -v` always succeeds meaning that `if ! diff
… | cat -v` always succeeds too.
Foo
ZyX