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

When installing python 3.9 on v2 throws annoying warning that displays as error after actions is completed. #156

Closed
2 of 7 tasks
AraHaan opened this issue Oct 20, 2020 · 1 comment
Labels
duplicate This issue or pull request already exists

Comments

@AraHaan
Copy link

AraHaan commented Oct 20, 2020

Describe the bug
A clear and concise description of what the bug is.
When installing python 3.9 from this action, it complains about the x64 and x86 python script dirs not being in the PATH.

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

If applicable, please specify if you're using a container

Python Versions
Please list all of the effected versions of Python (3.8.2, etc.)
3.9 stable

To Reproduce
Steps to reproduce the behavior:

  1. Try this in both x86 and x64
 - uses: actions/setup-python@v2
   with:
     python-version: '3.9'
     architecture: 'x86'
  1. Wait for it to download and install.
  2. Notice that after it tries to upgrade pip that it throws an warning that is annoying to see.
  3. Notice that after the action is 100% completed on the job that it shows up as an error as shown in the screenshot below.

Run/Repo Url
If applicable, and if your repo/run is public, please include a URL so it is easier for us to investigate.
(RUN) -> https://github.com/AraHaan/pthmgr/actions/runs/317209470
(Repo) -> https://github.com/AraHaan/pthmgr/

Screenshots
If applicable, add screenshots to help explain your problem.
image

Additional context
Add any other context about the problem here.
I would like this problem fixed somehow, I think that is also supposed to be added to the path as well temporarily so it can shut up.

@AraHaan AraHaan added the bug Something isn't working label Oct 20, 2020
@cclauss
Copy link
Contributor

cclauss commented Oct 20, 2020

Duplicate of #146

@konradpabjan konradpabjan added duplicate This issue or pull request already exists and removed bug Something isn't working labels Nov 9, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
duplicate This issue or pull request already exists
Projects
None yet
Development

No branches or pull requests

3 participants