You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+69-31Lines changed: 69 additions & 31 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -6,15 +6,15 @@ The test directory structure for Python and Java projects will often follow conv
6
6
Below, are typical structures for both languages, which help in organizing tests based on their type (e.g., unit tests, functional tests, integration tests).
7
7
8
8
9
+
## Project
9
10
```
10
11
dialoget/
11
12
│
12
13
├── src/
13
14
│ └── dialoget.py # Python file with code for the package
14
15
│
15
16
├── tests/ # Unit tests for the package
16
-
│ ├── dialoget.py
17
-
│ └── test_module2.py
17
+
│ └── dialoget.py
18
18
│
19
19
├── docs/ # Documentation for the package
20
20
│ ├── conf.py
@@ -23,67 +23,105 @@ dialoget/
23
23
│
24
24
├── README.md # README file with a description of the package, installation instructions, etc.
25
25
├── LICENSE # License file specifying how the package can be used and shared
26
-
├── setup.py # Setuptools script for installation and distribution of the package
26
+
├── pyproject.toml # Setuptools script for installation and distribution of the package
27
27
├── setup.cfg # Configuration settings for setuptools
28
28
├── requirements.txt # File listing all dependencies for the package
29
29
└── .gitignore # Specifies intentionally untracked files to ignore for git
30
30
```
31
31
32
32
33
+
## Usage
33
34
34
-
## Build
35
+
```bash
36
+
pip install dialoget==0.0.1
37
+
```
38
+
39
+
40
+
## Contribution
41
+
42
+
To update a release of a Python package, you'll typically go through the following general steps:
43
+
44
+
1. Update the code or documentation to incorporate the new changes or improvements.
45
+
46
+
2. Update the package version number to indicate a new release:
47
+
- Follow semantic versioning (or "semver") principles, using version numbers like MAJOR.MINOR.PATCH:
48
+
- Increment the MAJOR version when you make incompatible API changes,
49
+
- Increment the MINOR version when you add functionality in a backward-compatible manner, and
50
+
- Increment the PATCH version when you make backward-compatible bug fixes.
51
+
- Change the version number in your package's `__init__.py` file, `setup.cfg`, `pyproject.toml` file, wherever it's defined.
52
+
53
+
3. Update the `CHANGELOG` or `HISTORY` file (if you have one) to document the changes introduced in the new version.
54
+
55
+
4. Commit the changes and push them to your version control system (e.g., git).
56
+
57
+
5. Tag the commit with the version number:
58
+
```shell
59
+
git tag -a v1.0.1 -m "Release version 1.0.1"
60
+
git push --tags
61
+
```
62
+
63
+
6. Build the new distribution files for the package using your chosen build tool, typically the build package:
64
+
```shell
65
+
python -m build
66
+
```
67
+
68
+
7. Upload the new distribution files to the Python Package Index (PyPI), typically using twine:
69
+
```shell
70
+
twine upload dist/*
71
+
```
72
+
73
+
8. If your project is hosted on GitHub or a similar platform, you may also want to create a GitHub release:
74
+
- Go to the "Releases" section of your repository.
75
+
- Draft a new release, using the new tag you've created.
76
+
- Add release notes summarizing the changes.
77
+
- Optionally, attach binaries or additional files that accompany the release.
78
+
- Publish the release.
79
+
80
+
81
+
82
+
83
+
84
+
85
+
86
+
87
+
88
+
89
+
90
+
91
+
92
+
93
+
94
+
### Build
35
95
build your package, first ensure you have the latest versions of `build` and `wheel` installed:
36
96
37
97
```shell
38
98
pip install --upgrade build wheel
99
+
pip install --upgrade twine
39
100
```
40
101
41
-
## Install
102
+
###Install
42
103
Run the build module from the root of the project where the `pyproject.toml` file is located:
43
104
44
105
```shell
45
-
python -m build
106
+
python -m build --version 0.0.2
46
107
```
47
-
48
108
This command will generate distribution files in the newly created `dist/` directory within your project. You will find both a source archive (`.tar.gz`) and a wheel file (`.whl`).
0 commit comments