title | draft | type | layout | menu | ||||
---|---|---|---|---|---|---|---|---|
Commands |
false |
docs |
single |
|
You've already learned how to use the command-line interface to do some things. This chapter documents all the available commands.
To get help from the command-line, simply call poetry
to see the complete list of commands,
then --help
combined with any of those can give you more information.
--verbose (-v|vv|vvv)
: Increase the verbosity of messages: "-v" for normal output, "-vv" for more verbose output and "-vvv" for debug.--help (-h)
: Display help information.--quiet (-q)
: Do not output any message.--ansi
: Force ANSI output.--no-ansi
: Disable ANSI output.--version (-V)
: Display this application version.--no-interaction (-n)
: Do not ask any interactive question.
This command will help you kickstart your new Python project by creating a directory structure suitable for most projects.
poetry new my-package
will create a folder as follows:
my-package
├── pyproject.toml
├── README.md
├── my_package
│ └── __init__.py
└── tests
└── __init__.py
If you want to name your project differently than the folder, you can pass
the --name
option:
poetry new my-folder --name my-package
If you want to use a src folder, you can use the --src
option:
poetry new --src my-package
That will create a folder structure as follows:
my-package
├── pyproject.toml
├── README.md
├── src
│ └── my_package
│ └── __init__.py
└── tests
└── __init__.py
The --name
option is smart enough to detect namespace packages and create
the required structure for you.
poetry new --src --name my.package my-package
will create the following structure:
my-package
├── pyproject.toml
├── README.md
├── src
│ └── my
│ └── package
│ └── __init__.py
└── tests
└── __init__.py
--name
: Set the resulting package name.--src
: Use the src layout for the project.--readme
: Specify the readme file format. One ofmd
(default) orrst
.
This command will help you create a pyproject.toml
file interactively
by prompting you to provide basic information about your package.
It will interactively ask you to fill in the fields, while using some smart defaults.
poetry init
--name
: Name of the package.--description
: Description of the package.--author
: Author of the package.--python
Compatible Python versions.--dependency
: Package to require with a version constraint. Should be in formatfoo:1.0.0
.--dev-dependency
: Development requirements, see--require
.
The install
command reads the pyproject.toml
file from the current project,
resolves the dependencies, and installs them.
poetry install
If there is a poetry.lock
file in the current directory,
it will use the exact versions from there instead of resolving them.
This ensures that everyone using the library will get the same versions of the dependencies.
If there is no poetry.lock
file, Poetry will create one after dependency resolution.
If you want to exclude one or more dependency group for the installation, you can use
the --without
option.
poetry install --without test,docs
{{% note %}}
The --no-dev
option is now deprecated. You should use the --without dev
notation instead.
{{% /note %}}
You can also select optional dependency groups with the --with
option.
poetry install --with test,docs
It's also possible to only install specific dependency groups by using the only
option.
poetry install --only test,docs
{{% note %}}
The --dev-only
option is now deprecated. You should use the --only dev
notation instead.
{{% /note %}}
See [Dependency groups]({{< relref "managing-dependencies#dependency-groups" >}}) for more information about dependency groups.
If you want to synchronize your environment – and ensure it matches the lock file – use the
--sync
option.
poetry install --sync
The --sync
can be combined with group-related options:
poetry install --without dev --sync
poetry install --with docs --sync
poetry install --only dev
You can also specify the extras you want installed
by passing the -E|--extras
option (See [Extras]({{< relref "pyproject#extras" >}}) for more info)
poetry install --extras "mysql pgsql"
poetry install -E mysql -E pgsql
By default poetry
will install your project's package every time you run install
:
$ poetry install
Installing dependencies from lock file
No dependencies to install or update
- Installing <your-package-name> (x.x.x)
If you want to skip this installation, use the --no-root
option.
poetry install --no-root
Installation of your project's package is also skipped when the --only
option is used.
--without
: The dependency groups to ignore for installation.--with
: The optional dependency groups to include for installation.--only
: The only dependency groups to install.--default
: Only install the default dependencies.--sync
: Synchronize the environment with the locked packages and the specified groups.--no-root
: Do not install the root package (your project).--dry-run
: Output the operations but do not execute anything (implicitly enables --verbose).--extras (-E)
: Features to install (multiple values allowed).--no-dev
: Do not install dev dependencies. (Deprecated)--dev-only
: Only install dev dependencies. (Deprecated)--remove-untracked
: Remove dependencies not presented in the lock file. (Deprecated)
In order to get the latest versions of the dependencies and to update the poetry.lock
file,
you should use the update
command.
poetry update
This will resolve all dependencies of the project and write the exact versions into poetry.lock
.
If you just want to update a few packages and not all, you can list them as such:
poetry update requests toml
Note that this will not update versions for dependencies outside their version constraints specified
in the pyproject.toml
file. In other terms, poetry update foo
will be a no-op if the version constraint
specified for foo
is ~2.3
or 2.3
and 2.4
is available. In order for foo
to be updated, you must
update the constraint, for example ^2.3
. You can do this using the add
command.
--dry-run
: Outputs the operations but will not execute anything (implicitly enables --verbose).--no-dev
: Do not install dev dependencies.--lock
: Do not perform install (only update the lockfile).
The add
command adds required packages to your pyproject.toml
and installs them.
If you do not specify a version constraint, poetry will choose a suitable one based on the available package versions.
poetry add requests pendulum
You also can specify a constraint when adding a package, like so:
poetry add pendulum@^2.0.5
poetry add "pendulum>=2.0.5"
If you try to add a package that is already present, you will get an error.
However, if you specify a constraint, like above, the dependency will be updated
by using the specified constraint. If you want to get the latest version of an already
present dependency you can use the special latest
constraint:
poetry add pendulum@latest
You can also add git
dependencies:
poetry add git+https://github.com/sdispater/pendulum.git
or use ssh instead of https:
poetry add git+ssh://[email protected]/sdispater/pendulum.git
or alternatively:
poetry add git+ssh://[email protected]:sdispater/pendulum.git
If you need to checkout a specific branch, tag or revision,
you can specify it when using add
:
poetry add git+https://github.com/sdispater/pendulum.git#develop
poetry add git+https://github.com/sdispater/pendulum.git#2.0.5
or using SSH instead:
poetry add git+ssh://github.com/sdispater/pendulum.git#develop
poetry add git+ssh://github.com/sdispater/pendulum.git#2.0.5
or make them point to a local directory or file:
poetry add ./my-package/
poetry add ../my-package/dist/my-package-0.1.0.tar.gz
poetry add ../my-package/dist/my_package-0.1.0.whl
If you want the dependency to be installed in editable mode you can use the --editable
option.
poetry add --editable ./my-package/
poetry add --editable git+ssh://github.com/sdispater/pendulum.git#develop
Alternatively, you can specify it in the pyproject.toml
file. It means that changes in the local directory will be reflected directly in environment.
[tool.poetry.dependencies]
my-package = {path = "../my/path", develop = true}
{{% note %}}
Before poetry 1.1 path dependencies were installed in editable mode by default. You should always set the develop
attribute explicit,
to make sure the behavior is the same for all poetry versions.
{{% /note %}}
If the package(s) you want to install provide extras, you can specify them when adding the package:
poetry add requests[security,socks]
poetry add "requests[security,socks]~=2.22.0"
poetry add "git+https://github.com/pallets/[email protected][dotenv,dev]"
If you want to add a package to a specific group of dependencies, you can use the --group (-G)
option:
poetry add mkdocs --group docs
See [Dependency groups]({{< relref "managing-dependencies#dependency-groups" >}}) for more information about dependency groups.
--group (-G)
: The group to add the dependency to.--dev (-D)
: Add package as development dependency. (Deprecated)--editable (-e)
: Add vcs/path dependencies as editable.--extras (-E)
: Extras to activate for the dependency. (multiple values allowed)--optional
: Add as an optional dependency.--python
: Python version for which the dependency must be installed.--platform
: Platforms for which the dependency must be installed.--source
: Name of the source to use to install the package.--allow-prereleases
: Accept prereleases.--dry-run
: Output the operations but do not execute anything (implicitly enables --verbose).--lock
: Do not perform install (only update the lockfile).
The remove
command removes a package from the current
list of installed packages.
poetry remove pendulum
If you want to remove a package from a specific group of dependencies, you can use the --group (-G)
option:
poetry remove mkdocs --group docs
See [Dependency groups]({{< relref "managing-dependencies#dependency-groups" >}}) for more information about dependency groups.
--group (-D)
: The group to remove the dependency from.--dev (-D)
: Removes a package from the development dependencies. (Deprecated)--dry-run
: Outputs the operations but will not execute anything (implicitly enables --verbose).
To list all of the available packages, you can use the show
command.
poetry show
If you want to see the details of a certain package, you can pass the package name.
poetry show pendulum
name : pendulum
version : 1.4.2
description : Python datetimes made easy
dependencies
- python-dateutil >=2.6.1
- tzlocal >=1.4
- pytzdata >=2017.2.2
required by
- calendar >=1.4.0
--without
: Do not show the information of the specified groups' dependencies.--with
: Show the information of the specified optional groups' dependencies as well.--only
: Only show the information of dependencies belonging to the specified groups.--default
: Only show the information of the default dependencies.--no-dev
: Do not list the dev dependencies.--tree
: List the dependencies as a tree.--latest (-l)
: Show the latest version.--outdated (-o)
: Show the latest version but only for packages that are outdated.
The build
command builds the source and wheels archives.
poetry build
Note that, at the moment, only pure python wheels are supported.
--format (-f)
: Limit the format to eitherwheel
orsdist
.
This command publishes the package, previously built with the build
command, to the remote repository.
It will automatically register the package before uploading if this is the first time it is submitted.
poetry publish
It can also build the package if you pass it the --build
option.
--repository (-r)
: The repository to register the package to (default:pypi
). Should match a repository name set by theconfig
command.--username (-u)
: The username to access the repository.--password (-p)
: The password to access the repository.--dry-run
: Perform all actions except upload the package.
The config
command allows you to edit poetry config settings and repositories.
poetry config --list
poetry config [options] [setting-key] [setting-value1] ... [setting-valueN]
setting-key
is a configuration option name and setting-value1
is a configuration value.
See [Configuration]({{< relref "configuration" >}}) for all available settings.
--unset
: Remove the configuration element named bysetting-key
.--list
: Show the list of current config variables.
The run
command executes the given command inside the project's virtualenv.
poetry run python -V
It can also execute one of the scripts defined in pyproject.toml
.
So, if you have a script defined like this:
[tool.poetry.scripts]
my-script = "my_module:main"
You can execute it like so:
poetry run my-script
Note that this command has no option.
The shell
command spawns a shell,
according to the $SHELL
environment variable,
within the virtual environment.
If one doesn't exist yet, it will be created.
poetry shell
Note that this commmand starts a new shell and activates the virtual environment.
As such, exit
should be used to properly exit the shell and the virtual environment instead of deactivate
.
The check
command validates the structure of the pyproject.toml
file
and returns a detailed report if there are any errors.
{{% note %}} This command is also available as a pre-commit hook. See pre-commit hooks for more information. {{% /note %}}
poetry check
This command searches for packages on a remote index.
poetry search requests pendulum
This command locks (without installing) the dependencies specified in pyproject.toml
.
{{% note %}}
By default, this will lock all dependencies to the latest available compatible versions. To only refresh the lock file, use the --no-update
option.
This command is also available as a pre-commit hook. See pre-commit hooks for more information.
{{% /note %}}
poetry lock
--check
: Verify thatpoetry.lock
is consistent withpyproject.toml
--no-update
: Do not update locked versions, only refresh lock file.
This command shows the current version of the project or bumps the version of
the project and writes the new version back to pyproject.toml
if a valid
bump rule is provided.
The new version should ideally be a valid semver string or a valid bump rule:
patch
, minor
, major
, prepatch
, preminor
, premajor
, prerelease
.
The table below illustrates the effect of these rules with concrete examples.
rule | before | after |
---|---|---|
major | 1.3.0 | 2.0.0 |
minor | 2.1.4 | 2.2.0 |
patch | 4.1.1 | 4.1.2 |
premajor | 1.0.2 | 2.0.0-alpha.0 |
preminor | 1.0.2 | 1.1.0-alpha.0 |
prepatch | 1.0.2 | 1.0.3-alpha.0 |
prerelease | 1.0.2 | 1.0.3-alpha.0 |
prerelease | 1.0.3-alpha.0 | 1.0.3-alpha.1 |
prerelease | 1.0.3-beta.0 | 1.0.3-beta.1 |
--short (-s)
: Output the version number only.
This command exports the lock file to other formats.
poetry export -f requirements.txt --output requirements.txt
{{% note %}}
Only the requirements.txt
format is currently supported.
This command is also available as a pre-commit hook. See pre-commit hooks for more information.
{{% /note %}}
--format (-f)
: The format to export to (default:requirements.txt
). Currently, onlyrequirements.txt
is supported.--output (-o)
: The name of the output file. If omitted, print to standard output.--dev
: Include development dependencies.--extras (-E)
: Extra sets of dependencies to include.--without-hashes
: Exclude hashes from the exported file.--without-urls
: Exclude source repository urls from the exported file.--with-credentials
: Include credentials for extra indices.
The env
command regroups sub commands to interact with the virtualenvs
associated with a specific project.
See [Managing environments]({{< relref "managing-environments" >}}) for more information about these commands.
The cache
command regroups sub commands to interact with Poetry's cache.
The cache list
command lists Poetry's available caches.
poetry cache list
The cache clear
command removes packages from a cached repository.
For example, to clear the whole cache of packages from the pypi
repository, run:
poetry cache clear pypi --all
To only remove a specific package from a cache, you have to specify the cache entry in the following form cache:package:version
:
poetry cache clear pypi:requests:2.24.0
The plugin
namespace regroups sub commands to manage Poetry plugins.
The plugin add
command installs Poetry plugins and make them available at runtime.
For example, to install the poetry-plugin
plugin, you can run:
poetry plugin add poetry-plugin
The package specification formats supported by the plugin add
command are the same as the ones supported
by the add
command.
If you just want to check what would happen by installing a plugin, you can use the --dry-run
option
poetry plugin add poetry-plugin --dry-run
--dry-run
: Outputs the operations but will not execute anything (implicitly enables --verbose).
The plugin show
command lists all the currently installed plugins.
poetry plugin show
The plugin remove
command removes installed plugins.
poetry plugin remove poetry-plugin
The source
namespace regroups sub commands to manage repository sources for a Poetry project.
The source add
command adds source configuration to the project.
For example, to add the pypi-test
source, you can run:
poetry source add pypi-test https://test.pypi.org/simple/
{{% note %}}
You cannot use the name pypi
as it is reserved for use by the default PyPI source.
{{% /note %}}
--default
: Set this source as the [default]({{< relref "repositories#disabling-the-pypi-repository" >}}) (disable PyPI).--secondary
: Set this source as a [secondary]({{< relref "repositories#install-dependencies-from-a-private-repository" >}}) source.
{{% note %}}
You cannot set a source as both default
and secondary
.
{{% /note %}}
The source show
command displays information on all configured sources for the project.
poetry source show
Optionally, you can show information of one or more sources by specifying their names.
poetry source show pypi-test
{{% note %}}
This command will only show sources configured via the pyproject.toml
and does not include PyPI.
{{% /note %}}
The source remove
command removes a configured source from your pyproject.toml
.
poetry source remove pypi-test