gatemark 0.0.2__tar.gz
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- gatemark-0.0.2/PKG-INFO +90 -0
- gatemark-0.0.2/README.md +82 -0
- gatemark-0.0.2/pyproject.toml +7 -0
- gatemark-0.0.2/setup.cfg +4 -0
- gatemark-0.0.2/src/gatemark/__init__.py +1 -0
- gatemark-0.0.2/src/gatemark.egg-info/PKG-INFO +90 -0
- gatemark-0.0.2/src/gatemark.egg-info/SOURCES.txt +7 -0
- gatemark-0.0.2/src/gatemark.egg-info/dependency_links.txt +1 -0
- gatemark-0.0.2/src/gatemark.egg-info/top_level.txt +1 -0
gatemark-0.0.2/PKG-INFO
ADDED
|
@@ -0,0 +1,90 @@
|
|
|
1
|
+
Metadata-Version: 2.4
|
|
2
|
+
Name: gatemark
|
|
3
|
+
Version: 0.0.2
|
|
4
|
+
Summary: GateMark Placeholder Package
|
|
5
|
+
License-Expression: Apache-2.0
|
|
6
|
+
Requires-Python: >=3.12
|
|
7
|
+
Description-Content-Type: text/markdown
|
|
8
|
+
|
|
9
|
+
# GateMark
|
|
10
|
+
|
|
11
|
+
> [!WARNING]
|
|
12
|
+
> 0.0.2 is placeholder.
|
|
13
|
+
|
|
14
|
+
GateMark Placeholder Package.
|
|
15
|
+
|
|
16
|
+
```bash
|
|
17
|
+
pip install gatemark
|
|
18
|
+
```
|
|
19
|
+
|
|
20
|
+
---
|
|
21
|
+
|
|
22
|
+
## Publishing Guide (Placeholder & Release)
|
|
23
|
+
|
|
24
|
+
### 1. How to Update the Version Number
|
|
25
|
+
PyPI and TestPyPI enforce an **immutable release policy**: once a version (e.g. `0.0.1`) is published, it **cannot be overwritten or re-uploaded**. Whenever making updates:
|
|
26
|
+
|
|
27
|
+
1. Update the version string in `pyproject.toml`:
|
|
28
|
+
```toml
|
|
29
|
+
[project]
|
|
30
|
+
version = "0.0.2"
|
|
31
|
+
```
|
|
32
|
+
2. Update the version string in `src/gatemark/__init__.py`:
|
|
33
|
+
```python
|
|
34
|
+
__version__ = "0.0.2"
|
|
35
|
+
```
|
|
36
|
+
3. Remove old distribution files before rebuilding:
|
|
37
|
+
- **PowerShell (Windows)**:
|
|
38
|
+
```powershell
|
|
39
|
+
Remove-Item -Recurse -Force dist
|
|
40
|
+
```
|
|
41
|
+
- **Bash (Linux/macOS)**:
|
|
42
|
+
```bash
|
|
43
|
+
rm -rf dist
|
|
44
|
+
```
|
|
45
|
+
|
|
46
|
+
### 2. Prerequisites & Setup
|
|
47
|
+
|
|
48
|
+
Ensure you have Python and `uv` installed, then set up the virtual environment with build dependencies:
|
|
49
|
+
|
|
50
|
+
```bash
|
|
51
|
+
# Create virtual environment
|
|
52
|
+
uv venv
|
|
53
|
+
|
|
54
|
+
# Install build & twine
|
|
55
|
+
uv pip install build twine
|
|
56
|
+
```
|
|
57
|
+
|
|
58
|
+
### 3. Build Package
|
|
59
|
+
Clean previous artifacts and build the new distribution files:
|
|
60
|
+
|
|
61
|
+
```bash
|
|
62
|
+
uv run python -m build
|
|
63
|
+
```
|
|
64
|
+
|
|
65
|
+
The output packages will be located in the `dist/` folder (e.g., `gatemark-0.0.2.tar.gz` and `gatemark-0.0.2-py3-none-any.whl`).
|
|
66
|
+
|
|
67
|
+
### 4. Upload to TestPyPI (Verification)
|
|
68
|
+
Upload to TestPyPI to test packaging and metadata rendering:
|
|
69
|
+
|
|
70
|
+
```bash
|
|
71
|
+
uv run twine upload -r testpypi dist/*
|
|
72
|
+
```
|
|
73
|
+
|
|
74
|
+
- **Username**: `__token__`
|
|
75
|
+
- **Password**: Your TestPyPI API token (begins with `pypi-...`)
|
|
76
|
+
|
|
77
|
+
Check package rendering at: `https://test.pypi.org/project/gatemark/`
|
|
78
|
+
|
|
79
|
+
### 5. Upload to PyPI (Production)
|
|
80
|
+
Once verified on TestPyPI, publish to official PyPI:
|
|
81
|
+
|
|
82
|
+
```bash
|
|
83
|
+
uv run twine upload dist/*
|
|
84
|
+
```
|
|
85
|
+
|
|
86
|
+
- **Username**: `__token__`
|
|
87
|
+
- **Password**: Your PyPI API token (begins with `pypi-...`)
|
|
88
|
+
|
|
89
|
+
Verify the release at: `https://pypi.org/project/gatemark/`
|
|
90
|
+
|
gatemark-0.0.2/README.md
ADDED
|
@@ -0,0 +1,82 @@
|
|
|
1
|
+
# GateMark
|
|
2
|
+
|
|
3
|
+
> [!WARNING]
|
|
4
|
+
> 0.0.2 is placeholder.
|
|
5
|
+
|
|
6
|
+
GateMark Placeholder Package.
|
|
7
|
+
|
|
8
|
+
```bash
|
|
9
|
+
pip install gatemark
|
|
10
|
+
```
|
|
11
|
+
|
|
12
|
+
---
|
|
13
|
+
|
|
14
|
+
## Publishing Guide (Placeholder & Release)
|
|
15
|
+
|
|
16
|
+
### 1. How to Update the Version Number
|
|
17
|
+
PyPI and TestPyPI enforce an **immutable release policy**: once a version (e.g. `0.0.1`) is published, it **cannot be overwritten or re-uploaded**. Whenever making updates:
|
|
18
|
+
|
|
19
|
+
1. Update the version string in `pyproject.toml`:
|
|
20
|
+
```toml
|
|
21
|
+
[project]
|
|
22
|
+
version = "0.0.2"
|
|
23
|
+
```
|
|
24
|
+
2. Update the version string in `src/gatemark/__init__.py`:
|
|
25
|
+
```python
|
|
26
|
+
__version__ = "0.0.2"
|
|
27
|
+
```
|
|
28
|
+
3. Remove old distribution files before rebuilding:
|
|
29
|
+
- **PowerShell (Windows)**:
|
|
30
|
+
```powershell
|
|
31
|
+
Remove-Item -Recurse -Force dist
|
|
32
|
+
```
|
|
33
|
+
- **Bash (Linux/macOS)**:
|
|
34
|
+
```bash
|
|
35
|
+
rm -rf dist
|
|
36
|
+
```
|
|
37
|
+
|
|
38
|
+
### 2. Prerequisites & Setup
|
|
39
|
+
|
|
40
|
+
Ensure you have Python and `uv` installed, then set up the virtual environment with build dependencies:
|
|
41
|
+
|
|
42
|
+
```bash
|
|
43
|
+
# Create virtual environment
|
|
44
|
+
uv venv
|
|
45
|
+
|
|
46
|
+
# Install build & twine
|
|
47
|
+
uv pip install build twine
|
|
48
|
+
```
|
|
49
|
+
|
|
50
|
+
### 3. Build Package
|
|
51
|
+
Clean previous artifacts and build the new distribution files:
|
|
52
|
+
|
|
53
|
+
```bash
|
|
54
|
+
uv run python -m build
|
|
55
|
+
```
|
|
56
|
+
|
|
57
|
+
The output packages will be located in the `dist/` folder (e.g., `gatemark-0.0.2.tar.gz` and `gatemark-0.0.2-py3-none-any.whl`).
|
|
58
|
+
|
|
59
|
+
### 4. Upload to TestPyPI (Verification)
|
|
60
|
+
Upload to TestPyPI to test packaging and metadata rendering:
|
|
61
|
+
|
|
62
|
+
```bash
|
|
63
|
+
uv run twine upload -r testpypi dist/*
|
|
64
|
+
```
|
|
65
|
+
|
|
66
|
+
- **Username**: `__token__`
|
|
67
|
+
- **Password**: Your TestPyPI API token (begins with `pypi-...`)
|
|
68
|
+
|
|
69
|
+
Check package rendering at: `https://test.pypi.org/project/gatemark/`
|
|
70
|
+
|
|
71
|
+
### 5. Upload to PyPI (Production)
|
|
72
|
+
Once verified on TestPyPI, publish to official PyPI:
|
|
73
|
+
|
|
74
|
+
```bash
|
|
75
|
+
uv run twine upload dist/*
|
|
76
|
+
```
|
|
77
|
+
|
|
78
|
+
- **Username**: `__token__`
|
|
79
|
+
- **Password**: Your PyPI API token (begins with `pypi-...`)
|
|
80
|
+
|
|
81
|
+
Verify the release at: `https://pypi.org/project/gatemark/`
|
|
82
|
+
|
gatemark-0.0.2/setup.cfg
ADDED
|
@@ -0,0 +1 @@
|
|
|
1
|
+
__version__ = "0.0.2"
|
|
@@ -0,0 +1,90 @@
|
|
|
1
|
+
Metadata-Version: 2.4
|
|
2
|
+
Name: gatemark
|
|
3
|
+
Version: 0.0.2
|
|
4
|
+
Summary: GateMark Placeholder Package
|
|
5
|
+
License-Expression: Apache-2.0
|
|
6
|
+
Requires-Python: >=3.12
|
|
7
|
+
Description-Content-Type: text/markdown
|
|
8
|
+
|
|
9
|
+
# GateMark
|
|
10
|
+
|
|
11
|
+
> [!WARNING]
|
|
12
|
+
> 0.0.2 is placeholder.
|
|
13
|
+
|
|
14
|
+
GateMark Placeholder Package.
|
|
15
|
+
|
|
16
|
+
```bash
|
|
17
|
+
pip install gatemark
|
|
18
|
+
```
|
|
19
|
+
|
|
20
|
+
---
|
|
21
|
+
|
|
22
|
+
## Publishing Guide (Placeholder & Release)
|
|
23
|
+
|
|
24
|
+
### 1. How to Update the Version Number
|
|
25
|
+
PyPI and TestPyPI enforce an **immutable release policy**: once a version (e.g. `0.0.1`) is published, it **cannot be overwritten or re-uploaded**. Whenever making updates:
|
|
26
|
+
|
|
27
|
+
1. Update the version string in `pyproject.toml`:
|
|
28
|
+
```toml
|
|
29
|
+
[project]
|
|
30
|
+
version = "0.0.2"
|
|
31
|
+
```
|
|
32
|
+
2. Update the version string in `src/gatemark/__init__.py`:
|
|
33
|
+
```python
|
|
34
|
+
__version__ = "0.0.2"
|
|
35
|
+
```
|
|
36
|
+
3. Remove old distribution files before rebuilding:
|
|
37
|
+
- **PowerShell (Windows)**:
|
|
38
|
+
```powershell
|
|
39
|
+
Remove-Item -Recurse -Force dist
|
|
40
|
+
```
|
|
41
|
+
- **Bash (Linux/macOS)**:
|
|
42
|
+
```bash
|
|
43
|
+
rm -rf dist
|
|
44
|
+
```
|
|
45
|
+
|
|
46
|
+
### 2. Prerequisites & Setup
|
|
47
|
+
|
|
48
|
+
Ensure you have Python and `uv` installed, then set up the virtual environment with build dependencies:
|
|
49
|
+
|
|
50
|
+
```bash
|
|
51
|
+
# Create virtual environment
|
|
52
|
+
uv venv
|
|
53
|
+
|
|
54
|
+
# Install build & twine
|
|
55
|
+
uv pip install build twine
|
|
56
|
+
```
|
|
57
|
+
|
|
58
|
+
### 3. Build Package
|
|
59
|
+
Clean previous artifacts and build the new distribution files:
|
|
60
|
+
|
|
61
|
+
```bash
|
|
62
|
+
uv run python -m build
|
|
63
|
+
```
|
|
64
|
+
|
|
65
|
+
The output packages will be located in the `dist/` folder (e.g., `gatemark-0.0.2.tar.gz` and `gatemark-0.0.2-py3-none-any.whl`).
|
|
66
|
+
|
|
67
|
+
### 4. Upload to TestPyPI (Verification)
|
|
68
|
+
Upload to TestPyPI to test packaging and metadata rendering:
|
|
69
|
+
|
|
70
|
+
```bash
|
|
71
|
+
uv run twine upload -r testpypi dist/*
|
|
72
|
+
```
|
|
73
|
+
|
|
74
|
+
- **Username**: `__token__`
|
|
75
|
+
- **Password**: Your TestPyPI API token (begins with `pypi-...`)
|
|
76
|
+
|
|
77
|
+
Check package rendering at: `https://test.pypi.org/project/gatemark/`
|
|
78
|
+
|
|
79
|
+
### 5. Upload to PyPI (Production)
|
|
80
|
+
Once verified on TestPyPI, publish to official PyPI:
|
|
81
|
+
|
|
82
|
+
```bash
|
|
83
|
+
uv run twine upload dist/*
|
|
84
|
+
```
|
|
85
|
+
|
|
86
|
+
- **Username**: `__token__`
|
|
87
|
+
- **Password**: Your PyPI API token (begins with `pypi-...`)
|
|
88
|
+
|
|
89
|
+
Verify the release at: `https://pypi.org/project/gatemark/`
|
|
90
|
+
|
|
@@ -0,0 +1 @@
|
|
|
1
|
+
|
|
@@ -0,0 +1 @@
|
|
|
1
|
+
gatemark
|