Joris Nonnast
Joris Nonnast
The issue seems to be with numpy's new typing feature. For np.typing.NDArray jedi crashes in https://github.com/davidhalter/jedi/blob/7ff0d2d5952d1f4bd216a9df0fa7171b20d0512c/jedi/inference/gradual/stub_value.py#L88-L89 because `name.get_definition()` returns `None`. For me, a simple guard like this ```python if definition...
https://github.com/numpy/numpy/blob/25bcff17a58e942fbeaaba65902157b0f070376a/numpy/_typing/_generic_alias.py#L240-L245 This is the definition from the current numpy master branch, which should be numpy version 1.23.1.
Check the file 3rdparty/ippicv/ippicv.cmake in your opencv source directory, there seems to be some invalid CMake code in the first line. It might work if you delete that line. The...
I understand, that Better PDF may be at fault here, I already opened an [issue](https://github.com/MSzturc/obsidian-better-pdf-plugin/issues/26) at their repo, I am posting this here, as I am not proficient enough in...
I ran into a similar problem. For me `let test#python#pytest#file_pattern = '.py'` works. This makes every python file a test file for the pytest runner.
In my opinion, setting the file_pattern inside the vimscript is a sufficient workaround. I am not even sure why vim-test enforces these file patterns . If you have the file...
For me the issue was, that I write python test cases in my module files. Obviously my module filenames do not contain the word test. My workaround > `let test#python#pytest#file_pattern...
The current issue is that vim-test poses its own restrictions on the testfile and testfunction pattern based on the defaults of the respective unittest frameworks. In most unittest frameworks in...
Pytest still has defaults for how testfunctions and test classes have to look like. So if my pytest ini looks like this: ``` [pytest] python_files = "*.py" ``` Running pytest...
I was facing this problem in python: ```python subprocess.run(["pandoc", f"{file}", f"-o {export_file_path.as_posix()}", "--pdf-engine=xelatex"]) ``` This does the trick: ```python subprocess.run(["pandoc", f"{file}", "-o", f"{export_file_path.as_posix()}", "--pdf-engine=xelatex"]) ``` Notice the "-o" is split...