* 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
* 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]'
Since `python setup.py test` is deprecated and `tests_require` is only used by that,
this allows to programmatically read the tests dependencies from the metadata.
- Removes 'Programming Language :: Python :: 3.5' per the
README, which specifies 'Python version 3.6 or greater is required.'
- Adds 'Programming Language :: Python :: 3 :: Only' in place
