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.

Sign up for GitHub

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

Jump to bottom

Python 3.10 not recognized #160

Closed
2 of 7 tasks
adamjstewart opened this issue Nov 4, 2020 · 4 comments · Fixed by #175
Closed
2 of 7 tasks

Python 3.10 not recognized #160

adamjstewart opened this issue Nov 4, 2020 · 4 comments · Fixed by #175
Labels
bug Something isn't working

Comments

@adamjstewart
Copy link
Contributor

Describe the bug
All of the documentation for setup-python suggests that Python versions can be listed without quotes:

python-version: [2.7, 3.6, 3.7, 3.8, pypy2, pypy3]

However, this doesn't seem to work for 3.10. The action errors out, with the following error msg:

Version 3.1 with arch x64 not found

If I wrap 3.10 in quotes, it says 3.10 is not found, which is a little better, although I would like to be able to use the alpha version if possible.

Which version of the action are you using?

  • v1
  • v2
  • Some other tag (such as v2.0.1 or master)

Environment

  • self-hosted
  • Linux
  • Windows
  • Mac

Python Versions
3.10

To Reproduce
Steps to reproduce the behavior:

  1. Try adding 3.10 to the list of python-version without quotes

Run/Repo Url

https://github.com/adamjstewart/fiscalyear/actions/runs/346374366
https://github.com/adamjstewart/fiscalyear/actions/runs/346388888
@adamjstewart adamjstewart added the bug Something isn't working label Nov 4, 2020
@maxim-lobanov
Copy link
Contributor

@adamjstewart , Python 3.10 alpha is already available. But when you write 3.10, you are requesting 3.10 stable based on semver notation. Please follow example in readme file to setup 3.10-alpha: https://github.com/actions/setup-python

@adamjstewart
Copy link
Contributor Author

Ah, I was hoping 3.10 would mean any 3.10, even alpha/beta/rc. I think the following error msg is still a bug though:

Version 3.1 with arch x64 not found

It should say 3.10, not 3.1.

@maxim-lobanov
Copy link
Contributor

Please pay attention that task input follow semver notation.

As for the confusing error message, it is a feature of YAML parsing. When you specify input like

version: 3.10

3.10 is parsed as a number and it is trimmed to 3.1 that looks like expected behavior for numbers.
You should specify input with quotes to treat it as string.

version: '3.10'

The first and the second examples in README file shows the correct way with quotes.
But looks like the third and fourth examples show incorrect way. cc: @konradpabjan

@adamjstewart adamjstewart mentioned this issue Dec 20, 2020
Merged
Pytlicek added a commit to Pytlicek/sheet2dict that referenced this issue Mar 14, 2021
@Pytlicek
Update python-package.yml
6fbba5c 
FIX: Python version notation
actions/setup-python#160
@f-dangel f-dangel mentioned this issue Oct 7, 2021
Merged
Almenon added a commit to Almenon/AREPL-backend that referenced this issue Oct 10, 2021
@Almenon
quote to avoid error
4c3b0be 
see actions/setup-python#160
jeffshurtliff added a commit to jeffshurtliff/khoros that referenced this issue Oct 11, 2021
@jeffshurtliff
Added quotes around versions in pythonpackage.yml per actions/setup-p…
37a20e7 
…ython#160
nmlorg added a commit to nmlorg/foyerbot that referenced this issue Oct 18, 2021
@nmlorg
See actions/setup-python#160.
0eee46d
@oesgalha oesgalha mentioned this issue Oct 19, 2021
Merged
maurosilber added a commit to maurosilber/SMO that referenced this issue Oct 26, 2021
@maurosilber
Fix test.yml for Python 3.10
1de137a 
YAML interprets 3.10 as 3.1 if used without strings.

actions/setup-python#160
findgriffin added a commit to findgriffin/mind that referenced this issue Nov 4, 2021
@findgriffin
publish.yaml: Put Python versions in quotes, per actions/setup-python…
14a4e16 
…#160.
leycec added a commit to beartype/beartype that referenced this issue Nov 5, 2021
@leycec
Python 3.10 CI x 2.
f22ea54 
This commit is the next in a commit chain resurrecting Python 3.10
support in our GitHub Actions-based continuous integration (CI)
configuration. Specifically, this commit circumvents upstream issue
actions/setup-python#160 by coercively double-quoting *all* Python
version strings used as the values of "python-version:" keys.
(*Malignant lignite tonight!*)
monocongo pushed a commit to monocongo/climate_indices that referenced this issue Nov 5, 2021
[456] quote for py310 (see actions/setup-python#160)
1c349a2
sakurai-youhei added a commit to sakurai-youhei/python-shukujitsu that referenced this issue Nov 6, 2021
@sakurai-youhei
Change versions from number to string
9b24f06 
actions/setup-python#160 (comment)
leycec added a commit to beartype/beartype that referenced this issue Nov 6, 2021
@leycec
**Beartype 0.9.1** released.
acf44aa 
This patch release delivers obstreperous support for **Sphinx** (*curse
ye and yer little side effects too, `autodoc` extension!*), **generator
callables, readable exception messages,** and **Python 3.10 CI.**

This release resolves **4 issues** and merges **0 pull requests.**
Fearsome changes include:

## Compatibility Improved

* **Sphinx.** `@beartype` now explicitly provides first-class support
  for Sphinx's `autodoc` extension (i.e., `sphinx.ext.autodoc`),
  resolving issue #61, kindly submitted by SeldonIO/alibi ML dev maestro
  supremum Janis Klaise (@jklaise). `@beartype` now transparently
  ignores `autodoc`-mocked module attributes (e.g., produced by the
  `autodoc_mock_imports` list global in Sphinx-specific
  `doc{s,}/conf.py` configuration files of downstream documentation
  trees) used as type hints annotating `@beartype`-decorated callables,
  rendering `@beartype` compatible with `autodoc`-documented codebases.
  Since Sphinx lacks a public API for detecting when `autodoc` is
  currently generating documentation (see: sphinx-doc/sphinx#9805),
  `@beartype` now performs its own ad-hoc detection at decoration time
  with micro-optimized runtime complexity:
  * `O(1)` in the common case (i.e., Sphinx's `autodoc` extension has
    *not* been previously imported under the active Python interpreter).
  * `O(n)` in the worst case (i.e., Sphinx's `autodoc` extension has
    been previously imported under the active Python interpreter), where
    `n` is the height of the call stack leading to `@beartype`.
* **Generator callables.** `@beartype` now relaxes the requirement that
  [a]synchronous generator callables be annotated by [PEP 484][PEP 484]
  -compliant `typing.{Async,}Generator[...]` or [PEP
  585][PEP 585]-compliant `collections.abc.{Async,}Generator[...]` type
  hints to additionally accept [PEP 484][PEP 484]-compliant
  `typing.{Async,}Iterable[...]` and `typing.{Async,}Iterator[...]`
  as well as [PEP 585][PEP 585]-compliant
  `collections.abc.{Async,}Iterable[...]` and
  `collections.abc.{Async,}Iterator[...]` type hints, resolving issue
  #65 kindly submitted by the @posita the positronic brain emitter.

## Features Improved

* **Exception message readability.** `@beartype` now emits more
  human-readable, disambiguous, and useful exception messages. Notably:
  * `@beartype`-decorated callables annotated by one or more numeric
    types (e.g., `int`, `float`, `complex`) now raise exceptions on
    type-checking failures whose exception messages disambiguate those
    numbers from strings, resolving issue #63 kindly submitted by
    @jefcolbi. Previously, these messages double-quoted all numbers for
    disambiguity with the possibly preceding sequence index of those
    numbers in their parent containers -- which then introduced yet
    another unanticipated ambiguity between numbers and strings. Numbers
    are now preserve in their vanilla unquoted form; meanwhile, sequence
    items are additionally disambiguated from sequence values with
    additional explanatory substrings.
  * Edge-case exception messages emitted by our memoized code generator
    no longer contain the mostly inappropriate substring `"wrapper
    parameter" *except* where absolutely appropriate.
  * Annotation-centric exception messages now guaranteeably contain the
    critical substring `"type hint"`.

## Issues Resolved

* **#61,** kindly submitted by SeldonIO/alibi ML dev maestro supremum
  Janis Klaise (@jklaise). See "Compatibility Improved" above.
* **#62,** kindly submitted by Cal Leeming (@foxx), may his serious
  eyebrow-raising monochrome GitHub avatar be a guiding light to us
  all. See "Documentation Revised" below. (Thanks again to the foxy
  @foxx for appraising us all of hitherto unknown typing horrors. And
  just in time for Halloween too.)
* **#63,** kindly submitted by @jefcolbi. See "Features Improved" above.
* **#65,** kindly submitted by @posita the positronic brain emitter. See
  "Compatibility Improved" above.

## Tests Improved

* **Python 3.10 CI.** This release resurrects Python 3.10 support in our
  GitHub Actions-based continuous integration (CI) configuration,
  circumventing upstream issue actions/setup-python#160 by coercively
  double-quoting *all* Python version strings specified as the values of
  "python-version:" keys. *Ya!*

## Documentation Revised

* **Reverse dependency showcase.** The introduction of our front-facing
  `README.rst` documentation now gratefully advertises popular reverse
  dependencies (i.e., downstream open-source Python projects directly
  leveraging `beartype`) with a new on-brand icon bar. Gaze upon iconic
  icons and know the stylish face of unabashed beauty.
* **Type hint elision.** The new "Type Hint Connectives" subsection of
  our front-facing `README.rst` documentation documents various means of
  circumventing counter-intuitive historicity in Python's core type
  hierarchy with (*wait for it*) beartype validators, resolving issue
  #62 kindly submitted by Cal Leeming (@foxx). Specifically, this
  subsection documents how to effectively declare:
  * A new PEP-compliant `int - bool` type hint as a beartype validator
    matching the set of all integers that are *not* booleans.
  * A new PEP-compliant `Sequence - str` type hint as a beartype
    validator matching the set of all sequences that are *not* strings.

  [PEP 484]: https://www.python.org/dev/peps/pep-0484
  [PEP 585]: https://www.python.org/dev/peps/pep-0585

(*Unleaded laden jelly-like underbellies!*)
@johnthagen johnthagen mentioned this issue Nov 6, 2021
Closed
@ksamuel ksamuel mentioned this issue Nov 8, 2021
Closed
georgebisbas added a commit to devitocodes/devito that referenced this issue Nov 9, 2021
@georgebisbas
ci: python version 3.10 needs quotes, see actions/setup-python#160
955f073
@georgebisbas georgebisbas mentioned this issue Nov 10, 2021
Merged
mloubout pushed a commit to devitocodes/devito that referenced this issue Nov 10, 2021
@georgebisbas @mloubout
ci: python version 3.10 needs quotes, see actions/setup-python#160
add4e69
a-w-beck added a commit to USEPA/WARMer that referenced this issue Nov 10, 2021
@a-w-beck
Update python_CI-CD.yaml
f7150db 
correcting Python version 3.10 element to avoid notation issue actions/setup-python#160
@asriniva asriniva mentioned this issue Nov 15, 2021
Merged
h3llrais3r added a commit to h3llrais3r/Auto-Subliminal that referenced this issue Nov 28, 2021
@h3llrais3r
Update ci.yaml
6486f82 
Fix for python 3.10 (needs to be quoted)
See actions/setup-python#160
This was referenced Nov 29, 2021
Merged
Closed
@saadmanrafat
Copy link

on workflow Django CI adding [3.6, 3.7, 3.8, 3.9, 3] interprets as 3.10. The same way when you install python3.10 from the source code. Python3 becomes v3.10.0

@johnthagen johnthagen mentioned this issue Dec 9, 2021
Closed
victorlin added a commit to nextstrain/forecasts-ncov that referenced this issue Jan 18, 2023
@victorlin
setup-miniconda: Use quotes for python-version
6e62686 
3.9 works fine without quotes because it still translates to "3.9".
However, 3.10 will translates to "3.1"¹ which is not desirable.

Making it a string now to avoid unexpected issues in the future.

¹ actions/setup-python#160 (comment)
scs-kno pushed a commit to kown7/rmtoo that referenced this issue Jan 27, 2023
Version 3.10
4b45374 
actions/setup-python#160
@dmitry-shibanov dmitry-shibanov mentioned this issue Feb 3, 2023
Closed
5 tasks
@atc0005 atc0005 mentioned this issue Feb 3, 2023
Open
@panticmilos panticmilos mentioned this issue Feb 3, 2023
Closed
5 tasks
djnnvx added a commit to vrn-sh/erp that referenced this issue Feb 12, 2023
@djnnvx
fix(ci): testing with python 3.10
cf6ca12 
actions/setup-python#160
gkirgizov added a commit to aimclub/GOLEM that referenced this issue Feb 21, 2023
@gkirgizov
Fix python version for YAML
c6c0341 
Per actions/setup-python#160
gkirgizov added a commit to aimclub/GOLEM that referenced this issue Feb 21, 2023
@gkirgizov
Remove pyemd in favor of scipy (#37)
6b2fa54 
* Remove pyemd in favor of scipy

* Bump python version to 3.8 in actions and setup

* Fix python version for YAML

Per actions/setup-python#160
viraj-shah18 added a commit to viraj-shah18/HousingSanDiego that referenced this issue Feb 22, 2023
@viraj-shah18
fixed passing 3.10 as string
6bcc4f5 
actions/setup-python#160
@hpohekar hpohekar mentioned this issue Feb 22, 2023
Merged
mwalzer added a commit to MS-Quality-Hub/pymzqc that referenced this issue Mar 23, 2023
@mwalzer
try gh action fix from actions/setup-python#160
3bcf4de
@dmitry-shibanov dmitry-shibanov mentioned this issue May 9, 2023
Closed
@HajimeKawahara HajimeKawahara mentioned this issue Jun 10, 2023
Merged
sejour-a added a commit to sejour-a/portfolio_website that referenced this issue Jun 13, 2023
@sejour-a
fixed "Error: Version 3.1 with arch x64 not found"
0b24a1a 
actions/setup-python#160 (comment)
michael-kuhlmann added a commit to michael-kuhlmann/padertorch that referenced this issue Jul 21, 2023
@michael-kuhlmann
Put python version 3.10 in quotes
18a67c0 
See also actions/setup-python#160 (comment)
@adrianyorke adrianyorke mentioned this issue Aug 28, 2023
Merged
alexanderwerning pushed a commit to alexanderwerning/padertorch that referenced this issue Oct 25, 2023
@michael-kuhlmann
Put python version 3.10 in quotes
d93cd46 
See also actions/setup-python#160 (comment)
@felliott felliott mentioned this issue Feb 9, 2024
Open
rahmatnazali added a commit to trubusoft/django-starter that referenced this issue Mar 1, 2024
@rahmatnazali
Fix python matrix for 3.10 being recognized as 3.1
163c535 
Ref: actions/setup-python#160
rahmatnazali added a commit to trubusoft/django-starter that referenced this issue Mar 1, 2024
@rahmatnazali
Fix Django Tests runner (#2)
c9d3870 
* Move env inside job

* fix django.yaml

* Move env back to root

* Move requirements.txt inside source folder

* Add python version matrix and dependency install to django.yaml

* Rename Django workflow and job name

* Fix python matrix for 3.10 being recognized as 3.1

Ref: actions/setup-python#160

* Bump actions/setup-python to v5

* remove python 3.12 from matrix

as it will raise error on test:
AttributeError: 'ExampleTestCase' object has no attribute 'assertEquals'. Did you mean: 'assertEqual'?
@TZ-zzz TZ-zzz mentioned this issue Mar 27, 2024
Merged
ocriado91 added a commit to ocriado91/python-telegrambot-flashcards that referenced this issue Apr 1, 2024
@ocriado91
Fix python versions typo according to actions/setup-python#160
7d15c6a
jombr added a commit to jombr/rnc2rng that referenced this issue Apr 15, 2024
@jombr
ci.yml Use quotes around python versions
1df6f73 
version 3.10 was interpreted as 3.1.

Per actions/setup-python#160
use quotes around versions
to get around yaml limitation
jombr added a commit to djc/rnc2rng that referenced this issue Apr 15, 2024
@jombr
ci.yml Use quotes around python versions
95086ea 
version 3.10 was interpreted as 3.1.

Per actions/setup-python#160
use quotes around versions
to get around yaml limitation
Tony-Y added a commit to Tony-Y/pytorch_warmup that referenced this issue May 3, 2024
@Tony-Y
Fix Python 3.10
c9c23df 
actions/setup-python#160 (comment)
davnov015 pushed a commit to davnov015/django-permagate that referenced this issue Jun 10, 2024
Fix python 3 version number in django workflow
00a83ec 
See actions/setup-python#160
davnov015 pushed a commit to davnov015/django-permagate that referenced this issue Jun 10, 2024
Fix python 3 version number in django workflow
c392236 
See actions/setup-python#160
davnov015 pushed a commit to davnov015/django-permagate that referenced this issue Jun 12, 2024
@davnov015
Fix Django CI workflow
9756f89 
Add mysqlclient to requirements.txt

Remove mysql from django CI workflow

Fix python 3 version number in django workflow

See actions/setup-python#160

Don't drop DB in CI workflow

Remove mysqlclient and mysql from django CI workflow
@jannisborn jannisborn mentioned this issue Jun 13, 2024
Merged
davnov015 added a commit to davnov015/django-permagate that referenced this issue Jun 22, 2024
@davnov015
Fix Django CI workflow
283f09b 
Add mysqlclient to requirements.txt

Remove mysql from django CI workflow

Fix python 3 version number in django workflow

See actions/setup-python#160

Don't drop DB in CI workflow

Remove mysqlclient and mysql from django CI workflow
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug Something isn't working
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Use quotes around Python versions in README adamjstewart/setup-python
3 participants
@adamjstewart @saadmanrafat @maxim-lobanov