Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

--output relative to the project directory even when running from another directory #77

Closed
touilleMan opened this issue Jun 22, 2022 · 0 comments · Fixed by #130
Closed

Comments

@touilleMan
Copy link

Poetry can be run from within a sub directory, hence the command poetry export --output foo/requirements.txt can misleading:

$ ls
my_project
pyproject.toml
$ mkdir tmp && pushd tmp  # Go in a sub directory
$ mkdir foo
$ poetry export --output foo/requirements.txt  # User expects to write into C:\\Users\\gbleu\\my_project\\tmp\\foo\\requirements.txt
[Errno 2] No such file or directory: 'C:\\Users\\gbleu\\my_project\\foo\\requirements.txt'
$ poetry export --output requirements.txt  # User expects to write into C:\\Users\\gbleu\\my_project\\tmp\\requirements.txt
$ ls
$ ls ..  # export have been actually written into C:\\Users\\gbleu\\my_project\\requirements.txt
my_project
pyproject.toml
requirements.txt
Secrus pushed a commit that referenced this issue Oct 1, 2022
Fixes: #77

Also includes:
- refactor(tests): drop custom tmp_dir fixture in favor of tmp_path
- refactor(tests): correctness and removal of dead code
- refactor(tests): simplify fixture path logic
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant