Invalid MRO when importing rich_click about rich-click

[dwreeves]

Thanks for submitting an issue!

Which version of Python are you using? And which version of Click? Is there anything else in your configuration that may be of interest?

This is a weird issue, as it's not something we ever ran into when testing. I have a suspicion of what may be causing it.

[bhirsz]

Pythin 3.12. And I have just realized I'm using most recent, develop version of the Click(more recent than released 8.1.7). It may be the reason. pon., 6 maj 2024, 17:40 użytkownik Daniel Reeves ***@***.***> napisał:

…

Thanks for submitting an issue! Which version of Python are you using? And which version of Click? Is there anything else in your configuration that may be of interest? This is a weird issue, as it's not something we ever ran into when testing. I have a suspicion of what may be causing it. — Reply to this email directly, view it on GitHub <#195 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ACBDAYT3OAK2SW7WAOMRQL3ZA6P53AVCNFSM6AAAAABHIXBVSSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAOJWGMZDQMRXGM> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[dwreeves]

That's what I thought!

This is super helpful, I had a feeling the latest version of Click would cause issues, and I hadn't actually tested this part of the code. Thank you for unwittingly testing that for us 😅

I will have click~9 working (hopefully) as part of the 1.8.1 release. At least, this MRO issue will be resolved.

[dwreeves]

Github autoclosed this issue. I didn't fully test this (sorry, in a rush). I think it should be fixed. But let me know if it isn't.