PosixPath TypeError with `poetry install` on 0.12.1
See original GitHub issue- I am on the latest Poetry version.
- I have searched the issues of this repo and believe that this is not a duplicate.
- If an exception occurs when executing a command, I executed it again in debug mode (
-vvv
option).
- OS version and name: MacOS 10.13.6
- Poetry version: Poetry 0.12.1
- Link of a Gist with the contents of your pyproject.toml file: https://gist.github.com/phobologic/07c8a56f7f97b981ac046b9ee8d09a64
Issue
We’ve been using poetry internally at my company for a project for a while now and it has worked well, but since updating to poetry .12.1, whenever we do a poetry install in a fresh (blank) environment, we end up getting this error:
[TypeError]
coercing to Unicode: need string or buffer, PosixPath found
Exception trace:
/Users/mike/Library/Python/2.7/lib/python/site-packages/cleo/application.py in run() at line 94
status_code = self.do_run(input_, output_)
/Users/mike/Library/Python/2.7/lib/python/site-packages/poetry/console/application.py in do_run() at line 88
return super(Application, self).do_run(i, o)
/Users/mike/Library/Python/2.7/lib/python/site-packages/cleo/application.py in do_run() at line 197
status_code = command.run(input_, output_)
/Users/mike/Library/Python/2.7/lib/python/site-packages/poetry/console/commands/command.py in run() at line 77
return super(BaseCommand, self).run(i, o)
/Users/mike/Library/Python/2.7/lib/python/site-packages/cleo/commands/base_command.py in run() at line 136
self.initialize(input_, output_)
/Users/mike/Library/Python/2.7/lib/python/site-packages/poetry/console/commands/env_command.py in initialize() at line 16
o, self.poetry.package.name, cwd=self.poetry.file.parent
/Users/mike/Library/Python/2.7/lib/python/site-packages/poetry/console/commands/command.py in poetry() at line 62
return self.get_application().poetry
/Users/mike/Library/Python/2.7/lib/python/site-packages/poetry/console/application.py in poetry() at line 60
self._poetry = Poetry.create(os.getcwd())
/Users/mike/Library/Python/2.7/lib/python/site-packages/poetry/poetry.py in create() at line 191
shutil.move(old_lock, lock)
/System/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/shutil.py in move() at line 283
if os.path.isdir(dst):
/System/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/genericpath.py in isdir() at line 49
st = os.stat(s)
install [--no-dev] [--dry-run] [-E|--extras EXTRAS] [--develop DEVELOP]
Thanks for any help you can provide!
Issue Analytics
- State:
- Created 5 years ago
- Reactions:1
- Comments:6 (2 by maintainers)
Top Results From Across the Web
Poetry 0.12.1 is out | Blog
This chapter will tell you how to make your library installable through Poetry. Versioning Poetry requires PEP 440-compliant versions for all ...
Read more >Changelog — prospector documentation
Fixed the exit code for prospector - it was always 0 after the move to using poetry for packaging instead of 1 if...
Read more >xonsh: Versions | Openbase
Changed: When there is no git repository, the values of all gitstatus prompt fields are now None . With $THREAD_SUBPROCS=False : When a...
Read more >poetry - PyPI
Poetry helps you declare, manage and install dependencies of Python projects, ensuring you have the right stack everywhere. Poetry Install.
Read more >Poetry doesn't use the correct version of Python - Stack Overflow
I've reinstalled Python 3.8 again with Pyenv, but when I hit Poetry install I get the following error: The currently activated Python version ......
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
@phobologic Yes please. It will be easier to track the issue that way.
I just published the
0.12.2
release which should fix the issue!