pants export [args]
Export Pants data for use in other tools, such as IDEs.
Export the specified resolve(s). The export format is backend-specific, e.g., Python resolves are exported as virtualenvs.
Export Python resolves using this format. Options are:
mutable_virtualenv: Export a standalone mutable virtualenv that you can
symlinked_immutable_virtualenv: Export a symlink into a cached Python virtualenv.
This virtualenv will have no pip binary, and will be immutable. Any attempt to
modify it will corrupt the cache! It may, however, take significantly less time
to export than a standalone, mutable virtualenv.
--export-py-editable-in-resolve="['<str>', '<str>', ...]"
When exporting a mutable virtualenv for a resolve, do PEP-660 editable installs of all 'python_distribution' targets that own code in the exported resolve.
If a resolve name is not in this list, 'python_distribution' targets will not be installed in the virtualenv. This defaults to an empty list for backwards compatibility and to prevent unnecessary work to generate and install the PEP-660 editable wheels.
This only applies when '[python].enable_resolves' is true and when exporting a 'mutable_virtualenv' ('symlinked_immutable_virtualenv' exports are not "full" virtualenvs because they must not be edited, and do not include 'pip').
NOTE: If you are using legacy exports (not using the '--resolve' option), then this option has no effect. Legacy exports will not include any editable installs.
Deprecated, is scheduled to be removed in version: 2.20.0.dev0.
Set the `[export].py_resolve_format` option to 'symlinked_immutable_virtualenv'
Export a symlink into a cached Python virtualenv. This virtualenv will have no pip binary, and will be immutable. Any attempt to modify it will corrupt the cache! It may, however, take significantly less time to export than a standalone, mutable virtualenv will.
Updated 26 days ago