pdm venv create does not default to venv.location when .venv exists.

[laenan8466]

• I have searched the issue tracker and believe that this is not a duplicate.

Steps to reproduce

1. Project creation

pdm init # Create a new project

with parameters resulting in this pyproject.toml:

[project]
name = ""
version = ""
description = ""
authors = [
    {name = "", email = ""},
]
dependencies = []
requires-python = ">=3.10"
readme = "README.md"
license = {text = "MIT"}

and creating a new venv with the pyenv global setting on 3.11 during the init command.

2. 2nd venv
   Now creating another venv:

pdm venv create -v 3.10

Actual behavior

STATUS: Creating virtualenv using virtualenv...
[VirtualenvCreateError]: The location /path/to/project/.venv is not empty, add --force to overwrite it.

No creation of 2nd venv.

Expected behavior

I would have expected pdm to create the 2nd venv in venv.location, like described in the documentation.

Environment Information

PDM version:
  2.10.1
Python Interpreter:
  /path/to/project/.venv/bin/python (3.11)
Project Root:
  /path/to/project
Local Packages:
  
{
  "implementation_name": "cpython",
  "implementation_version": "3.11.6",
  "os_name": "posix",
  "platform_machine": "x86_64",
  "platform_release": "5.15.90.1-microsoft-standard-WSL2",
  "platform_system": "Linux",
  "platform_version": "#1 SMP Fri Jan 27 02:56:13 UTC 2023",
  "python_full_version": "3.11.6",
  "platform_python_implementation": "CPython",
  "python_version": "3.11",
  "sys_platform": "linux"
}

[frostming]

It seems like a mistake not implemented as desired. But I am not sure if anyone is relying on this behavior.

[laenan8466]

This would have been a feature for test-automation and creation of multiple venvs for a project.
Solved this for me by using a setup script (pawamoy/copier-pdm#36).

Would recommend to clarify in docs, that this is not the actual behavior. Can be tracked here or closed, your decision.

[frostming]

Okay, I will update the docs to reflect the actual behavior.