Bundle fails when calling from another folder than the repo itself

Using --directory option should let you run a command as if you were in the repo folder.

This fails and probably shouldn't:

poetry new -n issue_test
poetry bundle venv issue_test_bundle --directory=issue_test

  • Bundling issue-test (0.1.0) into issue_test_bundle: Installing issue-test (0.1.0)

[Errno 2] No such file or directory: '/home/clementpinard/issue_test/issue_test/issue_test/__init__.py'

As you can see, it seems that there is a confusion between directory and file discovery. the bundle plugins probably assumes that issue_test is the library folder while it's the repo folder, which happens to be named the same
As such, the issue_test/issue_test/__init__.py' relative path that gets appended to the given working folder with the --directory option.

Start by reproducing the poetry new and poetry bundle venv ... --directory=issue_test commands from outside the repository, then trace the bundle venv command's handling of the --directory entry point and relative package paths. Done means the same project bundles successfully without duplicating the repository directory in the package path.