Enhance reading from .python-version

[krystof-k]

Enhance reading from .python-version file, matching the Pyenv behavior:

• resolves multiple versions from multiple lines
• handles pyenv-virtualenv pointers (e.g. 3.10/envs/virtualenv)
  (see Don't use .python-version for auto-activation pyenv/pyenv-virtualenv#472)
• ignores empty lines and lines starting with #
• trims whitespace

Closes #734 and supersedes #647.

Check list:

• Mark if documentation changes are required.
• Mark if tests were added or updated to cover the changes.

[maruthiaws0808]

steps:

• uses: actions/checkout@v4
• uses: actions/setup-python@v4
  with:
  python-version: 'graalpy-22.3'
• run: python my_script.py

[priya-kinthali]

Hello @krystof-k👋,
Thank you for submitting this PR to enhance reading from the .python-version file! 😊
Could you please update your branch with the latest changes from the main branch and run the npm ci, npm run format and npm run build commands to resolve the failing checks related to Basic Validation and dist?
Thank you!

[krystof-k]

Hi @priya-kinthali, I did, please approve the workflows.

[krystof-k]

@priya-kinthali I fixed the lint, please rerun. I have no idea what the check-dist is.

[krystof-k]

@priya-kinthali sorry, I pushed into a wrong branch. Now it should pass.

[priya-kinthali]

Hello @krystof-k👋,
Thank you for the quick updates!
Please ensure to run npm run build to generate compiled files in the dist/setup and dist/cache-save directories. This should resolve the check-dist failure, as the compiled files are required for the checks to pass.
Also run the npm run test command to run the tests and ensure everything is working as expected.
Additionally, could you also please update the Python versions to the latest ones in the utils.test.ts file, removing the end-of-life versions?
Thank you for your cooperation and effort! 😊

[priya-kinthali]

Hello @krystof-k 👋,
Just wanted to kindly follow up on my previous comment regarding the updates. Could you please address the suggested modifications at your earliest convenience? Thank you!

[krystof-k]

Hey, @priya-kinthali, yeah, I will do it, I just haven't had the time yet.

[priya-kinthali]

Hello @krystof-k👋,
Just a gentle reminder to kindly sync your branch with the latest changes from the main branch and address the suggested modifications. Thank you!

[lmvysakh]

Hello @krystof-k👋,
Just another reminder to kindly make the suggested changes and modifications as soon as possible. Thank you!

[krystof-k]

Sorry, I was just too busy. I was actually planning to do it today, but @lmvysakh was faster with the #1105. I did it anyway, so merge whatever you like.

[priya-kinthali]

Hello @krystof-k👋,
Thank you for addressing the suggested fixes and updating the PR! We noticed that in utils.test.ts, versions like 3.15 and 3.14.2 are being used, which haven't been officially released yet. Could you please update the test file to use existing, valid Python versions instead? This will help ensure the tests remain accurate and relevant. Thanks again for your contributions!

[krystof-k]

@priya-kinthali done ;)

[lmvysakh]

Hello @krystof-k 👋🏻,

Thanks for updating the tests! However, Python 3.14 is currently a pre-release version and is not yet available as a stable release. To ensure the tests are accurate, could you please update the test cases to use the latest stable versions of Python (such as 3.13 or earlier)? We noticed that in utils.test.ts, the pypy version used( pypy3.14-7.3.19 ) is invalid. Could you please update the test file to use existing, valid pypy versions instead?

Also in the following code snippet:

const pythonVersionFileContent =
        '3.14/envs/virtualenv\r# 3.14\n3.13\r\n3.12\r\n 3.11 \r\n';
      fs.writeFileSync(pythonVersionFilePath, pythonVersionFileContent);

It looks like the same version appears twice in pythonVersionFileContent. Once as part of '3.14/envs/virtualenv' and once as a commented-out version ('# 3.14'). To avoid confusion and better demonstrate the comment behavior, could you please use different versions? Thank you!

[krystof-k]

@priya-kinthali OK, I tried once more, I hope you will be satisfied this time, although I see no difference if using released or unreleased versions if the test only parses and compares text :)