Tin Tvrtković

Hi, I tried simplifying the example to: ``` import asyncio import pytest from unittest.mock import MagicMock TEST_DATA = { 'Key1': ['Key1', 'Data desc for key1'], 'Key2': ['Key2', 'Data desc for...

The way pytest plugins register themselves with pytest is by using entrypoints: https://github.com/pytest-dev/pytest-asyncio/blob/master/setup.py#L53 So maybe this is the problem?

I think someone mentioned leaving the original names as they are and just adding a suffix explaining the test. How bout that?

Just take your `clear_directory` function and run it in a background thread: ```python from asyncio import get_running_loop async def coroutine(): await get_running_loop().run_in_executor(None, clear_directory) ``` This is what aiofiles would do...

Yep, looks like `functools.wraps` will do the trick. ```python from functools import wraps def dec(fn): @wraps(fn) def wrapper(*args, **kwargs): return fn(*args, **kwargs) return wrapper @dec async def coroutine_func(): pass print(coroutine_func.__name__)...

Negative, my global and workspace settings do not reference that key :(

Oh, interesting, my `src` does *not* have an `__init__.py`. We're using namespace packages since some other code is in the same package, but another directory. Here's the full log with...

No, it's a private repo, but I could try paring it down as much as I can while still reproing and then publishing it somewhere.

I whittled it down to https://github.com/Tinche/vs-code-test. Still says `No source files found.` unless I explicitly add `src` to `python.analysis.include`, then it says `Found 1 source file`.

Glad I could help and thanks for looking into this ;)