ivaldi 0.3.3__tar.gz → 0.3.4__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.
- {ivaldi-0.3.3 → ivaldi-0.3.4}/PKG-INFO +57 -49
- {ivaldi-0.3.3 → ivaldi-0.3.4}/README.md +56 -48
- {ivaldi-0.3.3 → ivaldi-0.3.4}/pyproject.toml +1 -1
- {ivaldi-0.3.3 → ivaldi-0.3.4}/LICENSE +0 -0
- {ivaldi-0.3.3 → ivaldi-0.3.4}/THIRD_PARTY_NOTICES.md +0 -0
- {ivaldi-0.3.3 → ivaldi-0.3.4}/ivaldi/__init__.py +0 -0
- {ivaldi-0.3.3 → ivaldi-0.3.4}/ivaldi/__main__.py +0 -0
- {ivaldi-0.3.3 → ivaldi-0.3.4}/ivaldi/commands/build.py +0 -0
- {ivaldi-0.3.3 → ivaldi-0.3.4}/ivaldi/commands/install.py +0 -0
- {ivaldi-0.3.3 → ivaldi-0.3.4}/ivaldi/commands/run.py +0 -0
- {ivaldi-0.3.3 → ivaldi-0.3.4}/ivaldi/shared/admin.py +0 -0
- {ivaldi-0.3.3 → ivaldi-0.3.4}/ivaldi/shared/alias.py +0 -0
- {ivaldi-0.3.3 → ivaldi-0.3.4}/ivaldi/shared/build.py +0 -0
- {ivaldi-0.3.3 → ivaldi-0.3.4}/ivaldi/shared/collect.py +0 -0
- {ivaldi-0.3.3 → ivaldi-0.3.4}/ivaldi/shared/extract.py +0 -0
- {ivaldi-0.3.3 → ivaldi-0.3.4}/ivaldi/shared/project.py +0 -0
- {ivaldi-0.3.3 → ivaldi-0.3.4}/ivaldi/shared/python.py +0 -0
- {ivaldi-0.3.3 → ivaldi-0.3.4}/ivaldi/shared/settings.py +0 -0
- {ivaldi-0.3.3 → ivaldi-0.3.4}/ivaldi/shared/uv.py +0 -0
- {ivaldi-0.3.3 → ivaldi-0.3.4}/ivaldi/stage/.gitkeep +0 -0
- {ivaldi-0.3.3 → ivaldi-0.3.4}/ivaldi/types/enums.py +0 -0
- {ivaldi-0.3.3 → ivaldi-0.3.4}/ivaldi/types/settings.py +0 -0
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
Metadata-Version: 2.4
|
|
2
2
|
Name: ivaldi
|
|
3
|
-
Version: 0.3.
|
|
3
|
+
Version: 0.3.4
|
|
4
4
|
Summary: Create a portable version of your Python Project
|
|
5
5
|
License-Expression: MIT
|
|
6
6
|
License-File: LICENSE
|
|
@@ -89,7 +89,7 @@ version = "3.14.5"
|
|
|
89
89
|
|
|
90
90
|
```
|
|
91
91
|
|
|
92
|
-
When no standalone configuration exists, Ivaldi extracts only `[tool.ivaldi]` and writes it to a project-root `ivaldi.toml` before building. Generated files include a schema directive and are refreshed when `[tool.ivaldi]` changes; a hand-written standalone file remains authoritative. The formal configuration definition is available in [`ivaldi.schema.json`](ivaldi.schema.json), and the same schema describes the object nested under `[tool.ivaldi]`.
|
|
92
|
+
When no standalone configuration exists, Ivaldi extracts only `[tool.ivaldi]` and writes it to a project-root `ivaldi.toml` before building. Generated files include a schema directive and are refreshed when `[tool.ivaldi]` changes; a hand-written standalone file remains authoritative. The formal configuration definition is available in [`ivaldi.schema.json`](https://github.com/FionnT/Ivaldi/blob/main/ivaldi.schema.json), and the same schema describes the object nested under `[tool.ivaldi]`.
|
|
93
93
|
|
|
94
94
|
---
|
|
95
95
|
|
|
@@ -97,56 +97,64 @@ When no standalone configuration exists, Ivaldi extracts only `[tool.ivaldi]` an
|
|
|
97
97
|
|
|
98
98
|
## Configuration Flags
|
|
99
99
|
|
|
100
|
-
All default settings and flags are visible in [the ivaldi settings dataclass](/ivaldi/types/settings.py)
|
|
100
|
+
All default settings and flags are visible in [the ivaldi settings dataclass](https://github.com/FionnT/Ivaldi/blob/main/ivaldi/types/settings.py)
|
|
101
101
|
|
|
102
102
|
|
|
103
103
|
```yaml
|
|
104
|
-
app
|
|
105
|
-
|
|
106
|
-
|
|
107
|
-
|
|
108
|
-
|
|
109
|
-
|
|
110
|
-
|
|
111
|
-
|
|
112
|
-
|
|
113
|
-
|
|
114
|
-
|
|
115
|
-
|
|
116
|
-
|
|
117
|
-
|
|
118
|
-
[
|
|
119
|
-
|
|
120
|
-
|
|
121
|
-
|
|
122
|
-
|
|
123
|
-
|
|
124
|
-
|
|
125
|
-
|
|
126
|
-
|
|
127
|
-
[
|
|
128
|
-
|
|
129
|
-
|
|
130
|
-
|
|
131
|
-
|
|
132
|
-
|
|
133
|
-
|
|
134
|
-
|
|
135
|
-
|
|
136
|
-
|
|
137
|
-
|
|
138
|
-
|
|
139
|
-
|
|
140
|
-
|
|
141
|
-
|
|
142
|
-
|
|
143
|
-
|
|
144
|
-
|
|
145
|
-
|
|
146
|
-
|
|
147
|
-
|
|
148
|
-
|
|
149
|
-
|
|
104
|
+
[app]
|
|
105
|
+
entrypoint:
|
|
106
|
+
description: The entrypoint for your application. Can be a module e.g. `mycli` or a specific command, e.g. `mycli:main`
|
|
107
|
+
type: str
|
|
108
|
+
example: mycli:main
|
|
109
|
+
include:
|
|
110
|
+
description: Controls which source files are copied to Ivaldi's clean wheel-build stage.
|
|
111
|
+
note: `pyproject.toml` is always included. Add any files referenced by the build configuration, such as a README or license.
|
|
112
|
+
type: list[glob]
|
|
113
|
+
example: ["*.py"]
|
|
114
|
+
exclude:
|
|
115
|
+
description: Specify files to exclude by a matching pattern.
|
|
116
|
+
note: If a file would be excluded, but a more specific include would include it, it is superseded by include
|
|
117
|
+
type: list[glob]
|
|
118
|
+
example: ["*.pyc"]
|
|
119
|
+
[uv,python]
|
|
120
|
+
version:
|
|
121
|
+
description: Which Python or UVX version to use for your application.
|
|
122
|
+
No compatability checks are performed, and the wrapped executable does not compile with these versions.
|
|
123
|
+
`ivaldi build` will use local Python and UV, fetching only UV if required.
|
|
124
|
+
install_args:
|
|
125
|
+
description: Are passed through to the corresponding UV, UVX, Python, and Nuitka commands.
|
|
126
|
+
note: Overwrites defaults, does not merge them.
|
|
127
|
+
type: list[flag]
|
|
128
|
+
example: ["--compile"]
|
|
129
|
+
[uv,uvx,python,nuitka]:
|
|
130
|
+
build_args:
|
|
131
|
+
description: Are passed through to the corresponding UV, UVX, Python, and Nuitka commands.
|
|
132
|
+
note: Overwrites defaults, does not merge them.
|
|
133
|
+
type: list[flag]
|
|
134
|
+
example: ["--compile",]
|
|
135
|
+
[darwin, windows, linux]:
|
|
136
|
+
location:
|
|
137
|
+
description: The name for a specific subdirectory to install the project to, inside cache directory for that platform (e.g. $HOME/local/.bin)
|
|
138
|
+
type: str
|
|
139
|
+
example: mycli
|
|
140
|
+
add_to_path:
|
|
141
|
+
description: When true, Ivaldi copies the launcher into the platform bin directory (e.g. `~/.local/bin`, `~/.bin`)
|
|
142
|
+
type: bool
|
|
143
|
+
alias:
|
|
144
|
+
description: In Unix-like systems, adds an idempotent managed alias pointing to that copy.
|
|
145
|
+
note: Attempts to locate the active shell's startup file (`.zshrc`, `.bash_profile`, `.bashrc`, Fish's `config.fish`, or `.profile` as applicable).
|
|
146
|
+
When false, no command alias is installed. Your command might still be accessible if `add_to_path` was `true`
|
|
147
|
+
type: string
|
|
148
|
+
admin:
|
|
149
|
+
description: Requires sudo/administrator privileges for installation or application runs.
|
|
150
|
+
note: Ivaldi does not elevate itself. It stops and asks to be rerun with sudo (or as Administrator on Windows).
|
|
151
|
+
values:
|
|
152
|
+
- `install` requires sudo only for first-run installation. exits after installation so the application can subsequently be run without elevation.
|
|
153
|
+
- `run` requires sudo only for running the installed application.
|
|
154
|
+
- `true` requires sudo for running and installation.
|
|
155
|
+
- `false` never requires them.
|
|
156
|
+
type: Literal[true, false, 'install', 'run']
|
|
157
|
+
[nuitka]:
|
|
150
158
|
description: Nuitka metadata is passed as `--company-name`, `--product-name`, and `--file-description`.
|
|
151
159
|
note: Relative icon paths are resolved from the wrapped project and translated to the platform-specific Nuitka icon option.
|
|
152
160
|
name:
|
|
@@ -69,7 +69,7 @@ version = "3.14.5"
|
|
|
69
69
|
|
|
70
70
|
```
|
|
71
71
|
|
|
72
|
-
When no standalone configuration exists, Ivaldi extracts only `[tool.ivaldi]` and writes it to a project-root `ivaldi.toml` before building. Generated files include a schema directive and are refreshed when `[tool.ivaldi]` changes; a hand-written standalone file remains authoritative. The formal configuration definition is available in [`ivaldi.schema.json`](ivaldi.schema.json), and the same schema describes the object nested under `[tool.ivaldi]`.
|
|
72
|
+
When no standalone configuration exists, Ivaldi extracts only `[tool.ivaldi]` and writes it to a project-root `ivaldi.toml` before building. Generated files include a schema directive and are refreshed when `[tool.ivaldi]` changes; a hand-written standalone file remains authoritative. The formal configuration definition is available in [`ivaldi.schema.json`](https://github.com/FionnT/Ivaldi/blob/main/ivaldi.schema.json), and the same schema describes the object nested under `[tool.ivaldi]`.
|
|
73
73
|
|
|
74
74
|
---
|
|
75
75
|
|
|
@@ -77,56 +77,64 @@ When no standalone configuration exists, Ivaldi extracts only `[tool.ivaldi]` an
|
|
|
77
77
|
|
|
78
78
|
## Configuration Flags
|
|
79
79
|
|
|
80
|
-
All default settings and flags are visible in [the ivaldi settings dataclass](/ivaldi/types/settings.py)
|
|
80
|
+
All default settings and flags are visible in [the ivaldi settings dataclass](https://github.com/FionnT/Ivaldi/blob/main/ivaldi/types/settings.py)
|
|
81
81
|
|
|
82
82
|
|
|
83
83
|
```yaml
|
|
84
|
-
app
|
|
85
|
-
|
|
86
|
-
|
|
87
|
-
|
|
88
|
-
|
|
89
|
-
|
|
90
|
-
|
|
91
|
-
|
|
92
|
-
|
|
93
|
-
|
|
94
|
-
|
|
95
|
-
|
|
96
|
-
|
|
97
|
-
|
|
98
|
-
[
|
|
99
|
-
|
|
100
|
-
|
|
101
|
-
|
|
102
|
-
|
|
103
|
-
|
|
104
|
-
|
|
105
|
-
|
|
106
|
-
|
|
107
|
-
[
|
|
108
|
-
|
|
109
|
-
|
|
110
|
-
|
|
111
|
-
|
|
112
|
-
|
|
113
|
-
|
|
114
|
-
|
|
115
|
-
|
|
116
|
-
|
|
117
|
-
|
|
118
|
-
|
|
119
|
-
|
|
120
|
-
|
|
121
|
-
|
|
122
|
-
|
|
123
|
-
|
|
124
|
-
|
|
125
|
-
|
|
126
|
-
|
|
127
|
-
|
|
128
|
-
|
|
129
|
-
|
|
84
|
+
[app]
|
|
85
|
+
entrypoint:
|
|
86
|
+
description: The entrypoint for your application. Can be a module e.g. `mycli` or a specific command, e.g. `mycli:main`
|
|
87
|
+
type: str
|
|
88
|
+
example: mycli:main
|
|
89
|
+
include:
|
|
90
|
+
description: Controls which source files are copied to Ivaldi's clean wheel-build stage.
|
|
91
|
+
note: `pyproject.toml` is always included. Add any files referenced by the build configuration, such as a README or license.
|
|
92
|
+
type: list[glob]
|
|
93
|
+
example: ["*.py"]
|
|
94
|
+
exclude:
|
|
95
|
+
description: Specify files to exclude by a matching pattern.
|
|
96
|
+
note: If a file would be excluded, but a more specific include would include it, it is superseded by include
|
|
97
|
+
type: list[glob]
|
|
98
|
+
example: ["*.pyc"]
|
|
99
|
+
[uv,python]
|
|
100
|
+
version:
|
|
101
|
+
description: Which Python or UVX version to use for your application.
|
|
102
|
+
No compatability checks are performed, and the wrapped executable does not compile with these versions.
|
|
103
|
+
`ivaldi build` will use local Python and UV, fetching only UV if required.
|
|
104
|
+
install_args:
|
|
105
|
+
description: Are passed through to the corresponding UV, UVX, Python, and Nuitka commands.
|
|
106
|
+
note: Overwrites defaults, does not merge them.
|
|
107
|
+
type: list[flag]
|
|
108
|
+
example: ["--compile"]
|
|
109
|
+
[uv,uvx,python,nuitka]:
|
|
110
|
+
build_args:
|
|
111
|
+
description: Are passed through to the corresponding UV, UVX, Python, and Nuitka commands.
|
|
112
|
+
note: Overwrites defaults, does not merge them.
|
|
113
|
+
type: list[flag]
|
|
114
|
+
example: ["--compile",]
|
|
115
|
+
[darwin, windows, linux]:
|
|
116
|
+
location:
|
|
117
|
+
description: The name for a specific subdirectory to install the project to, inside cache directory for that platform (e.g. $HOME/local/.bin)
|
|
118
|
+
type: str
|
|
119
|
+
example: mycli
|
|
120
|
+
add_to_path:
|
|
121
|
+
description: When true, Ivaldi copies the launcher into the platform bin directory (e.g. `~/.local/bin`, `~/.bin`)
|
|
122
|
+
type: bool
|
|
123
|
+
alias:
|
|
124
|
+
description: In Unix-like systems, adds an idempotent managed alias pointing to that copy.
|
|
125
|
+
note: Attempts to locate the active shell's startup file (`.zshrc`, `.bash_profile`, `.bashrc`, Fish's `config.fish`, or `.profile` as applicable).
|
|
126
|
+
When false, no command alias is installed. Your command might still be accessible if `add_to_path` was `true`
|
|
127
|
+
type: string
|
|
128
|
+
admin:
|
|
129
|
+
description: Requires sudo/administrator privileges for installation or application runs.
|
|
130
|
+
note: Ivaldi does not elevate itself. It stops and asks to be rerun with sudo (or as Administrator on Windows).
|
|
131
|
+
values:
|
|
132
|
+
- `install` requires sudo only for first-run installation. exits after installation so the application can subsequently be run without elevation.
|
|
133
|
+
- `run` requires sudo only for running the installed application.
|
|
134
|
+
- `true` requires sudo for running and installation.
|
|
135
|
+
- `false` never requires them.
|
|
136
|
+
type: Literal[true, false, 'install', 'run']
|
|
137
|
+
[nuitka]:
|
|
130
138
|
description: Nuitka metadata is passed as `--company-name`, `--product-name`, and `--file-description`.
|
|
131
139
|
note: Relative icon paths are resolved from the wrapped project and translated to the platform-specific Nuitka icon option.
|
|
132
140
|
name:
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|