@@ -54,6 +54,24 @@ Build a wheel and an sdist (tarball) from the package.
54
54
55
55
Generating ``setup.py `` disabled by default.
56
56
57
+ .. option :: --use-vcs
58
+
59
+ Use the files checked in to git or mercurial as the starting list to include
60
+ in an sdist, and then apply inclusions and exclusions :ref: `from pyproject.toml
61
+ <pyproject_toml_sdist>`.
62
+
63
+ This is the default for now, but we're planning to switch to ``--no-use-vcs ``
64
+ as the default in a future version.
65
+
66
+ .. option :: --no-use-vcs
67
+
68
+ Create the sdist starting with only the files inside the installed module
69
+ or package, along with any inclusions and exclusions defined in pyproject.toml.
70
+
71
+ With this option, sdists from ``flit build `` are equivalent to those built
72
+ by tools calling Flit as a backend, such as `build
73
+ <https://pypa-build.readthedocs.io/en/stable/> `_.
74
+
57
75
.. _publish_cmd :
58
76
59
77
``flit publish ``
@@ -70,19 +88,12 @@ or another repository.
70
88
You should normally publish the two formats together.
71
89
72
90
.. option :: --setup-py
73
-
74
- Generate a ``setup.py `` file in the sdist, so it can be installed by older
75
- versions of pip.
76
-
77
91
.. option :: --no-setup-py
92
+ .. option :: --use-vcs
93
+ .. option :: --no-use-vcs
78
94
79
- Don't generate a setup.py file in the sdist. This is the default.
80
- An sdist built without this will only work with tools that support PEP 517,
81
- but the wheel will still be usable by any compatible tool.
82
-
83
- .. versionchanged :: 3.5
84
-
85
- Generating ``setup.py `` disabled by default.
95
+ These options affecting what goes in the sdist are described for
96
+ :ref: `build_cmd ` above.
86
97
87
98
.. option :: --repository <repository >
88
99
0 commit comments