@@ -32,7 +32,7 @@ Here's how to get started with your code contribution:
32
32
33
33
1 . Create your own fork of redis-py
34
34
2 . Do the changes in your fork
35
- 3 .
35
+ 3 .
36
36
* Create a virtualenv and install the development dependencies from the dev_requirements.txt file:*
37
37
38
38
a. python -m venv .venv
@@ -69,12 +69,12 @@ configuration](https://redis.io/topics/sentinel).
69
69
70
70
## Testing
71
71
72
- Call ` invoke tests ` to run all tests, or ` invoke all-tests ` to run linters
73
- tests as well. With the 'tests' and 'all-tests' targets, all Redis and
74
- RedisCluster tests will be run.
72
+ Call ` invoke tests ` to run all tests, or ` invoke all-tests ` to run linters
73
+ tests as well. With the 'tests' and 'all-tests' targets, all Redis and
74
+ RedisCluster tests will be run.
75
75
76
- It is possible to run only Redis client tests (with cluster mode disabled) by
77
- using ` invoke standalone-tests ` ; similarly, RedisCluster tests can be run by using
76
+ It is possible to run only Redis client tests (with cluster mode disabled) by
77
+ using ` invoke standalone-tests ` ; similarly, RedisCluster tests can be run by using
78
78
` invoke cluster-tests ` .
79
79
80
80
Each run of tox starts and stops the various dockers required. Sometimes
@@ -85,9 +85,7 @@ tests against multiple versions of python. Feel free to test your
85
85
changes against all the python versions supported, as declared by the
86
86
tox.ini file (eg: tox -e py39). If you have the various python versions
87
87
on your desktop, you can run * tox* by itself, to test all supported
88
- versions. Alternatively, as your source code is mounted in the
89
- ** lots-of-pythons** docker, you can start exploring from there, with all
90
- supported python versions!
88
+ versions.
91
89
92
90
### Docker Tips
93
91
0 commit comments