Skip to content

Commit fd6f59d

Browse files
author
IvanZosimov
committed
Change contents to make them more readable
1 parent c6e66a7 commit fd6f59d

File tree

1 file changed

+7
-7
lines changed

1 file changed

+7
-7
lines changed

docs/advanced-usage.md

+7-7
Original file line numberDiff line numberDiff line change
@@ -21,7 +21,7 @@
2121

2222
## Specifying a Python version
2323

24-
If there is a specific version of Python that you need and you don't want to worry about any potential breaking changes due to patch updates (going from `3.7.5` to `3.7.6` for example), you should specify the **exact major, minor, and patch version** (such as `3.7.5`):
24+
- If there is a specific version of Python that you need and you don't want to worry about any potential breaking changes due to patch updates (going from `3.7.5` to `3.7.6` for example), you should specify the **exact major, minor, and patch version** (such as `3.7.5`):
2525

2626
```yaml
2727
steps:
@@ -34,7 +34,7 @@ steps:
3434
- The only downside to this is that set-up will take a little longer since the exact version will have to be downloaded if the exact version is not already installed on the runner due to more recent versions.
3535
- MSI installers are used on Windows for this, so runs will take a little longer to set up vs MacOS and Linux.
3636
37-
You can specify **only a major and minor version** if you are okay with the most recent patch version being used:
37+
- You can specify **only a major and minor version** if you are okay with the most recent patch version being used:
3838
3939
```yaml
4040
steps:
@@ -48,7 +48,7 @@ steps:
4848
- The patch version that will be preinstalled, will generally be the latest and every time there is a new patch released, the older version that is preinstalled will be replaced.
4949
- Using the most recent patch version will result in a very quick setup since no downloads will be required since a locally installed version of Python on the runner will be used.
5050
51-
You can specify the version with **prerelease tag** to download and set up an accurate pre-release version of Python:
51+
- You can specify the version with **prerelease tag** to download and set up an accurate pre-release version of Python:
5252
5353
```yaml
5454
steps:
@@ -59,7 +59,7 @@ steps:
5959
- run: python my_script.py
6060
```
6161
62-
It's also possible to use **x.y-dev syntax** to download and set up the latest patch version of Python, alpha and beta releases included. (for specified major & minor versions):
62+
- It's also possible to use **x.y-dev syntax** to download and set up the latest patch version of Python, alpha and beta releases included. (for specified major & minor versions):
6363
6464
```yaml
6565
steps:
@@ -70,9 +70,9 @@ steps:
7070
- run: python my_script.py
7171
```
7272
73-
You can also use several types of ranges that are specified in [semver](https://github.com/npm/node-semver#ranges), for instance:
73+
- You can also use several types of ranges that are specified in [semver](https://github.com/npm/node-semver#ranges), for instance:
7474
75-
- **[hyphen ranges](https://github.com/npm/node-semver#hyphen-ranges-xyz---abc)** to download and set up the latest available version of Python (includes both pre-release and stable versions):
75+
- **[hyphen ranges](https://github.com/npm/node-semver#hyphen-ranges-xyz---abc)** to download and set up the latest available version of Python (includes both pre-release and stable versions):
7676
7777
```yaml
7878
steps:
@@ -83,7 +83,7 @@ steps:
8383
- run: python my_script.py
8484
```
8585
86-
- **[x-ranges](https://github.com/npm/node-semver#x-ranges-12x-1x-12-)** to specify the latest stable version of Python (for specified major version):
86+
- **[x-ranges](https://github.com/npm/node-semver#x-ranges-12x-1x-12-)** to specify the latest stable version of Python (for specified major version):
8787
8888
```yaml
8989
steps:

0 commit comments

Comments
 (0)