Add a paragraph to installation documentation page explaining issue where Anacoda on MacOS may try to install the Intel version of packages on M1 system and run things through Rosetta, which fails for unknown reasons. Current recommendation is to switch to using miniconda if this happens, which seems to manage the installation without issue. This is probably not really an apexpy problem, but we'll make a note of it in case other users encounter the same issue. More work could be done to investigate why Anaconda running through Rosetta generates an issue, but this is likely a rare edge case.
Type of change
This change is a documentation update
Checklist
[x] Make sure you are merging into the develop (not main) branch
[x] My code follows the style guidelines of this project
[x] I have performed a self-review of my own code
[ ] I have commented my code, particularly in hard-to-understand areas
[x] I have made corresponding changes to the documentation
[x] My changes generate no new warnings
[ ] I have added tests that prove my fix is effective or that my feature works
[x] New and existing unit tests pass locally with my changes
[ ] Any dependent changes have been merged and published in downstream modules
[ ] Add a note to Changelog.rst, summarising the changes
Description
Add a paragraph to installation documentation page explaining issue where Anacoda on MacOS may try to install the Intel version of packages on M1 system and run things through Rosetta, which fails for unknown reasons. Current recommendation is to switch to using miniconda if this happens, which seems to manage the installation without issue. This is probably not really an apexpy problem, but we'll make a note of it in case other users encounter the same issue. More work could be done to investigate why Anaconda running through Rosetta generates an issue, but this is likely a rare edge case.
Type of change
Checklist
develop(notmain) branchChangelog.rst, summarising the changesAUTHORS.rstand.zenodo.json