Anyio seems to still be a concrete dependency but is not in core requirements

[ascopes]

Hello, thanks for the awesome fork!

Just come across an issue that appears to be related to the anyio migration.

I can see that as part of pyproject.toml, there is no hard dependency on anyio here anymore:

asyncclick/pyproject.toml

Lines 16 to 18 in cdd7233

	dependencies = [
	"colorama; platform_system == 'Windows'",
	]

Unfortunately, it seems we are still importing this:

asyncclick/src/asyncclick/termui.py

Lines 11 to 15 in cdd7233

	from inspect import iscoroutine
	import anyio
	from ._compat import isatty

As a result, I can see the following issues during import:

Traceback (most recent call last):
  File "/home/me/.pyenv/versions/3.12.11/lib/python3.12/site-packages/myapp/cli/mycommand.py", line 6, in <module>
    import asyncclick
  File "/home/me/.pyenv/versions/3.12.11/lib/python3.12/site-packages/asyncclick/__init__.py", line 10, in <module>
    from .core import Argument as Argument
  File "/home/me/.pyenv/versions/3.12.11/lib/python3.12/site-packages/asyncclick/core.py", line 39, in <module>
    from .termui import confirm
  File "/home/me/.pyenv/versions/3.12.11/lib/python3.12/site-packages/asyncclick/termui.py", line 13, in <module>
    import anyio
ModuleNotFoundError: No module named 'anyio'

Environment:

• Python version: 3.12.11
• AsyncClick version: asyncclick-8.3.0.4

[smurfix]

Could you please test the "anyiono" branch?

[ascopes]

I don't think I'll be able to access this without it being on PyPI first unfortunately, reviewed the change though and it looks like it is what is needed to fix this. I'll see if I can manually patch per those changes tomorrow.

[smurfix]

You can "pip install" directly from a git branch.

[ascopes]

Yeah, just need to see if I have permission to do that from the network I'm on

[ascopes]

Yep, looks like it is working. Thanks!

[ascopes]

Forgot to say, thanks for the speedy fix. It is greatly appreciated 🙂