Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Commit 5da37be

Browse files
merwokmerwok
committed
Kill trailing whitespace
1 parent 3a9f58f commit 5da37be

4 files changed

Lines changed: 30 additions & 30 deletions

File tree

‎Doc/install/pysetup-config.rst‎

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -11,8 +11,8 @@ Pysetup supports two configuration files: :file:`.pypirc` and :file:`packaging.c
1111
Configuring indexes
1212
-------------------
1313

14-
You can configure additional indexes in :file:`.pypirc` to be used for index-related
15-
operations. By default, all configured index-servers and package-servers will be used
14+
You can configure additional indexes in :file:`.pypirc` to be used for index-related
15+
operations. By default, all configured index-servers and package-servers will be used
1616
in an additive fashion. To limit operations to specific indexes, use the :option:`--index`
1717
and :option:`--package-server options`::
1818

‎Doc/install/pysetup-servers.rst‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -8,7 +8,7 @@ Pysetup supports installing Python packages from *Package Servers* in addition
88
to PyPI indexes and mirrors.
99

1010
Package Servers are simple directory listings of Python distributions. Directories
11-
can be served via HTTP or a local file system. This is useful when you want to
11+
can be served via HTTP or a local file system. This is useful when you want to
1212
dump source distributions in a directory and not worry about the full index structure.
1313

1414
Serving distributions from Apache

‎Doc/packaging/introduction.rst‎

Lines changed: 26 additions & 26 deletions
Original file line numberDiff line numberDiff line change
@@ -33,13 +33,13 @@ code, of course!) are:
3333

3434
All of these tasks are covered in this document.
3535

36-
Not all module developers have access to multiple platforms, so one cannot
36+
Not all module developers have access to multiple platforms, so one cannot
3737
expect them to create buildt distributions for every platform. To remedy
3838
this, it is hoped that intermediaries called *packagers* will arise to address
3939
this need. Packagers take source distributions released by module developers,
40-
build them on one or more platforms and release the resulting built
41-
distributions. Thus, users on a greater range of platforms will be able to
42-
install the most popular Python modules in the most natural way for their
40+
build them on one or more platforms and release the resulting built
41+
distributions. Thus, users on a greater range of platforms will be able to
42+
install the most popular Python modules in the most natural way for their
4343
platform without having to run a setup script or compile a single line of code.
4444

4545

@@ -69,14 +69,14 @@ Some observations:
6969
arguments to the :func:`setup` function
7070

7171
* those keyword arguments fall into two categories: package metadata (name,
72-
version number, etc.) and information about what's in the package (a list
72+
version number, etc.) and information about what's in the package (a list
7373
of pure Python modules in this case)
7474

7575
* modules are specified by module name, not filename (the same will hold true
7676
for packages and extensions)
7777

78-
* it's recommended that you supply a little more metadata than we have in the
79-
example. In particular your name, email address and a URL for the
78+
* it's recommended that you supply a little more metadata than we have in the
79+
example. In particular your name, email address and a URL for the
8080
project if appropriate (see section :ref:`packaging-setup-script` for an example)
8181

8282
To create a source distribution for this module you would create a setup
@@ -102,10 +102,10 @@ This simple example demonstrates some fundamental concepts of Distutils.
102102
First, both developers and installers have the same basic user interface, i.e.
103103
the setup script. The difference is which Distutils *commands* they use: the
104104
:command:`sdist` command is almost exclusively for module developers, while
105-
:command:`install` is more often used by installers (although some developers
105+
:command:`install` is more often used by installers (although some developers
106106
will want to install their own code occasionally).
107107

108-
If you want to make things really easy for your users, you can create more
108+
If you want to make things really easy for your users, you can create more
109109
than one built distributions for them. For instance, if you are running on a
110110
Windows machine and want to make things easy for other Windows users, you can
111111
create an executable installer (the most appropriate type of built distribution
@@ -125,18 +125,18 @@ by running ::
125125
General Python terminology
126126
==========================
127127

128-
If you're reading this document, you probably have a good idea of what Python
129-
modules, extensions and so forth are. Nevertheless, just to be sure that
128+
If you're reading this document, you probably have a good idea of what Python
129+
modules, extensions and so forth are. Nevertheless, just to be sure that
130130
everyone is on the same page, here's a quick overview of Python terms:
131131

132132
module
133-
The basic unit of code reusability in Python: a block of code imported by
134-
some other code. Three types of modules are important to us here: pure
133+
The basic unit of code reusability in Python: a block of code imported by
134+
some other code. Three types of modules are important to us here: pure
135135
Python modules, extension modules and packages.
136136

137137
pure Python module
138138
A module written in Python and contained in a single :file:`.py` file (and
139-
possibly associated :file:`.pyc` and/or :file:`.pyo` files). Sometimes
139+
possibly associated :file:`.pyc` and/or :file:`.pyo` files). Sometimes
140140
referred to as a "pure module."
141141

142142
extension module
@@ -148,18 +148,18 @@ extension module
148148
currently Distutils only handles C/C++ extensions for Python.
149149

150150
package
151-
A module that contains other modules, typically contained in a directory of
152-
the filesystem and distinguished from other directories by the presence of a
151+
A module that contains other modules, typically contained in a directory of
152+
the filesystem and distinguished from other directories by the presence of a
153153
file :file:`__init__.py`.
154154

155155
root package
156-
The root of the hierarchy of packages. (This isn't really a package,
157-
since it doesn't have an :file:`__init__.py` file. But... we have to
158-
call it something, right?) The vast majority of the standard library is
159-
in the root package, as are many small standalone third-party modules that
160-
don't belong to a larger module collection. Unlike regular packages,
161-
modules in the root package can be found in many directories: in fact,
162-
every directory listed in ``sys.path`` contributes modules to the root
156+
The root of the hierarchy of packages. (This isn't really a package,
157+
since it doesn't have an :file:`__init__.py` file. But... we have to
158+
call it something, right?) The vast majority of the standard library is
159+
in the root package, as are many small standalone third-party modules that
160+
don't belong to a larger module collection. Unlike regular packages,
161+
modules in the root package can be found in many directories: in fact,
162+
every directory listed in ``sys.path`` contributes modules to the root
163163
package.
164164

165165

@@ -175,8 +175,8 @@ module distribution
175175
A collection of Python modules distributed together as a single downloadable
176176
resource and meant to be installed all as one. Examples of some well-known
177177
module distributions are NumPy, SciPy, PIL (the Python Imaging
178-
Library) or mxBase. (Module distributions would be called a *package*,
179-
except that term is already taken in the Python context: a single module
178+
Library) or mxBase. (Module distributions would be called a *package*,
179+
except that term is already taken in the Python context: a single module
180180
distribution may contain zero, one, or many Python packages.)
181181

182182
pure module distribution
@@ -189,5 +189,5 @@ non-pure module distribution
189189

190190
distribution root
191191
The top-level directory of your source tree (or source distribution). The
192-
directory where :file:`setup.py` exists. Generally :file:`setup.py` will
192+
directory where :file:`setup.py` exists. Generally :file:`setup.py` will
193193
be run from this directory.

‎Doc/packaging/setupscript.rst‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -9,7 +9,7 @@ installing modules using Distutils. The main purpose of the setup script is
99
to describe your module distribution to Distutils, so that the various
1010
commands that operate on your modules do the right thing. As we saw in section
1111
:ref:`packaging-simple-example`, the setup script consists mainly of a
12-
call to :func:`setup` where the most information is supplied as
12+
call to :func:`setup` where the most information is supplied as
1313
keyword arguments to :func:`setup`.
1414

1515
Here's a slightly more involved example, which we'll follow for the next couple

0 commit comments

Comments
 (0)