This file contains invisible Unicode characters that are indistinguishable to humans but may be processed differently by a computer. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.
TASK: Create a Python virtual environment named 'venv_test' in the current directory.
[215300] File "/tmp/r_python_WafFzp.py", line 4, in <module>
[215300] venv.create('venv_test', with_pip=True)
[215300] ~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[215300] File "/usr/lib/python3.13/venv/__init__.py", line 619, in create
[215300] builder.create(env_dir)
[215300] ~~~~~~~~~~~~~~^^^^^^^^^
[215300] File "/usr/lib/python3.13/venv/__init__.py", line 80, in create
[215300] self.setup_python(context)
[215300] ~~~~~~~~~~~~~~~~~^^^^^^^^^
[215300] File "/usr/lib/python3.13/venv/__init__.py", line 304, in setup_python
[215300] copier(context.executable, path)
[215300] ~~~~~~^^^^^^^^^^^^^^^^^^^^^^^^^^
[215300] File "/usr/lib/python3.13/venv/__init__.py", line 277, in symlink_or_copy
[215300] shutil.copyfile(src, dst)
[215300] ~~~~~~~~~~~~~~~^^^^^^^^^^
[215300] File "/usr/lib/python3.13/shutil.py", line 240, in copyfile
[215300] raise SameFileError("{!r} and {!r} are the same file".format(src, dst))
[215300] shutil.SameFileError: '/usr/bin/python3.13' and '/home/retoor/projects/r/venv_test/bin/python3.13' are the same file
The attempt to create a virtual environment named 'venv_test' failed because the script tried to create it in the current directory, which already contains a Python executable with the same name. To resolve this, I will delete any existing 'venv_test' directory if it exists, then recreate the virtual environment.
-> Applying patch to: ./
patch: **** Only garbage was found in the patch input.
It appears that applying a patch to delete the existing 'venv_test' directory and then recreate it failed. I will manually delete the directory if it exists, then create the virtual environment again.
-> Applying patch to: ./
patch: **** Only garbage was found in the patch input.
The patch application continues to fail. I will now manually delete the 'venv_test' directory if it exists, then create the virtual environment using a direct command.