| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
Added additional documentation
|
|
|
|
| |
now uses for builds
|
|
|
|
|
|
| |
Also:
- Try adding support for 3.9-dev on Travis
- Update to running flake8 for 3.8 instead of 3.7
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
| |
Modified setup.py to include a definition of the extra dependencies required for running unit tests.
This allowed a significant simplification of tox.ini
|
| |
|
|
|
|
|
| |
This is trying to work around a bug in Sphinx:
https://github.com/sphinx-doc/sphinx/issues/5322
|
|
|
|
|
| |
Also:
- Have doc build treat warnings as errors
|
|
|
|
| |
Slowly trying to reduce the number of places we have dependencies specified. The documentation building processes for both `tox -e docs` and readthedocs.org should now use the dependencies specified in `setup.py`.
|
| |
|
| |
|
| |
|
|
|
|
| |
logic in the argcomplete function but doesn't test actual completion in bash.
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
| |
function arguments.
Added example for fully custom completion functions mixed with argparse/AutoCompleter handling
- Also demonstrates the ability to pass in a list, tuple, or dict of parameters to append to the custom completion function.
Added new test cases exercising the custom completion function calls.
Added AutoCompleter and rl_utils to the coverage report.
|
| |
|
| |
|
|
|
|
| |
Apparently there were some issues in the unitest.mock module in Python 3.5 (but not 3.4 or 3.6)
|
|
|
|
|
| |
mock was a backport of Python's built in unittest.mock and was required for Python 3.2 or earlier
- Since we now support Python 3.4+ moving forward we no longer need to make use of the 3rd party mock module
|
|
|
|
| |
3.6 tests
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
- The python-forked module doesn't work on Windows
|
|
|
|
|
|
|
| |
Due to apparent bugs in pyparsing, this can significantly speed up unit test execution.
Also:
- Removed use of pexpect in unit tests
|
|
|
|
|
|
| |
Added pexpect to modules required for running unit tests.
This opens the door for carefully crafted complex unit tests to verify intricate behavior. Tests like this are somewhat painful to write and slow to execute. However, they can enable testing complicated interactive behavior that we otherwise probably would not be able to test.
|
|
|
|
|
| |
Python 3.3 builds appear to be no longer supported on Travis CI.
This replaces Python 3.3 with Python 3.7-dev for Travis CI builds.
|
|
|
|
| |
work again
|
|
|
|
|
|
|
|
|
|
| |
Now a real pipe is created to a subprocess. This has many advantages and should "just work" like intended with all commands.
One downside is to work properly on Python 2.7, it requires the subprocess32 module which is the subprocess module from Python 3.2 backported to Python 2.7. Another downside, is that unit testing the feature is now more difficult.
This still needs to be tested for compatibility across all OSes and supported versions of Python.
The user needs to be careful if designing multi-threaded cmd2 applications that do command processing in other threads and those threads can make calls to self.stdout.write to put in a try/except to catch Broken Pipe errors which can occur for long running commands if the user closes the shell subprocess before the command is finished.
|
| |
|
|
|
|
| |
pytest-xdist to play nicely together
|
| |
|
|
|
|
|
| |
It works fine for me on my Mac, but it doesn't seem to work right on either TravisCI or AppVeyor.
It appears to calculate the code coverage incorrectly when using pytest-xdist.
|
|
|
|
| |
analysis
|
|
|
|
| |
code coverage
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Now that we have a lot of unit tests and are running code coverage analysis,
our unit tests take a long time to run.
Changes include ...
tox:
- Install pytest-xdist to parallelize unit tests
- Only run code coverage analysis on Python 2.7 and 3.6
- Don't run examples/example.py anymore, just run the unit tests
TravisCI:
- Stop building on Python 3.7-dev since that won't be released for some time
AppVeyor:
- Stop building on Python 3.4 since that isn't as important and is covered by Travis
|
|
|
|
|
|
| |
- Added a 3rd-party dependency on the pyperclip module
TODO: Rigorous test on all OSes, particularly Linux systems without xclip
|
|
|
|
|
|
| |
Running a code coverage analysis takes forever on pypy and twice forever for pypy3, so don't try.
Also try to get codecov working with AppVeyor
|
| |
|
|
|
|
|
|
|
| |
Changes include:
1) Added CONTRIBUTING.md with detailed instructions for how to contribute, which should be especially useful to those new to open source in general or GitHub in particular
2) Added CODE_OF_CONDUCT.md which sets ground rules for participants’ behavior and helps to facilitate a friendly, welcoming environment
3) Renamed the "example" directory to "examples" in the hope that one day soon there may be more than a single example ;-)
|
| |
|
|
|
|
| |
compatibility via use of the six module.
|