Skip to content

Commit 5b711c7

Browse files
committed
finish version
1 parent e58de64 commit 5b711c7

File tree

3 files changed

+12
-75
lines changed

3 files changed

+12
-75
lines changed

CONTRIBUTING.md

Lines changed: 10 additions & 65 deletions
Original file line numberDiff line numberDiff line change
@@ -4,79 +4,24 @@ If you would like to contribute to pointers.py, just make a pull request with yo
44

55
Any pull request should include the following:
66

7-
- Type safe and provides type annotations
8-
- PEP 8 compliant code
9-
- Passes tests specified in the [tests](https://github.com/ZeroIntensity/pointers.py/tree/master/tests) directory
10-
- Documentation updated accordingly
7+
- Type safe and provides type annotations
8+
- PEP 8 compliant code
9+
- Passes tests specified in the [tests](https://github.com/ZeroIntensity/pointers.py/tree/master/tests) directory
10+
- Documentation updated accordingly
1111

1212
## Running tests
1313

14-
You can install the tests by installing dependencies in the `requirements_dev.txt` file:
14+
Pointers.py uses [pre-commit](https://pre-commit.com/) and [pytest](https://docs.pytest.org/en/7.1.x/) for running tests.
1515

16-
```
17-
pip install -r requirements_dev.txt
18-
```
19-
20-
### Mypy
21-
22-
Mypy type checks the code.
23-
24-
You can run it with the following command:
25-
26-
```
27-
python3 -m mypy src
28-
```
29-
30-
### Flake8
31-
32-
Flake8 ensures that the codebase is compliant to [PEP 8](https://peps.python.org/pep-0008/).
33-
34-
Heres how you run it:
35-
36-
```
37-
python3 -m flake8 src
38-
```
39-
40-
### Pytest
41-
42-
Pytest handles all unit tests for pointers.py
43-
44-
Run it by simply using:
16+
To get pre-commit running, simply run the following:
4517

4618
```
47-
python3 -m pytest
19+
$ pip install pre-commit
20+
$ pre-commit install
4821
```
4922

50-
### Tox
51-
52-
Tox runs all 3 of the above in different python environments:
23+
Then, just install pytest:
5324

5425
```
55-
python3 -m tox
26+
$ pip install pytest
5627
```
57-
58-
Please note that running tox is extremely slow and can take several minutes.
59-
60-
## Running documentation
61-
62-
Start with installing [mkdocs](https://pypi.org/project/mkdocs/):
63-
64-
```
65-
python3 -m pip install -U mkdocs
66-
```
67-
68-
To build the documentation, run the following command:
69-
70-
```
71-
python3 -m mkdocs build
72-
```
73-
74-
This will build the site in the `site/` directory.
75-
76-
However, constantly building can be annoying, so you can use `serve` instead:
77-
78-
```
79-
python3 -m mkdocs serve
80-
```
81-
82-
This will automatically rebuild when you change a file.

README.md

Lines changed: 0 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -70,11 +70,3 @@ python3 -m pip install -U pointers.py
7070
```
7171
py -3 -m pip install -U pointers.py
7272
```
73-
74-
### Running Documentation
75-
76-
```
77-
$ git clone https://github.com/ZeroIntensity/pointers.py && cd pointers.py
78-
$ pip install -U mkdocs
79-
$ mkdocs serve
80-
```

docs/movement.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -40,7 +40,7 @@ b = to_ptr("abcdefg")
4040
a.move(b) # InvalidSizeError
4141
```
4242

43-
This can be bypassed by passing `unsafe = True` to `move`:
43+
This can be bypassed by passing `unsafe=True` to `move`:
4444

4545
```py
4646
a = to_ptr("test")
@@ -98,7 +98,7 @@ print(~ptr)
9898

9999
## Consequences
100100

101-
After you are finished crying from accidentally overwriting your newborn child using this library, what actually happens when we break something with overwriting?
101+
What actually happens when we break something with overwriting?
102102

103103
Lets use the following code as an example:
104104

0 commit comments

Comments
 (0)