Paul O'Leary McCann

Sorry it took me a while to follow up, but thanks for the extensive test! It's great to have a really thorough test like that. I modified it so it...

For reference, while the code paths do look the same, this isn't the first inconsistency like this to come up - by default errors in the Tagger don't give output...

@aehlke That isn't the same issue, and you can get around it with quoting, see [here](https://github.com/polm/fugashi/blob/03451c283f016045877f956e8b2ec00a9e77b012/fugashi/fugashi.pyx#L216).

Thanks for checking! It's unfortunate this didn't just work, it's going to be hard for me to troubleshoot without an M1. I suspect the issue is that MeCab itself has...

Thanks for the report. If you're using 1.1.1 then either you're building from source or using x86 wheels (and x86 Python), which means it should work the same with the...

To clarify the current situation a bit, my impression is that it generally is harder to get fugashi to run on M1 Macs than other systems. The reason for this...

It looks like earlier this month Github [added support for M1 runners](https://github.blog/changelog/2022-08-09-github-actions-self-hosted-runners-now-support-apple-m1-hardware/), but the [setup-python action does not yet support it](https://github.com/actions/setup-python/issues/108). I will keep an eye on this to see...

To clarify: I missed it, but the support for M1 runners announced recently only covers **self-hosted** runners. As I own no Apple products this doesn't help fugashi/mecab-python3, so we'll have...

I'm not interested in doing any work on that feature myself, I've never used it. But if you've already written the code feel free to submit a PR and I...

Thanks! It might take me a bit but I'll take a look at it.