question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Poetry 0.12.2 installer doesn't modify PATH or install required jsonschema

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.4 / Docker (FROM python:3.6.5)
  • Poetry version: 0.12.2
  • Link of a Gist with the contents of your pyproject.toml file: N/A

Issue

When performing a fresh install using get-poetry.py $HOME/.poetry/bin doesn’t get added to the PATH like in previous releases.

Secondly, after running poetry self:update (or a fresh install using the get-poetry.py) poetry crashes with any command.

[AttributeError]
module ‘jsonschema’ has no attribute ‘Draft7Validator’

run <args> (<args>)…

I had to update jsonschema manually to get it to work.

pip install --upgrade jsonschema --pre

Issue Analytics

  • State:closed
  • Created 5 years ago
  • Reactions:15
  • Comments:16 (8 by maintainers)

github_iconTop GitHub Comments

15reactions
sdispatercommented, Oct 19, 2018

Poetry will not be available in the current shell after installation you have to execute:

source $HOME/.poetry/env

For the jsonchema problem, you best bet is to uninstall the currently installed Poetry version, especially if you come from 0.11.5, and reinstall it using get-poetry.py.

3reactions
jordanhamillcommented, Oct 22, 2018

Building a docker image doesn’t use a single shell instance across RUN commands so the $HOME/.poetry/env wont work, nor will RUN bash -c "EXPORT PATH='/root/.poetry/bin:$PATH'.

I’m happy with the work around of explicitly modifying the PATH but that would indicate that the installer isn’t doing what it says it is doing in all scenarios. I haven’t dug through the difference between the installers but I’m curious as to why it worked pre 0.12.0. It seems like a regression as the change log doesn’t mention this being intentional.

Read more comments on GitHub >

github_iconTop Results From Across the Web

schemathesis 1.2.0 - PyPI
Schemathesis is a tool for testing your web applications built with Open API / Swagger specifications. It reads the application schema and generates...
Read more >
could not install packages due to an oserror: [errno 2] no such ...
I have a feeling something somewhere broke my Python or Pip installation, causing it to not have a path to install dependencies in....
Read more >
Search Results - CVE
A relative path traversal vulnerability in a FileUtil class used by the PEAR management component of Apache UIMA allows an attacker to create...
Read more >
External Packages - SageMath Documentation
It installs them automatically if it does not find equivalent system packages. • _prereq: Represents system packages required for installing ...
Read more >
Untitled
... bcel.spec bcrypt-1.1.tar.gz bcrypt-change-man-install-path.patch bcrypt.spec ... add-variable-to-forbid-tmp-dir.patch backport-add-Requires-cloud-init- ...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found