install and uninstal Poetry on Windows #145

Comments

jeremy886 commented May 27, 2018

Hi, thanks for making this tool. I’m not very familiar with developing processes and still learning about it.

I can’t tell if Poetry supports Windows from the documentation but I tried it anyway and it worked!

Great news. Maybe make it explicit in the docs? I think Poetry can easily become more popular if it can attract a tiny fraction of Windows users. (For example, I’m a teacher, 90% of my students use Windows and 100% of my school) I use both though.

I installed Poetry this way and it was installed to the Python directory in my home directory (Windows).
curl -sSL https://raw.githubusercontent.com/sdispater/poetry/master/get-poetry.py | python

What is the recommended way to uninstall it?

I find Poetry interesting and definitely will explore it further.

The text was updated successfully, but these errors were encountered:

Victor-Savu commented May 27, 2018

poetry can be uninstalled using pip uninstall poetry . Do you have any proposal as to how to update the documentation in order to make the uninstallation and the Windows availability more easily discoverable?

jeremy886 commented May 27, 2018

Thanks Victor-Savu. It worked.

Out of curiosity I tried pip install poetry again and got massive influx of packages (shown when I did pip list ). I used pip-autoremove to save the day. One thing I like about poetry is that it can remove an installed package and its dependencies (pip/conda can’t do it) but I don’t think I could use poetry to remove itself.

Then I wondered how it hid these before and looked up «vendorizing» and found the _vendor folder in site-packages. (I thought it was in the home directory). Nice!

If PRs are welcome here, I can add a few lines here and there to README.md.

Victor-Savu commented May 27, 2018

You’re welcome, @jeremy886!
My guess would be that you could open a PR for the README and/or for the docs, but @sdispater is the one putting in most of the hard work, so he is the best person to ask about contributing to poetry 🙂

No colors in Windows Terminal or cmd #1972

Comments

sztomi commented Feb 4, 2020 •

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: Windows 10.0.18362.592 Poetry version: 1.0.3 Link of a Gist with the contents of your pyproject.toml file: n/a

Issue

This is #548 which was said to be fixed in «the latest beta» at the time, but now appears to be broken with no beta being more recent than the latest released version (1.0.3).

Long story short, there are no colors displayed on windows with any of the command shells I tried except in ConEmu. The default cmd.exe, powershell.exe and the new Windows Terminal don’t display colors.

Powershell in Windows Terminal:

Cmd in Windows Terminal:

Cmd in Cmder (based on ConEmu) — This works!:

Powershell in Cmder (based on ConEmu):

This last one can probably be considered working as well, the green text is likely due to the cmder config.

The text was updated successfully, but these errors were encountered:

Мелкая питонячая радость #3: Poetry

Управление зависимостями? Шо, опять?

Экосистема Python породила целую пачку способов управления зависимостями в проектах.
Прямо сейчас можно выбирать между setup.py, requirements.txt, setup.cfg, MANIFEST.in и Pipfile.
Но французского питониста Sébastien Eustace все эти способы не устроили, и он написал свою штуку для менеджмента питонячих пакетов — Poetry. Зачем он это сделал? Чтобы заменить все эти setup.py, requirements.txt, setup.cfg, MANIFEST.in и Pipfile чем-то простым и понятным. Плюс добавить кое-что полезное сверху.

Poetry позволяет рулить сразу кучей вещей — версией языка в вашем проекте, зависимостями, подключаемыми путями, скриптами тестирования/разработки, сборкой и публикацией билдов.Все необходимые пути, зависимости и скрипты описываются в специальном файле pyproject.toml.

Poetry лучше всего работает в паре с pyenv — системой управления множественными версиями Python и виртуальными окружениями.

Щупаем

Засучим рукава и посмотрим, как poetry работает в деле. Первым делом ставим pyenv, следуя официальной инструкции в доках.

Среда установлена и настроена, зависимости управляются одним пальцем, можно пилить код!

У вас, скорее всего, появятся в проекте команды запуска сервера, воркеров, скриптов деплоя и тестирования. Их можно засунуть в pyproject.toml и тоже рулить ими одним пальцем.

Добавляем в файл

и теперь можно запускать скрипт командой

Зачем это все?

Потратив десяток минут на освоение этой штуки, вы сэкономите время и нервы на управлении версиями языка и пакетов, отслеживании зависимостей и настройке путей. Особенно это поможет тем, кто хоть раз пробовал опубликовать свои наработки в pip 🙂

• Резолвер зависимостей, способный всегда найти решение конфликтам версий пакетов (если оно вообще существует)
• Автоматическое создание изолированных сред для запускапроектов.
• Приятная консольная утилита, которая здорово упрощает запуск, тесты и деплой проектов.

Poetry прекасно дружит с другими управлялками виртуальными средами, так что интегрировать новый подход в старые проекты будет очень легко.

poetry 1.1.6

pip install poetry Copy PIP instructions

Released: Apr 14, 2021

Python dependency management and packaging made easy.

Navigation

Project links

Statistics

View statistics for this project via Libraries.io, or by using our public dataset on Google BigQuery

License: MIT License (MIT)

Tags packaging, dependency, poetry

Requires: Python >=2.7, !=3.0.*, !=3.1.*, !=3.2.*, !=3.3.*, !=3.4.*

Maintainers

Classifiers

• License
  • OSI Approved :: MIT License
• Programming Language
  • Python :: 2
  • Python :: 2.7
  • Python :: 3
  • Python :: 3.5
  • Python :: 3.6
  • Python :: 3.7
  • Python :: 3.8
  • Python :: 3.9
• Topic
  • Software Development :: Build Tools
  • Software Development :: Libraries :: Python Modules

Project description

Poetry: Dependency Management for Python

Poetry 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.

Installation

Poetry provides a custom installer that will install poetry isolated from the rest of your system by vendorizing its dependencies. This is the recommended way of installing poetry .

Alternatively, you can download the get-poetry.py file 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)
• python3
• py.exe -3 (Windows)
• py.exe -2 (Windows)

If you want to install prerelease versions, you can do so by passing —preview to get-poetry.py :

Similarly, if you want to install a specific version, you can use —version :

Using pip to install poetry is also possible.

Be aware, however, that it will also install poetry’s dependencies which might cause conflicts.

Updating poetry

Updating poetry to the latest stable version is as simple as calling the self update command.

If you want to install prerelease versions, you can use the —preview option.

And finally, if you want to install a specific version you can pass it as an argument to self update .

Enable tab completion for Bash, Fish, or Zsh

poetry supports generating completion scripts for Bash, Fish, and Zsh. See poetry help completions for full details, but the gist is as simple as using one of the following:

Note: you may need to restart your shell in order for the changes to take effect.

For zsh , you must then add the following line in your

/.zshrc before compinit (not for homebrew setup):

Introduction

poetry is 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, standardized pyproject.toml .

In other words, poetry uses pyproject.toml to replace setup.py , requirements.txt , setup.cfg , MANIFEST.in and the newly added Pipfile .

There are some things we can notice here:

• It will try to enforce semantic versioning as the best practice in version naming.
• You can specify the readme, included and excluded files: no more MANIFEST.in . poetry will also use VCS ignore files (like .gitignore ) to populate the exclude section.
• 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.

poetry will also detect if you are inside a virtualenv and install the packages accordingly. So, poetry can be installed globally and used everywhere.

poetry also comes with a full fledged dependency resolution library.

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.in and the newly added Pipfile .

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, like composer (PHP) or cargo (Rust).

And, finally, there is no reliable tool to properly resolve dependencies in Python, so I started poetry to 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 resolution

The dependency resolution is erratic and will fail even if there is a solution. Let’s take an example:

will fail with this error:

while Poetry will get you the right set of packages:

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:

What interests us is pbr (>=0.6,!=0.7, .

At this point, poetry will choose pbr==0.11.1 which is the latest version that matches the constraint.

Poetry in the windows

Poetry: Dependency Management for Python

Poetry 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.

Poetry provides a custom installer that will install poetry isolated from the rest of your system.

osx / linux / bashonwindows install instructions

windows powershell install instructions

Warning: The previous get-poetry.py installer is now deprecated, if you are currently using it you should migrate to the new, supported, install-poetry.py installer.

The installer installs the poetry tool to Poetry’s bin directory. This location depends on you system:

• $HOME/.local/bin for Unix
• %APPDATA%\Python\Scripts on Windows

If this directory is not on you PATH , you will need to add it manually if you want to invoke Poetry with simply poetry .

Alternatively, you can use the full path to poetry to use it.

Once Poetry is installed you can execute the following:

If you see something like Poetry (version 1.2.0) then you are ready to use Poetry. If you decide Poetry isn’t your thing, you can completely remove it from your system by running the installer again with the —uninstall option or by setting the POETRY_UNINSTALL environment variable before executing the installer.

By default, Poetry is installed into the user’s platform-specific home directory. If you wish to change this, you may define the POETRY_HOME environment variable:

If you want to install prerelease versions, you can do so by passing —preview option to install-poetry.py or by using the POETRY_PREVIEW environment variable:

Similarly, if you want to install a specific version, you can use —version option or the POETRY_VERSION environment variable:

You can also install Poetry for a git repository by using the —git option:

Note: Note that the installer does not support Python

Updating poetry to the latest stable version is as simple as calling the self update command.

If you want to install prerelease versions, you can use the —preview option.

And finally, if you want to install a specific version you can pass it as an argument to self update .

Enable tab completion for Bash, Fish, or Zsh

poetry supports generating completion scripts for Bash, Fish, and Zsh. See poetry help completions for full details, but the gist is as simple as using one of the following:

Note: you may need to restart your shell in order for the changes to take effect.

For zsh , you must then add the following line in your

/.zshrc before compinit (not for homebrew setup):

poetry is 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, standardized pyproject.toml .

In other words, poetry uses pyproject.toml to replace setup.py , requirements.txt , setup.cfg , MANIFEST.in and the newly added Pipfile .

There are some things we can notice here:

• It will try to enforce semantic versioning as the best practice in version naming.
• You can specify the readme, included and excluded files: no more MANIFEST.in . poetry will also use VCS ignore files (like .gitignore ) to populate the exclude section.
• 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.

poetry will also detect if you are inside a virtualenv and install the packages accordingly. So, poetry can be installed globally and used everywhere.

poetry also comes with a full fledged dependency resolution library.

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.in and the newly added Pipfile .

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, like composer (PHP) or cargo (Rust).

And, finally, I started poetry to bring another exhaustive dependency resolver to the Python community apart from Conda’s.

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.

The dependency resolution is erratic and will fail even if there is a solution. Let’s take an example:

will fail with this error:

while Poetry will get you the right set of packages:

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:

What interests us is pbr (>=0.6,!=0.7, .

At this point, poetry will choose pbr==0.11.1 which is the latest version that matches the constraint.