diff options
Diffstat (limited to 'docs')
| -rw-r--r-- | docs/pkg_resources.rst | 2 | ||||
| -rw-r--r-- | docs/python 2 sunset.rst | 2 | ||||
| -rw-r--r-- | docs/userguide/dependency_management.rst | 2 | ||||
| -rw-r--r-- | docs/userguide/quickstart.rst | 8 |
4 files changed, 7 insertions, 7 deletions
diff --git a/docs/pkg_resources.rst b/docs/pkg_resources.rst index 994bea6f..2ba10134 100644 --- a/docs/pkg_resources.rst +++ b/docs/pkg_resources.rst @@ -1229,7 +1229,7 @@ Resource Extraction If you are implementing an ``IResourceProvider`` and/or ``IMetadataProvider`` for a new distribution archive format, you may need to use the following -``IResourceManager`` methods to co-ordinate extraction of resources to the +``IResourceManager`` methods to coordinate extraction of resources to the filesystem. If you're not implementing an archive format, however, you have no need to use these methods. Unlike the other methods listed above, they are *not* available as top-level functions tied to the global ``ResourceManager``; diff --git a/docs/python 2 sunset.rst b/docs/python 2 sunset.rst index f7b7ee25..225d6551 100644 --- a/docs/python 2 sunset.rst +++ b/docs/python 2 sunset.rst @@ -50,7 +50,7 @@ versions of Setuptools installed, here are some things to try. Then ``pip install setuptools``. 2. If possible, attempt to replicate the problem in a second environment (virtual machine, friend's computer, etc). If the issue is isolated to just - one unique enviornment, first determine what is different about those + one unique environment, first determine what is different about those environments (or reinstall/reset the failing one to defaults). 3. End users who are not themselves the maintainers for the package they are trying to install should contact the support channels for the relevant diff --git a/docs/userguide/dependency_management.rst b/docs/userguide/dependency_management.rst index 188083e0..c6333a10 100644 --- a/docs/userguide/dependency_management.rst +++ b/docs/userguide/dependency_management.rst @@ -250,7 +250,7 @@ dependencies for it to work: } ) -The name ``PDF`` is an arbitary identifier of such a list of dependencies, to +The name ``PDF`` is an arbitrary identifier of such a list of dependencies, to which other components can refer and have them installed. There are two common use cases. diff --git a/docs/userguide/quickstart.rst b/docs/userguide/quickstart.rst index a9f0bbae..5d4dd37b 100644 --- a/docs/userguide/quickstart.rst +++ b/docs/userguide/quickstart.rst @@ -173,7 +173,7 @@ Including Data Files ==================== The distutils have traditionally allowed installation of "data files", which are placed in a platform-specific location. Setuptools offers three ways to -specify data files to be included in your packages. For the simpliest use, you +specify data files to be included in your packages. For the simplest use, you can simply use the ``include_package_data`` keyword: .. code-block:: ini @@ -189,7 +189,7 @@ For more details, see :doc:`datafiles` Development mode ================ ``setuptools`` allows you to install a package without copying any files -to your interpretor directory (e.g. the ``site-packages`` directory). This +to your interpreter directory (e.g. the ``site-packages`` directory). This allows you to modify your source code and have the changes take effect without you having to rebuild and reinstall. This is currently incompatible with PEP 517 and therefore it requires a ``setup.py`` script with the following @@ -202,7 +202,7 @@ Then:: pip install --editable . -This creates a link file in your interpretor site package directory which +This creates a link file in your interpreter site package directory which associate with your source code. For more information, see: (WIP) @@ -216,7 +216,7 @@ basic use here. Transitioning from ``setup.py`` to ``setup.cfg`` ================================================ -To avoid executing arbitary scripts and boilerplate code, we are transitioning +To avoid executing arbitrary scripts and boilerplate code, we are transitioning into a full-fledged ``setup.cfg`` to declare your package information instead of running ``setup()``. This inevitably brings challenges due to a different syntax. Here we provide a quick guide to understanding how ``setup.cfg`` is |