8000 README: minor formatting fixes · drinkingjava/python-versioneer@6bcd9b0 · GitHub
[go: up one dir, main page]

Skip to content

Commit 6bcd9b0

Browse files
committed
README: minor formatting fixes
1 parent c47d293 commit 6bcd9b0

File tree

1 file changed

+5
-5
lines changed

1 file changed

+5
-5
lines changed

README.md

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -18,7 +18,7 @@ system, and maybe making new tarballs.
1818
## Quick Install
1919

2020
* download https://github.com/warner/python-versioneer/raw/master/versioneer.py
21-
* copy versioneer.py into the top of your source tree
21+
* copy `versioneer.py` into the top of your source tree
2222
* follow the instructions in its docstring
2323

2424
## Version Identifiers
@@ -57,13 +57,13 @@ uncommitted changes.
5757

5858
The version identifier is used for multiple purposes:
5959

60-
* to allow the module to self-identify its version: myproject.__version__
60+
* to allow the module to self-identify its version: `myproject.__version__`
6161
* to choose a name and prefix for a 'setup.py sdist' tarball
6262

6363

6464
## Theory Of Operation
6565

66-
This tool currently provides one script, named "versioneer.py". To
66+
This tool currently provides one script, named `versioneer.py`. To
6767
versioneer-enable your project, copy it into the top of your source tree,
6868
then follow the instructions in its docstring. This includes adding several
6969
lines to your setup.py (to teach the tool where your `_version.py` will live,
@@ -97,10 +97,10 @@ restriction will be fixed eventually (see issue #12).
9797

9898
This tool is designed to make it easily extended to other version-control
9999
systems: all VCS-specific components are in separate directories like
100-
src/git/ . The top-level 'versioneer.py' script is assembled from these
100+
src/git/ . The top-level `versioneer.py` script is assembled from these
101101
components by running make-versioneer.py . In the future, make-versioneer.py
102102
will take a VCS name as an argument, and will construct a version of
103-
versioneer.py that is specific to the given VCS. It might also take the
103+
`versioneer.py` that is specific to the given VCS. It might also take the
104104
configuration arguments that are currently provided manually during
105105
installation by editing setup.py . Alternatively, it might go the other
106106
direction and include code from all supported VCS systems, reducing the

0 commit comments

Comments
 (0)
0