Skip to content

Support 3.10 #249

Description

Hello,
Can you guys please add support for 3.10 it was released today.

Activity

  1. ghost added
    bugSomething isn't working
    on Oct 5, 2021
  2. hugovk commented on Oct 5, 2021

    @hugovk
    Contributor

    For reference, it took 17 hours for Python 3.9 (#148) and 20 days for Python 3.8 (#30) :)

    3.10 was released at 20:00 UTC yesterday, so 13:00 UTC today is your target!

  3. MaksimZhukov commented on Oct 5, 2021

    @MaksimZhukov
    Contributor

    Hello everyone!
    Python 3.10.0 is already available via the setup-python action.
    Unfortunately, it is not pre-installed on the images yet. New images with Python 3.10.0 will be deployed next week.

  4. hugovk commented on Oct 5, 2021

    @hugovk
    Contributor

    It wasn't two hours ago, but is now! (12 hours after release 👍 )

    Thank you!

  5. eddiebergman commented on Oct 5, 2021

    @eddiebergman

    For anyone who comes across this, make sure to use quotes around 3.10, i.e. "3.10", as 3.10 as a float gets converted to 3.1

  6. hugovk commented on Oct 5, 2021

    @hugovk
    Contributor

    For anyone who comes across this, make sure to use quotes around 3.10, i.e. "3.10", as 3.10 as a float gets converted to 3.1

    For a longer explanation see: https://dev.to/hugovk/the-python-3-1-problem-85g

  7. added a commit that references this issue on Oct 5, 2021
  8. added a commit that references this issue on Oct 8, 2021
  9. added a commit that references this issue on Oct 8, 2021
  10. pbelskiy commented on Oct 10, 2021

    @pbelskiy

    Thanks, but I when I will be available for GitHub actions? It's still problem with error:

    Error: Version 3.10 with arch x64 not found
    
    Available versions:
    2.7.18 (x64)
    3.5.10 (x64)
    3.6.15 (x64)
    3.7.12 (x64)
    3.8.12 (x64)
    3.9.7 (x64)
    
  11. hugovk commented on Oct 10, 2021

    @hugovk
    Contributor

    @pbelskiy You need to use actions/setup-python@v2 not actions/setup-python@v1.

  12. henryiii commented on Oct 12, 2021

    @henryiii

    Ah, this explains why setup-nox can't find 3.10, it activates all (pre-)installed versions.

  13. henryiii commented on Oct 12, 2021

    @henryiii

    Personally, I'd be tempted to at least consider making the float 3.1 map to "3.10" - the number of people using 3.1 should in theory be zero, and the number of users wondering why 3.10 produces a failure due to lack of "3.1" for most architectures is quite high, judging from twitter. After all, the fact that floats map to string versions is just a shortcut anyway - and a shortcut that has an unfortunate consequence for 3.10. By the time 3.20 rolls around, 3.2 should be even safer to map to 3.20, etc. (For those considering this a YAML bug, it has nothing to do with YAML - no language I know of maps 3.10 to anything but the float 3.1, and yaml does differentiate unambiguously between 3.10 (float) and "3.10" (string). It's just a shortcut that setup-python also accepts floats for version numbers. "3.1" would still access 3.1, if it's supported (I think it is on some platforms?)

    It's kind of weird, so I probably would just continue let people correct their usage to all strings, but, just a thought.

    Is 3.10 going to be installed by default at some point? It would be nice for it to be picked up by setup-nox, and I assume it would be faster to use, too.

  14. 11 remaining items

  15. added a commit that references this issue on Dec 26, 2021
  16. added a commit that references this issue on Jul 5, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't working

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions