You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Nov 7, 2024. It is now read-only.
On moat 0.39.8 (the current latest available on pip, despite the 0.40.0 release already available on GitHub), I have ran into errors like:
../../../.virtualenvs/throwaway/lib/python3.11/site-packages/anyio/_backends/_trio.py:164: in <module>
class ExceptionGroup(BaseExceptionGroup, trio.MultiError):
../../../.virtualenvs/throwaway/lib/python3.11/site-packages/trio/_deprecate.py:153: in __getattr__
raise AttributeError(msg.format(self.__name__, name))
E AttributeError: module 'trio' has no attribute 'MultiError'
which have gone away just by doing pip install -U anyio. Please update the version compatibility for moat-mqtt.
The text was updated successfully, but these errors were encountered:
lulingar
changed the title
Please release to pip 0.40.0, and update anyio dependency to 4.x
Please update anyio dependency to 4.x
Feb 19, 2024
While I can and will upload 0.40.1 shortly, the problem doesn't originate with moat-mqtt. The root cause is the fact that trio's version numbering scheme doesn't follow Semantic Versioning guidelines, thus some Trio upgrade happened to break your anyio package.
I'll probably have to start a discussion about that on the Trio issue tracker.
On moat 0.39.8 (the current latest available on
pip
, despite the 0.40.0 release already available on GitHub), I have ran into errors like:which have gone away just by doing
pip install -U anyio
. Please update the version compatibility for moat-mqtt.The text was updated successfully, but these errors were encountered: