summaryrefslogtreecommitdiffstatshomepage
path: root/test/functional/provider/python3_spec.lua
AgeCommit message (Collapse)AuthorFiles
2025-05-04feat(messages): cleanup Lua error messagesJustin M. Keyes1
"Error" in error messages is redundant. Just provide the context, don't say "Error ...".
2024-04-23test: improve test conventionsdundargoc1
Specifically, functions that are run in the context of the test runner are put in module `test/testutil.lua` while the functions that are run in the context of the test session are put in `test/functional/testnvim.lua`. Closes https://github.com/neovim/neovim/issues/27004.
2024-04-10refactor(test): inject after_each differentlyLewis Russell1
2024-04-08test: improve test conventionsdundargoc1
Work on https://github.com/neovim/neovim/issues/27004.
2024-03-05fix(eval): make has('pythonx') work properly (#27739)zeertzjq1
Problem: has('pythonx') always returns 1. Solution: Make it the same as has('python3').
2024-01-22refactor: rewrite python provider in luadundargoc1
2024-01-12test: rename (meths, funcs) -> (api, fn)Lewis Russell1
2024-01-03refactor: format test/*Justin M. Keyes1
2022-03-13test(python3_spec): use a pattern to match SyntaxError message (#17705)zeertzjq1
2022-01-29feat(provider)!: remove support for python2 and python3.[3-5]Björn Linse1
These versions of python has reached End-of-life. getting rid of python2 support removes a lot of logic to support two incompatible python versions in the same version.
2021-09-01refactor(tests): use assert_alive() #15546Justin M. Keyes1
2019-12-24system(), jobstart(): raise error on non-executable #11234Daniel Hahler1
* tv_to_argv: error when cmd is not executable Callers always assume that emsg was emitted: - https://github.com/neovim/neovim/blob/57fbf288/src/nvim/eval.c#L12509 - https://github.com/neovim/neovim/blob/57fbf288/src/nvim/eval.c#L17923 - https://github.com/neovim/neovim/blob/57fbf288/src/nvim/eval.c#L18202 * test/functional/provider: display reason from missing_provider * provider#node#Detect: skip / handle non-existing node executable
2019-09-09provider: has("python3_dynamic") et al. #10980Justin M. Keyes1
Vim added more flags for testing yet more dimensions of its Python situation. Handle those in eval_has_provider(). vim-patch:8.0.1436: not enough information about what Python version may work Problem: Not enough information about what Python version may work. Solution: Add "python_compiled", "python3_compiled", "python_dynamic" and "python3_dynamic" values for has(). ref: https://github.com/neovim/neovim/pull/10942#issuecomment-529479500
2019-09-06test: Eliminate expect_errJustin M. Keyes1
Eliminate `expect_err` in favor of `pcall_err` + `eq` or `matches`.
2019-08-28tests: use runtime from build for doc/tags with :help (#10479)Daniel Hahler1
This is better practice in general, and allows to remove the "helptags ALL" hacks. Ref: https://github.com/neovim/neovim/issues/8824 Ref: https://github.com/neovim/neovim/commit/f1b67c3453c * Makefile: fix dependencies with regard to helptags - use the file as the main target to avoid unnecessary triggering - use "make oldtest" on Travis to ensure it gets built
2019-08-14pyxversion: fix logic error #10759Björn Linse1
Do not incorrectly prefer python2 if python3 is working. fixes #10758
2019-05-26messages: use proper multiline error message for rpcrequest and API wrappersBjörn Linse1
2019-01-12provider: improve error message if provider is missing (#9487)Marco Hinz1
Move `has_eval_provider()` check to `eval_call_provider()` to make sure that every code path calls it first. Previously we would, when pynvim was missing, get a nice error message for `:python3 1`, but not for `:py3file blah`. Fixes https://github.com/neovim/neovim/issues/9485
2018-12-12provider: repurpose E319Justin M. Keyes1
In Vim (and some vestigial parts of Nvim) E319 was a placeholder for ex_ni commands, i.e. commands that are only available in certain builds of Vim. That is obviously counter to Nvim's goals: all Nvim commands are available on all platforms and build types (the remaining ex_ni commands are actually just missing providers). We need an error id for "missing provider", so it makes sense to use E319 for that purpose. ref #9344 ref #3577
2018-03-24provider/RPC: apply_autocmds_group(): fix double-freeJustin M. Keyes1
During provider dispatch, eval_call_provider() saves global state--including pointers, such as `autocmd_fname`--into `provider_caller_scope` which is later restored by f_rpcrequest(). But `autocmd_fname` is special-cased in eval_vars(), for performance (see Vim patch 7.2.021; this is also the singular purpose of the `autocmd_fname_full` global. Yay!) If eval_vars() frees `autocmd_fname` then its provider-RPC-scoped alias becomes a problem. Solution: Don't free autocmd_fname in eval_vars(), just copy into it. closes #5245 closes #5617 Reference ------------------------------------------------------------------------ Vim patch 7.2.021 https://github.com/vim/vim/commit/f6dad43c98f47da1ff9d8c99b320fc3674f83c63 Problem: When executing autocommands getting the full file name may be slow. (David Kotchan) Solution: Postpone calling FullName_save() until autocmd_fname is used. vim_dev discussion (2008): "Problem with CursorMoved AutoCommand when Editing Files on a Remote WIndows Share" https://groups.google.com/d/msg/vim_dev/kj95weZa_eE/GTgj4aq5sIgJ
2018-02-12test/python: less-noisy Python skip-messageJustin M. Keyes1
Developer can use :checkhealth to get more details, don't need to blast the details in the skip-message every time.
2017-05-13functests: Replace check_provider -> missing_provider with err reportZyX1
2017-05-13functests: Test invalid behaviourZyX1
Test correctly fail for oneline ruby, python and python3.
2017-04-23api: Do not truncate errors <1 MB. #6237Sander Bosma1
Closes #5984
2016-06-10functests: Check logs in lua codeZyX1
It is otherwise impossible to determine which test failed sanitizer/valgrind check. test/functional/helpers.lua module return was changed so that tests which do not provide after_each function to get new check will automatically fail.
2015-11-04Ensure a session is running before attempting to do Python detection.John Szakmeister1
2015-09-27test: Check for installed Python module with Vimscript function.Florian Walch1
Use the existing Vimscript function provider#pythonx#Detect() to determine whether the Neovim Python module is installed and Python 2/3 tests can be run.
2015-08-09test: move runtime/autoload/* to provider/Justin M. Keyes1
- Organize tests by logical function, not the literal impl location. - Avoid deep nesting / hyper-hierarchy.
Copyright © 2025 - 2026 Wayne Cole. WTFPL. Attribution appreciated. No warranty. Not liable for bodily damages.