Document how to evade a specific version about setup-python HOT 5 CLOSED

Yeah, the cache is on the image already, we don't control it. We could use some documentation here, I think I may want to hold off documenting this quite yet though because we're looking at changing a lot of this and having a repo to publish tool versions for each image (rather than having them in the tool cache).

Note also that you can check what versions are available on a given image by doing the same thing I do here.

from setup-python.

Covering this from the contributor's perspective would be great too (i.e. what file does one modify to fix the provisioning and send a PR -- though from what I can tell that seems possibly not in here? am I missing where the actual "meat" of the provisioning is?)

from setup-python.

Ah I see, from the README: "optionally installing a version of python and adding to PATH. Note that this action only uses versions of Python already installed in the cache." -- I don't know what "the cache" refers to, but I guess I assume it's some thing already provisioned on virtual machines and all this thing does is know how to pull files out of it, there's no remote downloading involved?

(Would probably be great to document that too)

from setup-python.

A big help-doc was recently published that details Actions + Python https://help.github.com/en/actions/automating-your-workflow-with-github-actions/using-python-with-github-actions

The doc includes an example on how to exclude a specific version of Python. I've added a similar example to the README here and added a link to the help-doc.

The help-doc and recent changes to the README here document all of the intricacies of how setup-python works.

from setup-python.

from setup-python.