Got the token to generate correctly, but now it's complaining about
scoping -- might be that it needs to be generated for xonsh/xonsh to
push to xonsh/xonsh-docs
* feat: initial match statement support
* refactor assignment exprs for <3.8 compatibility; sort imports
* remove match extensions
* bump qa-workflow python version, minor alterations for qa-pipeline
* add mypy exception
* update mypy version
* Bump workflow main python version to 3.10
* remove outdated note
Co-authored-by: Alexander Firbas <alexander.firbas@gmail.com>
* feat: use github actions to deploy docs
fixes#4473
* fix: install xonsh
* fix: doc action
* chore: support *.md for documentation
* fix: remove hardcoded docs link
it affects local testing
* refactor: move sphinx extensions to its own package
* fix: remove deprecated get_theme_dir
As of Sphinx 1.2, this is passed to Sphinx via a ``setup.py`` entry
point,
and no longer needs to be included in your documentation's
``conf.py``.
* feat: jinja2 render without affecting incremental build
* style:
* feat: auto generate API doc
no need to create a file for each module
* chore: watch top-level and nested files
* refactor: update lib api-docs as well
* fix: import errors when doc generated
for some modules
* fix: relative path
* feat: add release handling
* Update .github/workflows/docs.yml
Co-authored-by: Gil Forsyth <gforsyth@users.noreply.github.com>
* refactor: use github-app-token
* chore: deploy docs only when merged
Co-authored-by: Gil Forsyth <gforsyth@users.noreply.github.com>
* chore: adopt NEP-0029 for py version deprecation policy
fixes#4560
* chore: drop py3.6 from CI
* docs: add news item
* fix: failing qa because latest version to flake8-bugbear
see https://github.com/PyCQA/flake8-bugbear/issues/208
* chore: require >=py3.7
pip21.3 has changed the behaviour of build - https://pip.pypa.io/en/stable/news/#v21-3 to use in-tree-build by default. this creates amalgamated files.
this will install as editable dependency during qa checks
for some reason mypy exclude for __amalgam__.py is not working
* chore: adding py310 to ci
though this will require code/parser changes, this is to prepare for
upcoming adoption
* fix: set python version as string
* fix: reference to master -> main
* fix: coverage is not reported in master
- disable amalgamation
1. during coverage report tests
2. qa tools like mypy may follow imports
- use python 3.9 for coverage and qa report. since it will have more
coverage and better typing support
* chore: use py3.10 with setup-py action
* chore: add news-item check job
* fix: py3.10 error while starting
the match statement is not supported.
while the syntax support is only upto py3.8
* fix: news-item checker
* chore: enable fail report for py310 tests
* test: add test for ptk_shell
* fix: handle ast.Index and ast.ExtSlice change while Parsing
related to #4100, #4099, #4068, #4038, #4028, #4005,
* fix: py39 raises when lineno & col not given
TypeError: required field "col_offset" missing from keyword
* fix: tuple inside scbscriptor support for py39
* chore: enable py39 ci checks
they were silently failing before
* test: a backlog test for attributes inside subscriptors
this would require debugging deep into the ply parser methods.
* docs: add news item
* test: skip test_rc_with_modified_path on windows
* Update tests/test_parser.py
Co-authored-by: Gil Forsyth <gforsyth@users.noreply.github.com>
* test: mark failing tests for py39 parser
Co-authored-by: Gil Forsyth <gforsyth@users.noreply.github.com>
* chore: bring back codcoverage report
* chore: the run-tests.xsh script can't print to stdout
* test: combine coverage on multiple runs
* test: sort coverage report by coverage percent
* chore (ci): split test step
* docs: add news item for code-coverage
* chore: try coverage parallel
but this will not work with --append mode.
* refactor: rewrite xontribs/jedi.xsh -> xontribs/jedi.py to take advantage of python tooling
* chore: update elm ci workflow
* test: update test for jedi xontrib
this will further speedup the workflow.
- also the macos and windows should now have proper cache with conda
- use jinja to template workflows that looks the same
