* migrate setup.py to setup.cfg
No man pages
* fix Makefile build
* silence flake8 F811 for BaseCLIResponse.command
* also include man pages
* restore a stub setup.py
* remove pytest-lazy fixtures
* Hide pretty help
* Automatic release update warnings.
* `httpie cli check-updates`
* adapt to the new loglevel construct
* Don't make the pie-colors the bold
* Apply review feedback.
Co-authored-by: Jakub Roztocil <jakub@roztocil.co>
* Refactor tests to use a text-based standard output. (#1318)
* Implement new style `--help` (#1316)
* Implement man page generation (#1317)
* Implement rich progress bars. (#1324)
* Man page deployment & isolation. (#1325)
* Remove all unsorted usages in the CLI docs
* Implement isolated mode for man page generation
* Add a CI job for autogenerated files
* Distribute man pages through PyPI
* Pin the date for man pages. (#1326)
* Hide suppressed arguments from --help/man pages (#1329)
* Change download spinner to line (#1328)
* Regenerate autogenerated files when pushed against to master. (#1339)
* Highlight options (#1340)
* Additional man page enhancements (#1341)
* Group options by the parent category & highlight -o/--o
* Display (and underline) the METAVAR on man pages.
* Make help message processing more robust (#1342)
* Inherit `help` from `short_help`
* Don't mirror short_help directly.
* Fixup the serialization
* Use `pager` and `man` on `--manual` when applicable (#1343)
* Run `man $program` on --manual
* Page the output of `--manual` for systems that lack man pages
* Improvements over progress bars (separate bar, status line, etc.) (#1346)
* Redesign the --help layout.
* Make our usage of rich compatible with 9.10.0
* Add `HTTPIE_NO_MAN_PAGES`
* Make tests also patch os.get_terminal_size
* Generate CLI spec from HTTPie & Man Page Hook (#1354)
* Generate CLI spec from HTTPie & add man page hook
* Use the full command space for the option headers
* Add install/update instructions database
* Update the database
* Revert README changes
They will be overwritten later.
* Revert
* Tweak
* Tweaks
* Upgrade database
* Complete commands
Still not sure about Spack upgrades.
* Sort
* Doc generation script draft
* Remove OS names from tool names
* Fix Linuxbrew name
* `wheel` already installs `setuptools`
* Gen docs
* Update
* Tweak
* Add a GitHub workflow to check for outdated installation instructions
* Fix return value
* Test
* Delete test
* Rename the script
* Add `make doc-install-inst`
* Add missing dev requirement
* The first tool is the primary we want to display
Then they are simply sorted by `tool.title`.
* Sort OSes by name
* Refactoring, jinja template, etc.
* Add tool title uniqueness `assert`, fix platform list extra `\n`
* Rebuild docs
* Update generate.py
* Update README.md
* Update methods.yml
* Update distros derived, more assertions
* Tweaks
* Add workflow to auto-update the docs
* Do not hide the command
* Tweaks
Co-authored-by: Jakub Roztocil <jakub@roztocil.co>
* Add a workflow to check documentations
* Fix markdown issues
* Install Ruby 2.7
* Finally, handle and fix GitHub templates
* Minor improvement in the feature request template
* Verbose mode to be sure all files are checked
* Split the monolithic workflow into specific ones
* Rename workflows, improve commands
* Update pip from the venv
* Fix Windows setup
* Lowercase macos-latest
* Fix Windows run, again
* Update brew formula to 2.5.0
* Can use `idna` 3.2
* Sort requirements to ease reproductible builds
And also to have the same output as `brew bump-formula-pr`.
* Sync `bottles` with official Formula
And keep the `high_sierra` one.
* Add a workflow to check the Formula
* Convert most of the documentation from the frontend `README.rst` to `docs/REAME.md`
Also converted all reStructuredText files to Markdown.
* Tell `mdformat` to use LF for end on lines
* `--check` is not needed in the help message
* Skip tests on GitHub Windows.
Those tests pass on a real Windows machine.
Let's revisit those failure later, if needed.
* Move `mdoformat` requirement from `test` to `dev` extra
To fix Fedora CI.
Running tests through `python setup.py test` is deprecated:
> WARNING: Testing via this command is deprecated and will be removed
> in a future version. Users looking for a generic test entry point
> independent of test runner are encouraged to use tox.
I am not in favor of moving back to `tox`, we should simply run tests
using `python -m pytest` (or `make test`) and that's it.
A new extra was added, `dev`, to install development requirements:
$ python -m pip install --upgrade --editable '.[dev]'
`py.test` was chosen over `pytest` but it is not planned for removal yet [1].
Anyway, it is a good thing to ensure we are using the correct Python version
with the right `pytest` installed, so using `python -m pytest` is recommended.
[1] https://github.com/pytest-dev/pytest/issues/1629
* Removed the instructions of tox testing
* Deleted tox.ini
* removed tox from requirements
* removed tox from setup.cfg
* removed tox from the Makefile
* removed tox from contributing docs
* updated the CHANGELOG
* removed tox from .gitignore
