-
-
Notifications
You must be signed in to change notification settings - Fork 115
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
support for osx-arm64 ? #265
Comments
@MarkWieczorek
Please lety me know what result you have with the above, and if you get any error output from conda in general |
Installing pypandoc with pip seemed to work ok (no errors). However, the second part didn't work:
|
And here is the conda output
|
and just to make sure. The result from pypandoc.download_pandoc() doesn't actually put pandoc in the "/Users/lunokhod/Applications/pandoc" folder? |
It did put the pandoc executable in that folder, and the executable seems to work ( |
That's interesting. I'll look into it |
@MarkWieczorek the output from conda doesn't actually show what's wrong, just that it's failing. From what I've gathered:
I'll try to see if I can add mac m1 to the ci here, before I say that this is an upstream issue. |
hey @MarkWieczorek as you can see from the testing added in #267 it seems to be an anaconda issue, not so much a pypandoc issue. |
I'm not sure how travis ci tests work with macos, but its possible that they are being run on intel macs. |
as you can see from this link I've set the travis build to be run on macOS 12.3, macOS 11.6 and macOS 10.15.7. |
In "normal" times that would be ok. But, every 10 years apple decides to screw with us an make new hardware that runs on new chips that are incompatible with the old ones. Generally, this occurs 5 years before they come out with a new charging port for iphones. The past 10 years, macs have used intel chips, but about a year or so ago they started selling macs that use their own "M1" chip. "Big sur" runs on both of them. To be honest, I haven't figured out how to run CI tests using the two different chips... |
aha... I'll see if I can make it report if it's running on inten or m1 chips |
@MarkWieczorek as it turns out, you were right. |
So the error is, that you are getting a "FileNotFoundError" when trying to install pandoc through PyPandoc. |
I don't know how to fix this... sorry! |
There currently is not a pypandoc conda package that works on the new macos machines with M1 chips (osx-arm64). I tried to add pypandoc to the automatic osx-arm64 migrator to generate one (conda-forge/pypandoc-feedstock#16), but it appears that this package can't be automatically migrated for some unknown reason. I am not familiar enough with this repo to understand the problem, but it appears that this might be related to the fact that this wrapper to pandoc downloads pandoc binaries, and that perhaps there isn't an osx-arm64 binary available.
In any case, I would really like to use this package on the new macs, so if anyone knows the origin of this problem, please speak up!
The text was updated successfully, but these errors were encountered: