From 2187e457ebf842f5162917bfa3868560bee081ab Mon Sep 17 00:00:00 2001 From: DMRobertson Date: Fri, 15 Jul 2022 15:19:30 +0000 Subject: deploy: e9ce4d089bbb013f870bbc8d58ec796e8f315eb4 --- develop/development/dependencies.html | 15 +++++++++++++++ 1 file changed, 15 insertions(+) (limited to 'develop/development') diff --git a/develop/development/dependencies.html b/develop/development/dependencies.html index 19cf215053..813ffbcf0a 100644 --- a/develop/development/dependencies.html +++ b/develop/development/dependencies.html @@ -321,6 +321,21 @@ be required.

because build is a standardish tool which doesn't require poetry. (It's what we use in CI too). However, you could try poetry build too.

+

Troubleshooting

+

Check the version of poetry with poetry --version.

+

At the time of writing, the 1.2 series is beta only. We have seen some examples +where the lockfiles generated by 1.2 prereleasese aren't interpreted correctly +by poetry 1.1.x. For now, use poetry 1.1.14, which includes a critical +change needed to remain +compatible with PyPI.

+

It can also be useful to check the version of poetry-core in use. If you've +installed poetry with pipx, try pipx runpip poetry list | grep poetry-core.

+

Clear caches: poetry cache clear --all pypi.

+

Poetry caches a bunch of information about packages that isn't readily available +from PyPI. (This is what makes poetry seem slow when doing the first +poetry install.) Try poetry cache list and poetry cache clear --all <name of cache> to see if that fixes things.

+

Try --verbose or --dry-run arguments.

+

Sometimes useful to see what poetry's internal logic is.

-- cgit 1.5.1