Package: poetry-windows-fix
Poetry: Dependency Management for PythonPoetry helps you declare, manage and install dependencies of Python projects,
ensuring you have the right stack everywhere.It supports Python 2.7 and 3.5+.Note: Python 2.7 and 3.5 will no longer be supported in the next feature release (1.2).
You should consider updating your Python version to a supported one.Thecomplete documentationis available on theofficial website.InstallationPoetry provides a custom installer that will installpoetryisolated
from the rest of your system by vendorizing its dependencies. This is the
recommended way of installingpoetry.Note:Theget-poetry.pyscript described here will be replaced in Poetry 1.2 byinstall-poetry.py.
From Poetry1.1.7 onwards, you can already use this script as describedhere.curl-sSLhttps://raw.githubusercontent.com/python-poetry/poetry/master/get-poetry.py|pythonAlternatively, you can download theget-poetry.pyfile and execute it separately.The setup script must be able to find one of following executables in your shell's path environment:python(which can be a py3 or py2 interpreter)python3py.exe -3(Windows)py.exe -2(Windows)If you want to install prerelease versions, you can do so by passing--previewtoget-poetry.py:pythonget-poetry.py--previewSimilarly, if you want to install a specific version, you can use--version:pythonget-poetry.py--version0.7.0Usingpipto installpoetryis also possible.pipinstall--userpoetryBe aware, however, that it will also install poetry's dependencies
which might cause conflicts.UpdatingpoetryUpdating poetry to the latest stable version is as simple as calling theself updatecommand.poetryselfupdateIf you want to install prerelease versions, you can use the--previewoption.poetryselfupdate--previewAnd finally, if you want to install a specific version you can pass it as an argument
toself update.poetryselfupdate1.0.0Note:If you are still on poetry version < 1.0 use `poetry self:update` instead.Enable tab completion for Bash, Fish, or Zshpoetrysupports generating completion scripts for Bash, Fish, and Zsh.
Seepoetry help completionsfor full details, but the gist is as simple as using one of the following:# Bashpoetrycompletionsbash>/etc/bash_completion.d/poetry.bash-completion# Bash (Homebrew)poetrycompletionsbash>$(brew--prefix)/etc/bash_completion.d/poetry.bash-completion# Fishpoetrycompletionsfish>~/.config/fish/completions/poetry.fish# Fish (Homebrew)poetrycompletionsfish>(brew--prefix)/share/fish/vendor_completions.d/poetry.fish# Zshpoetrycompletionszsh>~/.zfunc/_poetry# Zsh (Homebrew)poetrycompletionszsh>$(brew--prefix)/share/zsh/site-functions/_poetry# Zsh (Oh-My-Zsh)mkdir$ZSH_CUSTOM/plugins/poetry
poetrycompletionszsh>$ZSH_CUSTOM/plugins/poetry/_poetry# Zsh (prezto)poetrycompletionszsh>~/.zprezto/modules/completion/external/src/_poetryNote:you may need to restart your shell in order for the changes to take
effect.Forzsh, you must then add the following line in your~/.zshrcbeforecompinit(not for homebrew setup):fpath+=~/.zfuncIntroductionpoetryis a tool to handle dependency installation as well as building and packaging of Python packages.
It only needs one file to do all of that: the new,standardizedpyproject.toml.In other words, poetry usespyproject.tomlto replacesetup.py,requirements.txt,setup.cfg,MANIFEST.inand the newly addedPipfile.[tool.poetry]name="my-package"version="0.1.0"description="The description of the package"license="MIT"authors=["Sébastien Eustace <sebastien@eustace.io>"]readme='README.md'# Markdown files are supportedrepository="https://github.com/python-poetry/poetry"homepage="https://github.com/python-poetry/poetry"keywords=['packaging','poetry'][tool.poetry.dependencies]python="~2.7 || ^3.2"# Compatible python versions must be declared heretoml="^0.9"# Dependencies with extrasrequests={version="^2.13",extras=["security"]}# Python specific dependencies with prereleases allowedpathlib2={version="^2.2",python="~2.7",allow-prereleases=true}# Git dependenciescleo={git="https://github.com/sdispater/cleo.git",branch="master"}# Optional dependencies (extras)pendulum={version="^1.4",optional=true}[tool.poetry.dev-dependencies]pytest="^3.0"pytest-cov="^2.4"[tool.poetry.scripts]my-script='my_package:main'There are some things we can notice here:It will try to enforcesemantic versioningas the best practice in version naming.You can specify the readme, included and excluded files: no moreMANIFEST.in.poetrywill also use VCS ignore files (like.gitignore) to populate theexcludesection.Keywords (up to 5) can be specified and will act as tags on the packaging site.The dependencies sections support caret, tilde, wildcard, inequality and multiple requirements.You must specify the python versions for which your package is compatible.poetrywill also detect if you are inside a virtualenv and install the packages accordingly.
So,poetrycan be installed globally and used everywhere.poetryalso comes with a full fledged dependency resolution library.Why?Packaging systems and dependency management in Python are rather convoluted and hard to understand for newcomers.
Even for seasoned developers it might be cumbersome at times to create all files needed in a Python project:setup.py,requirements.txt,setup.cfg,MANIFEST.inand the newly addedPipfile.So I wanted a tool that would limit everything to a single configuration file to do:
dependency management, packaging and publishing.It takes inspiration in tools that exist in other languages, likecomposer(PHP) orcargo(Rust).And, finally, there is no reliable tool to properly resolve dependencies in Python, so I startedpoetryto bring an exhaustive dependency resolver to the Python community.What about Pipenv?In short: I do not like the CLI it provides, or some of the decisions made,
and I think we can make a better and more intuitive one. Here are a few things
that I don't like.Dependency resolutionThe dependency resolution is erratic and will fail even if there is a solution. Let's take an example:pipenvinstalloslo.utils==1.4.0will fail with this error:Could not find a version that matches pbr!=0.7,!=2.1.0,<1.0,>=0.6,>=2.0.0while Poetry will get you the right set of packages:poetryaddoslo.utils=1.4.0results in :- Installing pytz (2018.3)
  - Installing netifaces (0.10.6)
  - Installing netaddr (0.7.19)
  - Installing oslo.i18n (2.1.0)
  - Installing iso8601 (0.1.12)
  - Installing six (1.11.0)
  - Installing babel (2.5.3)
  - Installing pbr (0.11.1)
  - Installing oslo.utils (1.4.0)This is possible thanks to the efficient dependency resolver at the heart of Poetry.Here is a breakdown of what exactly happens here:oslo.utils (1.4.0)depends on:pbr (>=0.6,!=0.7,<1.0)Babel (>=1.3)six (>=1.9.0)iso8601 (>=0.1.9)oslo.i18n (>=1.3.0)netaddr (>=0.7.12)netifaces (>=0.10.4)What interests us ispbr (>=0.6,!=0.7,<1.0).At this point, poetry will choosepbr==0.11.1which is the latest version that matches the constraint.Next it will try to selectoslo.i18n==3.20.0which is the latest version that matchesoslo.i18n (>=1.3.0).However this version requirespbr (!=2.1.0,>=2.0.0)which is incompatible withpbr==0.11.1,
sopoetrywill try to find a version ofoslo.i18nthat satisfiespbr (>=0.6,!=0.7,<1.0).By analyzing the releases ofoslo.i18n, it will findoslo.i18n==2.1.0which requirespbr (>=0.11,<2.0).
At this point the rest of the resolution is straightforward since there is no more conflict.ResourcesOfficial WebsiteIssue TrackerDiscord