Skip to content
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

Python 3.8 and 3.9 not found on macOS #850

Closed
2 of 5 tasks
ZeroIntensity opened this issue Apr 23, 2024 · 11 comments
Closed
2 of 5 tasks

Python 3.8 and 3.9 not found on macOS #850

ZeroIntensity opened this issue Apr 23, 2024 · 11 comments
Assignees
Labels
bug Something isn't working

Comments

@ZeroIntensity
Copy link

ZeroIntensity commented Apr 23, 2024

Description:
Python 3.8 and 3.9 on macOS no longer work, and actions complains about them not being a real version.

Action version:
Latest

Platform:

  • Ubuntu
  • macOS
  • Windows

Runner type:

  • Hosted
  • Self-hosted

Tools version:
Python 3.8 - Python 3.9. It might be all versions <Python 3.10, but I haven't tested that.

Repro steps:
See this run from yesterday, vs this run from this morning on the same commit.

Expected behavior:
Python 3.8 and 3.9 should install on macOS

Actual behavior:
The following is logged to actions:

Version 3.8 was not found in the local cache
Error: Version 3.8 with arch arm64 not found
The list of all available versions can be found here: https://raw.githubusercontent.com/actions/python-versions/main/versions-manifest.json
@ZeroIntensity ZeroIntensity added bug Something isn't working needs triage labels Apr 23, 2024
@hugovk
Copy link
Contributor

hugovk commented Apr 23, 2024

This is a duplicate, macos-latest now uses M1 runners (macos-14-arm64) and 3.9 and earlier aren't available there: #696 (comment)

To fix, you can use one of the options at python/peps#3763, or stick to macos-12 or macos-13 (but you get some nice speedups using M1 where available).

@snorkman88
Copy link

I am facing the same issues when running GHA I get:

Installed versions
  Version 3.8 was not found in the local cache
  Error: The version '3.8' with architecture 'arm64' was not found for macOS 14.4.1.

@ZeroIntensity
Copy link
Author

Odd, that issue is from months ago, but I only started having problems this morning.

@hugovk
Copy link
Contributor

hugovk commented Apr 23, 2024

Yeah, macos-latest used to point to macos-12 but now points to macos-14-arm64.

You can check the top of your CI logs to see which image was used yesterday and today.

gcattan added a commit to qbarthelemy/pyRiemann-qiskit that referenced this issue Apr 23, 2024
gcattan added a commit to pyRiemann/pyRiemann-qiskit that referenced this issue Apr 23, 2024
* deprecate cov_to_corr_matrix

* change import for deprecated

* Update setup.py

fix setup.py

* Update requirements.txt

add mne dependency to requirement file for doc only

* Update Dockerfile

remove protobuf install in Dockerfile (now by default in setup.py)

* Update light_benchmark.py

flake8  # noqa: E231

* Update plot_financial_data.py

flake8

* Update light_benchmark.yml

trigger benchmark on change to setup.py

* [pre-commit.ci] auto fixes from pre-commit.com hooks

* Update testing.yml

as per actions/setup-python#850 (comment)

---------

Co-authored-by: gcattan <[email protected]>
Co-authored-by: pre-commit-ci[bot] <66853113+pre-commit-ci[bot]@users.noreply.github.com>
@Paebbels
Copy link

The list of offered Python versions is here: https://raw.githubusercontent.com/actions/python-versions/main/versions-manifest.json

It shows no Python 3.8 and Python 3.9 for macOS (Python for ARM64 platform).

@HarithaVattikuti
Copy link
Contributor

Hello @ZeroIntensity
Thank you for creating this issue. We will investigate it and get back to you as soon as we have some feedback.

WenjieDu added a commit to WenjieDu/PyPOTS that referenced this issue Apr 29, 2024
* test: stick to macOS-13 to avoid python 3.7 missing for m1 chip;

actions/setup-python#850
jdkent pushed a commit to neurostuff/PyMARE that referenced this issue Apr 30, 2024
…tion term in Stouffers (#121)

* Support precomputed correlation matrix for calculating variance inflation term in Stouffers

* Update test_results.py

* Switch to macos-12 per actions/setup-python#850

* Update test_results.py
yoda-vid added a commit to sanderslab/magellanmapper that referenced this issue May 1, 2024
Python 3.6-3.9 is no longer supported on `macos-latest`, which was recently updated to `macos-14-arm64` (see actions/setup-python#850 (comment)).

- Target macOS runner platforms by supported Python version
- Simplify specification of Ubuntu runners by moving `ubuntu-20.04` to an `include` statement
yoda-vid added a commit to sanderslab/magellanmapper that referenced this issue May 2, 2024
Python 3.6-3.9 is no longer supported on `macos-latest`, which was recently updated to `macos-14-arm64` (see actions/setup-python#850 (comment)).

- Target macOS runner platforms by supported Python version
- Simplify specification of Ubuntu runners by moving `ubuntu-20.04` to an `include` statement
@aparnajyothi-y aparnajyothi-y self-assigned this May 6, 2024
@aparnajyothi-y
Copy link
Contributor

Hello @ZeroIntensity, We are supporting python 3.8 and 3.9 versions for macos arm64 now. Please test your workflows. Closing this issue for now and let us know to reopen this issue if the you are still facing the issue.

Hello @abravalheri, We have investigated the issue and we found that setup-python is successful on macos-latest. We have further more investigated by looking into your project about the issue and found that the file attribute is not found in the global scope of a module being used, which in this case is the setup.py file. The issue occurs in the context of the setup-python action when it tries to install setuptools and pip. The error is more likely to do with how the environment is configured in the action rather than the macOS version.
We can add a step to upgrade setuptools before the step where the error occurs to resolve the issue.

name: Upgrade setuptools
run: pip install --upgrade setuptools

we can change the setup.py file in the repository, consider replacing it with pyproject.toml and setup.cfg. The pyproject.toml file is a newer, more robust method of managing Python package builds and dependencies.
Please raise new issue if the issue still exists as this issue is opened for Python 3.8 and 3.9 support on macOS.

@abravalheri
Copy link

abravalheri commented May 7, 2024

Hello @abravalheri, We have investigated the issue and we found that setup-python is successful on macos-latest. We have further more investigated by looking into your project about the issue and found that the file attribute is not found in the global scope of a module being used, which in this case is the setup.py file. The issue occurs in the context of the setup-python action when it tries to install setuptools and pip. The error is more likely to do with how the environment is configured in the action rather than the macOS version.\nWe can add a step to upgrade setuptools before the step where the error occurs to resolve the issue.\n\nname: Upgrade setuptools\nrun: pip install --upgrade setuptools\n\nwe can change the setup.py file in the repository, consider replacing it with pyproject.toml and setup.cfg. The pyproject.toml file is a newer, more robust method of managing Python package builds and dependencies.\nPlease raise new issue if the issue still exists as this issue is opened for Python 3.8 and 3.9 support on macOS.

Hi @aparnajyothi-y thank you for investigating, but this explanation does not make much sense for me.

You suggested installing the updated version of setuptools before the step that is failing... The problem with this suggestion that the problem that is failing is the installation of Python itself... So, how should I update stuff when Python is not installed yet? The step that is failing is very much the first one, it should not depend on the code inside the repository, right?

The second suggestion about replacing setup.py with pyproject.toml, also does not work and actually contains a bit of misleading and innacurate information:

  1. pyproject.toml is by no means more robust, it is just a different configuration format.

  2. setup.py, setup.cfg and pyproject.toml are not mutually exclusive, they can all exist at the same time and do different things - that is exactly what happens in the repository with problems: we have all of these files at the same time.

Please note that the problem is happening for the repository of setuptools itself. Maybe that is related?

bkueng added a commit to Auterion/libmav-python that referenced this issue May 14, 2024
bkueng added a commit to Auterion/libmav-python that referenced this issue May 14, 2024
tseaver added a commit to Pylons/hypatia that referenced this issue May 16, 2024
tseaver added a commit to Pylons/hypatia that referenced this issue May 16, 2024
* tests: demonstrate #18

Fix 'setup.py' to prevent building 'okascore' module if 'PURE_PYTHON'
is defined.

Add 'py310-pure' environment to build / run tests with that env var set.

Note that the new test fails under 'py310', but passes under 'py310-pure'

* fix: use 'PyFloat_AsDouble' for upcasts

- We know that the second element of each 'd2fitems' *should* be a float
  already (we store it, after all, in an IF BTree).

- The upcast in the second change is safe, and more regular.

* ci: bump checkout, setup-python action versions

- Use released Python 3.12

* ci: work around GHA macos-latest messes:

- actions/setup-python#850
- actions/setup-python#860

---------

Co-authored-by: Peter Wilkinson <[email protected]>
dstansby pushed a commit to UCL-ARC/python-tooling that referenced this issue May 17, 2024
Following the recent change on GitHub Actions
actions/setup-python#850 our tests are
currently failing #359.

Previously we were following
[NEP29](https://numpy.org/neps/nep-0029-deprecation_policy.html) which
is why we never supported `3.8`. My suggestion is to drop `3.9` which
means nothing else has to change.

The alternative is to do @dstansby's
[suggestion](#359 (comment)),
but I think this is low-key complicated when involving our `tox` setup
too. Personally, I don't think it's worth it, and we should fix the
tests ASAP.
ThomasDebrunner pushed a commit to Auterion/libmav-python that referenced this issue Jun 13, 2024
KotlinIsland pushed a commit to KotlinIsland/basedmypy that referenced this issue Jun 20, 2024
Fix failing MacOS tests in CI

Python 3.9 is not available on the latest MacOS images
actions/setup-python#850
KotlinIsland pushed a commit to KotlinIsland/basedmypy that referenced this issue Jun 21, 2024
Fix failing MacOS tests in CI

Python 3.9 is not available on the latest MacOS images
actions/setup-python#850
KotlinIsland pushed a commit to KotlinIsland/basedmypy that referenced this issue Jun 22, 2024
Fix failing MacOS tests in CI

Python 3.9 is not available on the latest MacOS images
actions/setup-python#850
KotlinIsland pushed a commit to KotlinIsland/basedmypy that referenced this issue Jun 22, 2024
Fix failing MacOS tests in CI

Python 3.9 is not available on the latest MacOS images
actions/setup-python#850
KotlinIsland pushed a commit to KotlinIsland/basedmypy that referenced this issue Jun 22, 2024
Fix failing MacOS tests in CI

Python 3.9 is not available on the latest MacOS images
actions/setup-python#850
KotlinIsland pushed a commit to KotlinIsland/basedmypy that referenced this issue Jun 25, 2024
Fix failing MacOS tests in CI

Python 3.9 is not available on the latest MacOS images
actions/setup-python#850
KotlinIsland pushed a commit to KotlinIsland/basedmypy that referenced this issue Jun 25, 2024
Fix failing MacOS tests in CI

Python 3.9 is not available on the latest MacOS images
actions/setup-python#850
Fontanapink added a commit to ucl-cssb/MIMIC that referenced this issue Oct 23, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

8 participants