Command Line Tools
The tools can also be invoked using the -m command line option of the
Python interpreter. For example, the following two command lines are
equivalent:
sip-build -h
python -m sipbuild.tools.build -h
Note that, for the build tools, the command line options described in this
section are the standard options. Any of these options could be removed, or
new options added, by build system extensions including project-specific
project.py files.
sip-build
sip-build builds a project but does not install it. This is useful when developing a set of bindings.
The syntax of the sip-build command line is:
sip-build [options]
The full set of command line options is:
- -h, --help
Display a help message.
- -V, --version
Display the SIP version number.
- --deprecations-are-errors
The use of any deprecated feature is handled as an error rather than a warning.
- --quiet
All progress messages are disabled.
- --verbose
Verbose progress messages are enabled.
- --abi-version M[.N]
The version number of the ABI of the
sipmodule to target isM.N. By default the latest major version is used. If the minor version is not specified then the latest minor version of the major version is used.
- --api-dir DIR
A QScintilla
.apifile is created inDIR.
- --build-dir DIR
DIRis created as a build directory in which all generated files will be created. The build directory is not removed after the build has been completed. The default value isbuild.
- --concatenate N
The generated code is split into
Nfiles. By default one file is generated for each C structure or C++ class. Specifying a low value ofNcan significantly speed up the build of large projects.
- --disable NAME
The
NAMEbindings are disabled and will not be built. This option may be specified multiple times. It is only available if the project contains multiple sets of bindings.
- --disabled-feature TAG
The
TAGfeature tag is disabled. This option may be specified multiple times.
- --enable NAME
The
NAMEbindings are enabled and will be built. Any associated configuration tests that would normally be run to determine if the bindings should be built are suppressed. This option may be specified multiple times. It is only available if the project contains multiple sets of bindings.
- --debug
A build with debugging symbols is performed.
- --no-compile
The compilation of the generated code is disabled.
- --no-docstrings
The generation of docstrings that describe the signature of all functions, methods and constructors is disabled.
- --no-version-info
No reference the SIP version number is included in any generated code.
- --pep484-pyi
The generation of Python type hints stub files is enabled. These files contain a description of a module’s API that is compliant with PEP 484.
- --protected-is-public
SIP can generate code to provide access to protected C++ functions from Python. On non-Windows platforms this code can be avoided if the
protectedkeyword is redefined aspublicduring compilation. This can result in a significant reduction in the size of a generated Python module. This option enables the redefinition ofprotectedand is the default on all platforms except Windows.
- --no-protected-is-public
This option disables the redefinition of
protectedto access protected C++ functions from Python and is the default on Windows.
- --scripts-dir DIR
Any project scripts will eventually be installed in
DIR. IfDIRis relative then it is taken as relative to the target directory. By default the directory containing the Python interpreter is used.
- --target-dir DIR
The project will eventually be installed in
DIR. By default it is thesite-packagesdirectory of the Python installation.
- --tracing
Debugging statements that trace the execution of the bindings are automatically generated. By default the statements are not generated.
sip-distinfo
sip-distinfo creates and populates a .dist-info directory of
an installation or a wheel. It is provided for build systems that extend the
SIP build system and need to create the .dist-info directory from an
external tool such as make.
The syntax of the sip-distinfo command line is:
sip-distinfo [options] directory
directory is the full path name of the directory to create.
The full set of command line options is:
- -h, --help
Display a help message.
- -V, --version
Display the SIP version number.
- --console-script ENTRY-POINT
The console entry point
ENTRY-POINTis added to the wheel. It is ignored if the--wheel-tagoption is not specified. This option may be specified multiple times.
- --generator NAME
If the
--wheel-tagoption is specified thenNAMEis written as part of theGeneratorin theWHEELfile in the.dist-infodirectory. OtherwiseNAMEis written to theINSTALLERfile. By defaultsipbuildis written.
- --generator-version VERSION
VERSIONis written as part of theGeneratorin theWHEELfile in the.dist-infodirectory. By default the SIP version number is written.
- --gui-script ENTRY-POINT
The GUI entry point
ENTRY-POINTis added to the wheel. It is ignored if the--wheel-tagoption is not specified. This option may be specified multiple times.
- --inventory FILE
FILEcontains a list of the relative names of the files, one per line, that comprise the installation or wheel contents. This option must be specified.
- --metadata NAME[=VALUE]
VALUEis used instead of any value specified forNAMEin the[tool.sip.metadata]section of thepyproject.tomlfile.
- --prefix DIR
This option is provided as an aid to Linux package builders.
DIRis used to pass the commonly used values ofDESTDIRorINSTALL_ROOT. If specified it should have a trailing native path separator.
- --project-root DIR
The name of the directory containing the project’s
pyproject.tomlfile isDIR. This option must be specified.
- --requires-dist EXPR
EXPRis added to the list of prerequisites written to theMETADATAfile in the.dist-infodirectory. It is normally used to specify a particular version of a package project’ssipmodule. This option may be specified multiple times.
- --sbom FILE
Added in version 6.13.
FILEis copied to thesbomssubdirectory of the.dist-infodirectory as defined in PEP 770.FILEmay be a glob-style pattern. This option may be specified multiple times.
- --wheel-tag TAG
TAGis written as theTagin theWHEELfile in the.dist-infodirectory.
sip-install
sip-install builds and installs a project.
The syntax of the sip-install command line is:
sip-install [options]
The full set of command line options is:
- -h, --help
Display a help message.
- -V, --version
Display the SIP version number.
- --deprecations-are-errors
The use of any deprecated feature is handled as an error rather than a warning.
- --quiet
All progress messages are disabled.
- --verbose
Verbose progress messages are enabled.
- --abi-version M[.N]
The version number of the ABI of the
sipmodule to target isM.N. By default the latest major version is used. If the minor version is not specified then the latest minor version of the major version is used.
- --api-dir DIR
A QScintilla
.apifile is created inDIR.
- --build-dir DIR
DIRis created as a build directory in which all generated files will be created. This build directory is not removed after the build has been completed. By default a temporary build directory is created which is removed after the build has been completed.
- --concatenate N
The generated code is split into
Nfiles. By default one file is generated for each C structure or C++ class. Specifying a low value ofNcan significantly speed up the build of large projects.
- --disable NAME
The
NAMEbindings are disabled and will not be built. This option may be specified multiple times. It is only available if the project contains multiple sets of bindings.
- --disabled-feature TAG
The
TAGfeature tag is disabled. This option may be specified multiple times.
- --enable NAME
The
NAMEbindings are enabled and will be built. Any associated configuration tests that would normally be run to determine if the bindings should be built are suppressed. This option may be specified multiple times. It is only available if the project contains multiple sets of bindings.
- --debug
A build with debugging symbols is performed.
- --no-docstrings
The generation of docstrings that describe the signature of all functions, methods and constructors is disabled.
- --no-distinfo
The creation of the
.dist-infodirectory is disabled.
- --pep484-pyi
The generation of Python type hints stub files is enabled. These files contain a description of a module’s API that is compliant with PEP 484.
- --protected-is-public
SIP can generate code to provide access to protected C++ functions from Python. On non-Windows platforms this code can be avoided if the
protectedkeyword is redefined aspublicduring compilation. This can result in a significant reduction in the size of a generated Python module. This option enables the redefinition ofprotectedand is the default on all platforms except Windows.
- --no-protected-is-public
This option disables the redefinition of
protectedto access protected C++ functions from Python and is the default on Windows.
- --scripts-dir DIR
Any project scripts will be installed in
DIR. IfDIRis relative then it is taken as relative to the target directory. By default the directory containing the Python interpreter is used.
- --target-dir DIR
The project will be installed in
DIR. By default it is thesite-packagesdirectory of the Python installation.
- --tracing
Debugging statements that trace the execution of the bindings are automatically generated. By default the statements are not generated.
sip-module
sip-module builds one of more of the elements of the sip
module for a set of package projects.
The syntax of the sip-module command line is:
sip-module [options] name
name is the fully qualified name of the sip module (i.e. including
the package name).
The full set of command line options is:
- -h, --help
Display a help message.
- -V, --version
Display the SIP version number.
- --abi-version MAJOR[.MINOR]
The major version number of the ABI implemented by the
sipmodule isMAJOR. If a minor version number is also specified it is interpreted as a minimum minor version rather than the exact minor version to be used. By default the very latest version is used.
- --option NAME
The
sipmodule will be built using theNAMEconfiguration option. See the%SipModuleConfigurationdirective for a list of possible options and their meanings. This option may be specified multiple times.
- --project NAME
The name of the project as it would appear on PyPI is
NAME. By default the name is derived from the fully qualified name of thesipmodule.
- --sdist
Create an sdist which can then be installed by pip or uploaded to PyPI.
pip can also be used to create a wheel from the sdist. However, for Linux wheels, auditwheel must be run for the wheel before it can be uploaded to PyPI.
- --setup-cfg FILE
FILEis copied to the sdist assetup.cfginstead of the default version. This allows the sdist to be customised. A number of macros may be specified in thesetup.cfgfile:@SIP_MODULE_FQ_NAME@is replaced by the fully qualified name of thesipmodule.@SIP_MODULE_PACKAGE_NAME@is replaced by the module’s project top-level package name.@SIP_MODULE_PROJECT_NAME@is replaced by the module’s project name as it would appear on PyPI.@SIP_MODULE_VERSION@is replaced by the version number of the module.
- --sip-h
Create a
sip.hheader file that defines the C ABI implemented by thesipmodule.
- --sip-rst
Create a
sip.rstfile that documents the Python API implemented by thesipmodule.
- --target-dir DIR
Each of the module’s elements will be created in
DIR.
sip-sdist
sip-sdist creates an sdist (a source distribution) than be uploaded to PyPI.
The syntax of the sip-sdist command line is:
sip-sdist [options]
Changed in version 6.9.1: The name of the sdist file now conforms to PEP 625 (i.e. it is all lower case).
The full set of command line options is:
- -h, --help
Display a help message.
- -V, --version
Display the SIP version number.
- --abi-version M[.N]
The version number of the ABI of the
sipmodule to target isM.N. By default the latest major version is used. If the minor version is not specified then the latest minor version of the major version is used.
- --deprecations-are-errors
The use of any deprecated feature is handled as an error rather than a warning.
- --name NAME
NAMEis used instead of the PyPI project name in thepyproject.tomlfile in the name of the sdist file.
sip-wheel
sip-wheel creates a wheel (a binary distribution) than be uploaded to PyPI.
The syntax of the sip-wheel command line is:
sip-wheel [options]
The full set of command line options is:
- -h, --help
Display a help message.
- -V, --version
Display the SIP version number.
- --deprecations-are-errors
The use of any deprecated feature is handled as an error rather than a warning.
- --quiet
All progress messages are disabled.
- --verbose
Verbose progress messages are enabled.
- --abi-version M[.N]
The version number of the ABI of the
sipmodule to target isM.N. By default the latest major version is used. If the minor version is not specified then the latest minor version of the major version is used.
- --api-dir DIR
A QScintilla
.apifile is created inDIR. This must be a name relative to the directory where the wheel will be installed.
- --build-dir DIR
DIRis created as a build directory in which all generated files will be created. This build directory is not removed after the build has been completed. By default a temporary build directory is created which is removed after the build has been completed.
- --build-tag TAG
TAGis the build tag to be used in the name of the wheel. By default the name of the wheel does not include a build tag.
- --concatenate N
The generated code is split into
Nfiles. By default one file is generated for each C structure or C++ class. Specifying a low value ofNcan significantly speed up the build of large projects.
- --disable NAME
The
NAMEbindings are disabled and will not be built. This option may be specified multiple times. It is only available if the project contains multiple sets of bindings.
- --disabled-feature TAG
The
TAGfeature tag is disabled. This option may be specified multiple times.
- --enable NAME
The
NAMEbindings are enabled and will be built. Any associated configuration tests that would normally be run to determine if the bindings should be built are suppressed. This option may be specified multiple times. It is only available if the project contains multiple sets of bindings.
- --no-manylinux
Support for
manylinuxin the platform tag of a name of a wheel is disabled. It should only be used if support for older versions of pip is required.
- --minimum-glibc-version M.N
M.Nis the minimum GLIBC version required by the project specified as the major and minor version numbers. This is used to determine the correct platform tag to use for Linux wheels. The default version of GLIBC is v2.5 which corresponds tomanylinux1. It is ignored if the--no-manylinuxoption is specified.
- --name NAME
NAMEis used instead of the PyPI project name in thepyproject.tomlfile in the name of the wheel file.
- --debug
A build with debugging symbols is performed.
- --no-docstrings
The generation of docstrings that describe the signature of all functions, methods and constructors is disabled.
- --pep484-pyi
The generation of Python type hints stub files is enabled. These files contain a description of a module’s API that is compliant with PEP 484.
- --protected-is-public
SIP can generate code to provide access to protected C++ functions from Python. On non-Windows platforms this code can be avoided if the
protectedkeyword is redefined aspublicduring compilation. This can result in a significant reduction in the size of a generated Python module. This option enables the redefinition ofprotectedand is the default on all platforms except Windows.
- --no-protected-is-public
This option disables the redefinition of
protectedto access protected C++ functions from Python and is the default on Windows.
- --tracing
Debugging statements that trace the execution of the bindings are automatically generated. By default the statements are not generated.