Skip to content

Fix macOS Python 3.10 #311

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

Merged
merged 3 commits into from
Feb 25, 2022
Merged

Fix macOS Python 3.10 #311

merged 3 commits into from
Feb 25, 2022

Conversation

jakirkham
Copy link
Member

@jakirkham jakirkham commented Feb 25, 2022

For some reason we pick up clang version 12.0.0 only in the Python 3.10 job, which has problems with TAPI (hence the CI issues we have been seeing). These issues are not present with clang version 12.0.1+ (hence why the other Python jobs work). So here we require clang version 12.0.1+ when installing compilers to fix CI.

Edit: Also included a bit more debug info in CI to aid with issue templates that Conda & conda-forge use

TODO:

  • Unit tests and/or doctests in docstrings
  • tox -e py39 passes locally
  • Docstrings and API docs for any new/modified user-facing classes and functions
  • Changes documented in docs/release.rst
  • tox -e docs passes locally
  • GitHub Actions CI passes
  • Test coverage to 100% (Coveralls passes)

This is often needed when filling out issues in conda-forge. So just
provide this in the CI logs so it is easy to find and share
If `clang` version `12.0.0` is picked up, we encounter issues with TAPI
on macOS. For some reason this happens with Python 3.10 and not other
Pythons. In any event requiring `12.0.1`+ ensures TAPI support is
working correctly, so just apply that constraint when installing
`compilers` to avoid issues.
@jakirkham
Copy link
Member Author

cc @joshmoore @rabernat (for vis)

@joshmoore
Copy link
Member

Odd, but 👍

@jakirkham
Copy link
Member Author

Yeah I filed issue ( conda-forge/clangdev-feedstock#166 ) about this

@jakirkham jakirkham mentioned this pull request Feb 25, 2022
7 tasks
This behaves as exactly equals, which means we don't get patch version
updates (like 3.10.2) instead we get (3.10.0). So this relaxes that to
allow patch version fixes.
conda create -n env python==${{matrix.python-version}} wheel pip compilers 'clang>=12.0.1'
conda create -n env python=${{matrix.python-version}} wheel pip compilers 'clang>=12.0.1'
Copy link
Member Author

@jakirkham jakirkham Feb 25, 2022

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Having ==s effectively means 3.10.0 instead of 3.10.0+. As we likely don't want to pin the patch version to 0, relaxing that here. May be part of the issue we were seeing as well

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Oh wow. TIL. 👍

@jakirkham
Copy link
Member Author

Was unable to reproduce the issue locally.

Have conda version 4.11.0 (same as CI). A slightly newer version of python is used in the base environment (both locally and on CI it is 3.9) and a newer macOS, but doubt either of those is causing the solver issue.

In any event this should unblock CI here. Will see if anything turns up in the upstream issue.

@jakirkham
Copy link
Member Author

CI looks green ✅

@jakirkham
Copy link
Member Author

Merging to fix CI. Hope that is ok.

@jakirkham jakirkham deleted the fix_macos_py310 branch February 26, 2022 01:46
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants