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 Path is always first #851

Open
3 of 5 tasks
marverix opened this issue Apr 24, 2024 · 1 comment
Open
3 of 5 tasks

Python Path is always first #851

marverix opened this issue Apr 24, 2024 · 1 comment
Labels
bug Something isn't working

Comments

@marverix
Copy link

Description:
I don't know what kind of sorcery is this, maybe it's deeper - in core.addPath(), but when this action is amending PATH, the installed Python version directory is always first. Like, you cannot change it. Any later (after this action) changes to PATH do not really matter, because the installed Python directory is always first. This does not allow setupping any virtualenv on hosted runners.

Action version:
v5

Platform:

  • Ubuntu
  • macOS
  • Windows

Runner type:

  • Hosted
  • Self-hosted

Tools version:
Any

Repro steps:
Just run this action

Expected behavior:
This action should ofc amend the PATH but should allow to do any later amendments to PATH also. Currently this is not possible.

Actual behavior:
Already described earlier.

@marverix marverix added bug Something isn't working needs triage labels Apr 24, 2024
@aparnajyothi-y
Copy link

Hello @marverix, Thank you for creating this issue and we will get back to you once we have some feedback :)

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

2 participants