How to disable Poetry 1.1 warnings?

I’d like to hide:

Python 3.5 will no longer be supported in the next feature release of Poetry (1.2).
You should consider updating your Python version to a supported one.

Note that you will still be able to manage Python 3.5 projects by using the env command.
See https://python-poetry.org/docs/managing-environments/ for more information.

Issue Analytics

State:
Created 3 years ago
Reactions:2
Comments:16 (5 by maintainers)

Top GitHub Comments

10reactions

adamgreigcommented, Oct 2, 2020

Is there any chance of getting get-poetry.py to use python3 when it exists, in preference to python, especially now that python 2 support will be deprecated? Maybe at least if get-poetry.py is itself run under python3? This has been an issue for ages (#1042, #1257, #1494, #1878, #2106, #2222, #2352, #2547, among others); it was even briefly fixed in master until reverted by #2544. There was some more recent discussion about it in https://github.com/python-poetry/poetry/pull/2547#discussion_r449025727 too.

Specifically,

@rarenatoe the official installer based installer is designed to run on the currently active interpretor.

I don’t think that’s what actually happens in this case – it uses the first executable it finds that works, so even if the active interpreter for get-poetry.py is python3, if there’s a python installed it uses it instead, causing this issue.

On all the Ubuntu 18.04 and 20.04 systems I run, python is 2.7, python3 is 3.x, and Poetry won’t use python3 unless there’s no python available at all, no matter what the installer is run with. Consequently I still have to leave a note in my installation instructions to tell people to modify the shebang in .poetry/bin/poetry to use python3 which I’d really like to avoid. It’s not a great first experience of using Poetry!

4reactions

brechtmcommented, Oct 26, 2020

I originally posted this as a comment in #3184 (closed).

I would also expect that if running get-poetry.py with python3, python3 would be used for the shebang line. Even when I explicitly use python3 to install Poetry, I still get bothered by a big warning that Python 2 support is about to be dropped.

Sure, it’s easy enough to adjust the shebang line manually, but not when installing Poetry in an automated way.

How about simply changing the following line in get-poetry.py

allowed_executables = ["python", "python3"]

allowed_executables = ["python3", "python"]

This first tries Python 3, which doesn’t spit out a big warning message. In fact, this is how it is done for Windows:

allowed_executables += ["py.exe -3", "py.exe -2"]

Is there any reason why this would need to be different in Windows and Linux/MacOS?

Top Results From Across the Web

Introduction | Documentation | Poetry - Python dependency ...

Warning. Poetry 1.1 series releases are not able to update in-place to 1.2 or newer series releases. To migrate to newer releases, uninstall...

Dependency Management With Python Poetry

When creating a new Poetry project, you'll receive a basic folder structure right away. Remove ads. Inspect the Project Structure. The rp_poetry ......

poetry - PyPI

Poetry : Python packaging and dependency management made easy ... Poetry helps you declare, manage and install dependencies of Python projects, ensuring you...

CVE-2022-36070 Detail - NVD

References to Advisories, Solutions, and Tools ; https://github.com/python-poetry/poetry/releases/tag/1.1.9, Release Notes Third Party Advisory.

Poetry fails whenever I try to run cicd in GitHub Actions

toml. You may be getting outdated dependencies. Run update to update them. . I've tried to delete poetry.lock and run poetry ...