Code size report:

   bare-arm:    +0 +0.000% 
minimal x86:    +0 +0.000% 
   unix x64:  +224 +0.028% standard[incl +96(data)]
      stm32:   +64 +0.016% PYBV10
        rp2:   +64 +0.020% PICO

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 98.39%. Comparing base (6a4a9bc) to head (d4904f1).
Report is 2219 commits behind head on master.

@@           Coverage Diff           @@
##           master   #11526   +/-   ##
=======================================
  Coverage   98.39%   98.39%           
=======================================
  Files         156      156           
  Lines       20609    20609           
=======================================
  Hits        20278    20278           
  Misses        331      331           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

I don't know if this is any help but I have classes where a passed callback may be either a function or a coroutine. The detection is as follows:

async def _g():
    pass
type_coro = type(_g())

# If a callback is passed, run it and return.
# If a coro is passed initiate it and return.
def launch(func, tup_args):
    res = func(*tup_args)
    if isinstance(res, type_coro):
        res = asyncio.create_task(res)
    return res

@peterhinch thanks yeah I was testing doing exactly the same thing, unfortunately it's not cpython compatible - there the type() of async functions and regular functions are the same!

That being said, this type() based method does work for implementing iscoroutine on micropython, I just thought it was cleaner to re-use the existing hasattr method used in uasyncio, even if it's less exact than actually checking the type.

Would be a good addition. I've run into this as well, and use Peter's method. I strive for interoperability with python code, having same modules running on server and embedded. Anything along that path, especially implementing an existing standard method, sounds good to me.

There's inspect.iscoroutine in the library. Would that not do what you're proposing here?

There's inspect.iscoroutine in the library.

? I can't find it in the inspect source.

Ugh, sorry, you're right, that was my own copy with

iscoroutinefunction = isgeneratorfunction
iscoroutine = isgenerator

added. Seems I forgot to create a PR for that.

@smurfix fwiw I would certainly support a PR for that though, I'd be quite happy to have this as an optional install via mip as part of the inspect library.

I added a comment to that effect to micropython/micropython-lib#998 and will create a separate PR if that's merged without these two lines.

Closed in favour of micropython/micropython-lib#998 thanks @smurfix !