@@ -110,7 +110,7 @@ and check for changes in them.
110110
111111Some projects are concerned about increasing the size of source distributions,
112112or do not wish Python packaging tools to fall back to source distributions
113- automatically. In these cases, a good compromise may be to publish a separate
113+ automatically. In these cases, a good compromise may be to publish a separate
114114source archive for downstream use, for example by attaching it to a GitHub
115115release. Alternatively, large files, such as test data, can be split into
116116separate archives.
@@ -206,7 +206,7 @@ in upstream packaging may cause a number of problems for end users:
206206
207207For these reasons, you may reasonably decide to either statically link
208208your dependencies, or to provide local copies in the installed package.
209- You may also vendor the dependency in your source distribution. Sometimes
209+ You may also vendor the dependency in your source distribution. Sometimes
210210these dependencies are also repackaged on PyPI, and can be declared as
211211project dependencies like any other Python package.
212212
@@ -325,7 +325,7 @@ Some specific suggestions are:
325325- Make the test suite work offline. Mock network interactions, using
326326 packages such as responses _ or vcrpy _. If that is not possible, make it
327327 possible to easily disable the tests using Internet access, e.g. via a pytest _
328- marker. Use pytest-socket _ to verify that your tests work offline. This
328+ marker. Use pytest-socket _ to verify that your tests work offline. This
329329 often makes your own test workflows faster and more reliable as well.
330330
331331- Make your tests work without a specialized setup, or perform the necessary
0 commit comments