fontlab 1.0.0__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.
@@ -0,0 +1,223 @@
1
+ # Byte-compiled / optimized / DLL files
2
+ __pycache__/
3
+ *.py[codz]
4
+ *$py.class
5
+
6
+ # C extensions
7
+ *.so
8
+
9
+ # Distribution / packaging
10
+ .Python
11
+ build/
12
+ develop-eggs/
13
+ dist/
14
+ downloads/
15
+ eggs/
16
+ .eggs/
17
+ lib/
18
+ lib64/
19
+ parts/
20
+ sdist/
21
+ var/
22
+ wheels/
23
+ share/python-wheels/
24
+ *.egg-info/
25
+ .installed.cfg
26
+ *.egg
27
+ MANIFEST
28
+
29
+ # PyInstaller
30
+ # Usually these files are written by a python script from a template
31
+ # before PyInstaller builds the exe, so as to inject date/other infos into it.
32
+ *.manifest
33
+ *.spec
34
+
35
+ # Installer logs
36
+ pip-log.txt
37
+ pip-delete-this-directory.txt
38
+
39
+ # Unit test / coverage reports
40
+ htmlcov/
41
+ .tox/
42
+ .nox/
43
+ .coverage
44
+ .coverage.*
45
+ .cache
46
+ nosetests.xml
47
+ coverage.xml
48
+ *.cover
49
+ *.py.cover
50
+ *.lcov
51
+ .hypothesis/
52
+ .pytest_cache/
53
+ cover/
54
+
55
+ # Translations
56
+ *.mo
57
+ *.pot
58
+
59
+ # Django stuff:
60
+ *.log
61
+ local_settings.py
62
+ db.sqlite3
63
+ db.sqlite3-journal
64
+
65
+ # Flask stuff:
66
+ instance/
67
+ .webassets-cache
68
+
69
+ # Scrapy stuff:
70
+ .scrapy
71
+
72
+ # Sphinx documentation
73
+ docs/_build/
74
+
75
+ # PyBuilder
76
+ .pybuilder/
77
+ target/
78
+
79
+ # Jupyter Notebook
80
+ .ipynb_checkpoints
81
+
82
+ # IPython
83
+ profile_default/
84
+ ipython_config.py
85
+
86
+ # pyenv
87
+ # For a library or package, you might want to ignore these files since the code is
88
+ # intended to run in multiple environments; otherwise, check them in:
89
+ # .python-version
90
+
91
+ # pipenv
92
+ # According to pypa/pipenv#598, it is recommended to include Pipfile.lock in version control.
93
+ # However, in case of collaboration, if having platform-specific dependencies or dependencies
94
+ # having no cross-platform support, pipenv may install dependencies that don't work, or not
95
+ # install all needed dependencies.
96
+ # Pipfile.lock
97
+
98
+ # uv
99
+ # Similar to Pipfile.lock, it is generally recommended to include uv.lock in version control.
100
+ # This is especially recommended for binary packages to ensure reproducibility, and is more
101
+ # commonly ignored for libraries.
102
+ # uv.lock
103
+
104
+ # poetry
105
+ # Similar to Pipfile.lock, it is generally recommended to include poetry.lock in version control.
106
+ # This is especially recommended for binary packages to ensure reproducibility, and is more
107
+ # commonly ignored for libraries.
108
+ # https://python-poetry.org/docs/basic-usage/#commit-your-poetrylock-file-to-version-control
109
+ # poetry.lock
110
+ # poetry.toml
111
+
112
+ # pdm
113
+ # Similar to Pipfile.lock, it is generally recommended to include pdm.lock in version control.
114
+ # pdm recommends including project-wide configuration in pdm.toml, but excluding .pdm-python.
115
+ # https://pdm-project.org/en/latest/usage/project/#working-with-version-control
116
+ # pdm.lock
117
+ # pdm.toml
118
+ .pdm-python
119
+ .pdm-build/
120
+
121
+ # pixi
122
+ # Similar to Pipfile.lock, it is generally recommended to include pixi.lock in version control.
123
+ # pixi.lock
124
+ # Pixi creates a virtual environment in the .pixi directory, just like venv module creates one
125
+ # in the .venv directory. It is recommended not to include this directory in version control.
126
+ .pixi/*
127
+ !.pixi/config.toml
128
+
129
+ # PEP 582; used by e.g. github.com/David-OConnor/pyflow and github.com/pdm-project/pdm
130
+ __pypackages__/
131
+
132
+ # Celery stuff
133
+ celerybeat-schedule*
134
+ celerybeat.pid
135
+
136
+ # Redis
137
+ *.rdb
138
+ *.aof
139
+ *.pid
140
+
141
+ # RabbitMQ
142
+ mnesia/
143
+ rabbitmq/
144
+ rabbitmq-data/
145
+
146
+ # ActiveMQ
147
+ activemq-data/
148
+
149
+ # SageMath parsed files
150
+ *.sage.py
151
+
152
+ # Environments
153
+ .env
154
+ .envrc
155
+ .venv
156
+ env/
157
+ venv/
158
+ ENV/
159
+ env.bak/
160
+ venv.bak/
161
+
162
+ # Conda environments
163
+ conda-meta/
164
+
165
+ # Spyder project settings
166
+ .spyderproject
167
+ .spyproject
168
+
169
+ # Rope project settings
170
+ .ropeproject
171
+
172
+ # mkdocs/Zensical documentation
173
+ /site
174
+
175
+ # mypy
176
+ .mypy_cache/
177
+ .dmypy.json
178
+ dmypy.json
179
+
180
+ # Pyre type checker
181
+ .pyre/
182
+
183
+ # pytype static type analyzer
184
+ .pytype/
185
+
186
+ # Cython debug symbols
187
+ cython_debug/
188
+
189
+ # PyCharm
190
+ # JetBrains specific template is maintained in a separate JetBrains.gitignore that can
191
+ # be found at https://github.com/github/gitignore/blob/main/Global/JetBrains.gitignore
192
+ # and can be added to the global gitignore or merged into this file. For a more nuclear
193
+ # option (not recommended) you can uncomment the following to ignore the entire idea folder.
194
+ # .idea/
195
+
196
+ # Abstra
197
+ # Abstra is an AI-powered process automation framework.
198
+ # Ignore directories containing user credentials, local state, and settings.
199
+ # Learn more at https://abstra.io/docs
200
+ .abstra/
201
+
202
+ # Visual Studio Code
203
+ # Visual Studio Code specific template is maintained in a separate VisualStudioCode.gitignore that
204
+ # can be found at https://github.com/github/gitignore/blob/main/Global/VisualStudioCode.gitignore
205
+ # and can be added to the global gitignore or merged into this file. However, if you prefer, you
206
+ # could uncomment the following to ignore the entire vscode folder
207
+ # .vscode/
208
+ # Temporary file for partial code execution
209
+ tempCodeRunnerFile.py
210
+
211
+ # Ruff stuff:
212
+ .ruff_cache/
213
+
214
+ # PyPI configuration file
215
+ .pypirc
216
+
217
+ # Marimo
218
+ marimo/_static/
219
+ marimo/_lsp/
220
+ __marimo__/
221
+
222
+ # Streamlit
223
+ .streamlit/secrets.toml
@@ -0,0 +1,21 @@
1
+ ---
2
+ this_file: CHANGELOG.md
3
+ ---
4
+ # Changelog
5
+
6
+ ## Unreleased
7
+
8
+ - Implemented external `fontlab` API and `fontlab-cli` installation, launch,
9
+ script submission and Remopy remote operations.
10
+ - Added official release/beta appcast selection for macOS and Windows,
11
+ HTTPS downloads with length/optional SHA-256 checks, DMG installation and
12
+ elevated unattended Inno installation, preserving existing applications.
13
+ - Added explanatory native-only `fontgate` and `fontpr` distributions.
14
+ - Added shared hatch-vcs versioning, three-package builds and pypitrust OIDC helper.
15
+
16
+ - Reused pypitrust's semver release helper; publishing now runs its
17
+ `uvx gitnextver` commit/bump/push/build flow before OIDC upload.
18
+ - Corrected unattended DMG licence acceptance, preserved Remopy file-execution
19
+ semantics and exposed captured subprocess errors; 45 tests and Ruff pass.
20
+ - Verified the four live feeds and a real macOS installer download, followed by
21
+ isolated copy/detach/reuse; the running application was preserved.
@@ -0,0 +1,11 @@
1
+ ---
2
+ this_file: DEPENDENCIES.md
3
+ ---
4
+ # Dependencies
5
+
6
+ - Python 3.11+: standard-library HTTPS, XML, hashing, subprocess and file APIs.
7
+ - fontlab-remopy >=2.0.8: existing application launch and authenticated MCP client.
8
+ - hatchling and hatch-vcs: package builds and versions from shared semver git tags.
9
+ - pytest/pytest-cov and ruff: focused checks; not runtime dependencies.
10
+ - pypitrust: generated multi-package OIDC publishing helper, maintained upstream.
11
+ - macOS hdiutil/ditto and the Windows Inno installer: native installation tools.
fontlab-1.0.0/LICENSE ADDED
@@ -0,0 +1,201 @@
1
+ Apache License
2
+ Version 2.0, January 2004
3
+ http://www.apache.org/licenses/
4
+
5
+ TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
6
+
7
+ 1. Definitions.
8
+
9
+ "License" shall mean the terms and conditions for use, reproduction,
10
+ and distribution as defined by Sections 1 through 9 of this document.
11
+
12
+ "Licensor" shall mean the copyright owner or entity authorized by
13
+ the copyright owner that is granting the License.
14
+
15
+ "Legal Entity" shall mean the union of the acting entity and all
16
+ other entities that control, are controlled by, or are under common
17
+ control with that entity. For the purposes of this definition,
18
+ "control" means (i) the power, direct or indirect, to cause the
19
+ direction or management of such entity, whether by contract or
20
+ otherwise, or (ii) ownership of fifty percent (50%) or more of the
21
+ outstanding shares, or (iii) beneficial ownership of such entity.
22
+
23
+ "You" (or "Your") shall mean an individual or Legal Entity
24
+ exercising permissions granted by this License.
25
+
26
+ "Source" form shall mean the preferred form for making modifications,
27
+ including but not limited to software source code, documentation
28
+ source, and configuration files.
29
+
30
+ "Object" form shall mean any form resulting from mechanical
31
+ transformation or translation of a Source form, including but
32
+ not limited to compiled object code, generated documentation,
33
+ and conversions to other media types.
34
+
35
+ "Work" shall mean the work of authorship, whether in Source or
36
+ Object form, made available under the License, as indicated by a
37
+ copyright notice that is included in or attached to the work
38
+ (an example is provided in the Appendix below).
39
+
40
+ "Derivative Works" shall mean any work, whether in Source or Object
41
+ form, that is based on (or derived from) the Work and for which the
42
+ editorial revisions, annotations, elaborations, or other modifications
43
+ represent, as a whole, an original work of authorship. For the purposes
44
+ of this License, Derivative Works shall not include works that remain
45
+ separable from, or merely link (or bind by name) to the interfaces of,
46
+ the Work and Derivative Works thereof.
47
+
48
+ "Contribution" shall mean any work of authorship, including
49
+ the original version of the Work and any modifications or additions
50
+ to that Work or Derivative Works thereof, that is intentionally
51
+ submitted to Licensor for inclusion in the Work by the copyright owner
52
+ or by an individual or Legal Entity authorized to submit on behalf of
53
+ the copyright owner. For the purposes of this definition, "submitted"
54
+ means any form of electronic, verbal, or written communication sent
55
+ to the Licensor or its representatives, including but not limited to
56
+ communication on electronic mailing lists, source code control systems,
57
+ and issue tracking systems that are managed by, or on behalf of, the
58
+ Licensor for the purpose of discussing and improving the Work, but
59
+ excluding communication that is conspicuously marked or otherwise
60
+ designated in writing by the copyright owner as "Not a Contribution."
61
+
62
+ "Contributor" shall mean Licensor and any individual or Legal Entity
63
+ on behalf of whom a Contribution has been received by Licensor and
64
+ subsequently incorporated within the Work.
65
+
66
+ 2. Grant of Copyright License. Subject to the terms and conditions of
67
+ this License, each Contributor hereby grants to You a perpetual,
68
+ worldwide, non-exclusive, no-charge, royalty-free, irrevocable
69
+ copyright license to reproduce, prepare Derivative Works of,
70
+ publicly display, publicly perform, sublicense, and distribute the
71
+ Work and such Derivative Works in Source or Object form.
72
+
73
+ 3. Grant of Patent License. Subject to the terms and conditions of
74
+ this License, each Contributor hereby grants to You a perpetual,
75
+ worldwide, non-exclusive, no-charge, royalty-free, irrevocable
76
+ (except as stated in this section) patent license to make, have made,
77
+ use, offer to sell, sell, import, and otherwise transfer the Work,
78
+ where such license applies only to those patent claims licensable
79
+ by such Contributor that are necessarily infringed by their
80
+ Contribution(s) alone or by combination of their Contribution(s)
81
+ with the Work to which such Contribution(s) was submitted. If You
82
+ institute patent litigation against any entity (including a
83
+ cross-claim or counterclaim in a lawsuit) alleging that the Work
84
+ or a Contribution incorporated within the Work constitutes direct
85
+ or contributory patent infringement, then any patent licenses
86
+ granted to You under this License for that Work shall terminate
87
+ as of the date such litigation is filed.
88
+
89
+ 4. Redistribution. You may reproduce and distribute copies of the
90
+ Work or Derivative Works thereof in any medium, with or without
91
+ modifications, and in Source or Object form, provided that You
92
+ meet the following conditions:
93
+
94
+ (a) You must give any other recipients of the Work or
95
+ Derivative Works a copy of this License; and
96
+
97
+ (b) You must cause any modified files to carry prominent notices
98
+ stating that You changed the files; and
99
+
100
+ (c) You must retain, in the Source form of any Derivative Works
101
+ that You distribute, all copyright, patent, trademark, and
102
+ attribution notices from the Source form of the Work,
103
+ excluding those notices that do not pertain to any part of
104
+ the Derivative Works; and
105
+
106
+ (d) If the Work includes a "NOTICE" text file as part of its
107
+ distribution, then any Derivative Works that You distribute must
108
+ include a readable copy of the attribution notices contained
109
+ within such NOTICE file, excluding those notices that do not
110
+ pertain to any part of the Derivative Works, in at least one
111
+ of the following places: within a NOTICE text file distributed
112
+ as part of the Derivative Works; within the Source form or
113
+ documentation, if provided along with the Derivative Works; or,
114
+ within a display generated by the Derivative Works, if and
115
+ wherever such third-party notices normally appear. The contents
116
+ of the NOTICE file are for informational purposes only and
117
+ do not modify the License. You may add Your own attribution
118
+ notices within Derivative Works that You distribute, alongside
119
+ or as an addendum to the NOTICE text from the Work, provided
120
+ that such additional attribution notices cannot be construed
121
+ as modifying the License.
122
+
123
+ You may add Your own copyright statement to Your modifications and
124
+ may provide additional or different license terms and conditions
125
+ for use, reproduction, or distribution of Your modifications, or
126
+ for any such Derivative Works as a whole, provided Your use,
127
+ reproduction, and distribution of the Work otherwise complies with
128
+ the conditions stated in this License.
129
+
130
+ 5. Submission of Contributions. Unless You explicitly state otherwise,
131
+ any Contribution intentionally submitted for inclusion in the Work
132
+ by You to the Licensor shall be under the terms and conditions of
133
+ this License, without any additional terms or conditions.
134
+ Notwithstanding the above, nothing herein shall supersede or modify
135
+ the terms of any separate license agreement you may have executed
136
+ with Licensor regarding such Contributions.
137
+
138
+ 6. Trademarks. This License does not grant permission to use the trade
139
+ names, trademarks, service marks, or product names of the Licensor,
140
+ except as required for reasonable and customary use in describing the
141
+ origin of the Work and reproducing the content of the NOTICE file.
142
+
143
+ 7. Disclaimer of Warranty. Unless required by applicable law or
144
+ agreed to in writing, Licensor provides the Work (and each
145
+ Contributor provides its Contributions) on an "AS IS" BASIS,
146
+ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
147
+ implied, including, without limitation, any warranties or conditions
148
+ of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
149
+ PARTICULAR PURPOSE. You are solely responsible for determining the
150
+ appropriateness of using or redistributing the Work and assume any
151
+ risks associated with Your exercise of permissions under this License.
152
+
153
+ 8. Limitation of Liability. In no event and under no legal theory,
154
+ whether in tort (including negligence), contract, or otherwise,
155
+ unless required by applicable law (such as deliberate and grossly
156
+ negligent acts) or agreed to in writing, shall any Contributor be
157
+ liable to You for damages, including any direct, indirect, special,
158
+ incidental, or consequential damages of any character arising as a
159
+ result of this License or out of the use or inability to use the
160
+ Work (including but not limited to damages for loss of goodwill,
161
+ work stoppage, computer failure or malfunction, or any and all
162
+ other commercial damages or losses), even if such Contributor
163
+ has been advised of the possibility of such damages.
164
+
165
+ 9. Accepting Warranty or Additional Liability. While redistributing
166
+ the Work or Derivative Works thereof, You may choose to offer,
167
+ and charge a fee for, acceptance of support, warranty, indemnity,
168
+ or other liability obligations and/or rights consistent with this
169
+ License. However, in accepting such obligations, You may act only
170
+ on Your own behalf and on Your sole responsibility, not on behalf
171
+ of any other Contributor, and only if You agree to indemnify,
172
+ defend, and hold each Contributor harmless for any liability
173
+ incurred by, or claims asserted against, such Contributor by reason
174
+ of your accepting any such warranty or additional liability.
175
+
176
+ END OF TERMS AND CONDITIONS
177
+
178
+ APPENDIX: How to apply the Apache License to your work.
179
+
180
+ To apply the Apache License to your work, attach the following
181
+ boilerplate notice, with the fields enclosed by brackets "[]"
182
+ replaced with your own identifying information. (Don't include
183
+ the brackets!) The text should be enclosed in the appropriate
184
+ comment syntax for the file format. We also recommend that a
185
+ file or class name and description of purpose be included on the
186
+ same "printed page" as the copyright notice for easier
187
+ identification within third-party archives.
188
+
189
+ Copyright [yyyy] [name of copyright owner]
190
+
191
+ Licensed under the Apache License, Version 2.0 (the "License");
192
+ you may not use this file except in compliance with the License.
193
+ You may obtain a copy of the License at
194
+
195
+ http://www.apache.org/licenses/LICENSE-2.0
196
+
197
+ Unless required by applicable law or agreed to in writing, software
198
+ distributed under the License is distributed on an "AS IS" BASIS,
199
+ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
200
+ See the License for the specific language governing permissions and
201
+ limitations under the License.
fontlab-1.0.0/PKG-INFO ADDED
@@ -0,0 +1,112 @@
1
+ Metadata-Version: 2.5
2
+ Name: fontlab
3
+ Version: 1.0.0
4
+ Summary: Install FontLab and automate it from external Python
5
+ Project-URL: Repository, https://github.com/Fontlab/fontlab-pypi
6
+ License-Expression: Apache-2.0
7
+ License-File: LICENSE
8
+ Requires-Python: >=3.11
9
+ Requires-Dist: fontlab-remopy>=2.0.8
10
+ Description-Content-Type: text/markdown
11
+
12
+ ---
13
+ this_file: README.md
14
+ ---
15
+ # FontLab for external Python
16
+
17
+ Install FontLab 9 and automate its desktop application from ordinary Python:
18
+
19
+ ```bash
20
+ uv pip install fontlab
21
+ fontlab-cli latest --beta
22
+ fontlab-cli install --beta
23
+ fontlab-cli launch
24
+ fontlab-cli submit my-script.vfpy
25
+ fontlab-cli eval 'fontlab.__name__'
26
+ fontlab-cli run automation.py
27
+ fontlab-cli tools
28
+ fontlab-cli call list_fonts --arguments '{}'
29
+ ```
30
+
31
+ `install`, `launch`, `submit` and remote commands install FontLab automatically
32
+ when it is absent. `--beta` selects the beta appcast for a new installation;
33
+ an existing installation is reused unchanged, even if older or newer than the
34
+ feed. There is no automatic upgrade or downgrade. `latest` only reads the feed.
35
+ All command options follow the command name; `--verbose` shows a traceback.
36
+
37
+ On macOS, the default new destination is `~/Applications/FontLab 9.app`.
38
+ An existing `/Applications/FontLab 9.app` is also recognized. To select a different
39
+ bundle, pass `--destination '/path/to/FontLab 9.app'`.
40
+ On Windows, run installation from an **elevated terminal**: the shipped Inno
41
+ installer requires administrator privileges. Its default is
42
+ `%ProgramFiles%\Fontlab\FontLab 9\FontLab 9.exe`. `--destination` takes the full
43
+ executable path. Silent flags suppress setup UI and prohibit restarts or closing
44
+ applications; they cannot bypass Windows UAC. Normal launch and automation do not
45
+ need elevation after installation. Linux is unsupported.
46
+
47
+ Downloads use the official platform appcasts over HTTPS, bounded network and
48
+ installer waits, and enclosure length checks. A SHA-256 is checked if supplied
49
+ by the feed. Current feeds supply Sparkle signatures, **not SHA-256 hashes**;
50
+ this package does not verify those signatures. The unattended macOS installer automatically accepts the disk image’s licence
51
+ prompt. Use installation only if you accept FontLab’s licence terms; activation
52
+ and entitlement remain separate. The disk image is detached on copy failure. Existing destination files are never replaced intentionally.
53
+
54
+ ```python
55
+ import fontlab
56
+
57
+ fontlab.launch(beta=True)
58
+ with fontlab.connect(timeout=30) as app:
59
+ print(app.eval('fontlab.__name__'))
60
+ print(app.fonts())
61
+ ```
62
+
63
+ Automation uses [fontlab-remopy](https://github.com/fontlabcom/fontlab-remopy),
64
+ including its authenticated MCP transport and execution result handling.
65
+ `run` returns JSON with `value`, `stdout` and `stderr`; remote scripts assign
66
+ `result` for a return value. `submit` hands a `.vfpy` file to FontLab and does
67
+ not claim execution finished. On Windows file submission uses FontLab's executable;
68
+ Remopy's own native application launcher supports macOS only. A native MCP bridge
69
+ must be present for `run`, `eval`, `tools` and `call`; otherwise use `submit`.
70
+ Timeouts can mean an operation executed without a response: inspect the host
71
+ before repeating a mutating command. FontLab 9.1.9813 has a reported native bridge
72
+ crash; use script submission on affected builds rather than MCP commands.
73
+
74
+ This is **not** the native `fontlab` binary API. Use these packages only in an
75
+ external Python environment, never install them in FontLab's embedded Python.
76
+ Inside FontLab, its native `fontlab`, `fontgate` and `fontpr` modules provide the
77
+ real font-editing API. Outside it, the `fontgate` and `fontpr` PyPI distributions
78
+ are explanatory stubs that raise `ImportError`. They do not emulate native types.
79
+ FontLab licensing and activation remain the normal desktop application's process;
80
+ installation does not grant a licence or bypass activation.
81
+
82
+ ## Development and releases
83
+
84
+ ```bash
85
+ ./test.sh -q
86
+ ALLOW_DEV=1 ./build.sh # development version from git
87
+ ./release.sh # commit, patch bump, push and build all three packages
88
+ ./publish.sh # release, then upload all three through PyPI OIDC
89
+ ./publish.sh minor # or major
90
+ ```
91
+
92
+ `release.sh` reuses pypitrust's `uvx gitnextver` flow: it fetches, fast-forwards
93
+ the tracked branch, commits pending changes, bumps the semver tag and pushes
94
+ through installed hooks. A clean, already tagged HEAD is reused. Run it only
95
+ from a reviewed release checkout. `publish.sh` runs this release step first.
96
+
97
+ All three packages use the same repository tags through hatch-vcs. Build artifacts
98
+ are collected in `dist/vMAJOR.MINOR.PATCH` (`dist/dev` for development). Publishing uses the multi-package upload helper generated
99
+ by [pypitrust](https://github.com/twardoch/pypitrust). Register a trusted publisher
100
+ for **each** of `fontlab`, `fontgate`, `fontpr`, using repository
101
+ `Fontlab/fontlab-pypi`, workflow `pypi-upload.yml`, environment `pypi`.
102
+ For the first publication, PyPI may reject simultaneous pending publishers with
103
+ identical repository/workflow/environment tuples. Register `fontlab`, run
104
+ `./release.sh` to build all three, then upload only its wheel and sdist with
105
+ `scripts/pypi-upload.sh dist/vX.Y.Z/fontlab-*.whl dist/vX.Y.Z/fontlab-*.tar.gz`.
106
+ After that project exists, register and upload `fontgate`, then `fontpr` the same
107
+ way. Once all three projects exist, `./publish.sh` publishes them together.
108
+ The helper retains failed staging drafts for retry. No PyPI API token is required.
109
+
110
+ Actual desktop installation, host automation and PyPI publication are separate
111
+ checks; see [WORK.md](WORK.md) for the verified scope and [TODO.md](TODO.md)
112
+ for outstanding acceptance checks.
fontlab-1.0.0/PLAN.md ADDED
@@ -0,0 +1,33 @@
1
+ ---
2
+ this_file: PLAN.md
3
+ ---
4
+ # Package design
5
+
6
+ Three distributions share the repository's semver tags and hatch-vcs version.
7
+ `fontlab` provides external automation and the `fontlab-cli` entry point;
8
+ `fontgate` and `fontpr` raise an actionable ImportError outside FontLab.
9
+ The installed native `fontlab` binary is a different API: these wheels belong
10
+ in external Python environments, never in FontLab's embedded Python.
11
+
12
+ The installer reads the appropriate official Sparkle appcast, selects the newest
13
+ compatible full installer, downloads over HTTPS with a timeout and length/hash
14
+ checks, then installs. macOS uses hdiutil and ditto in a user destination; Windows uses Inno
15
+ Setup's unattended switches from an elevated terminal (the installer requires admin). Existing applications are preserved. Installation
16
+ is explicit through `install`, or automatic before launch/submit/remote calls.
17
+ Remopy owns MCP transport and result handling. Windows launch/script submission
18
+ use the installed executable because Remopy's native launch supports macOS only.
19
+
20
+ The implementation affects package exports, CLI arguments, installer tests,
21
+ standalone stub tests, three wheel/sdist configurations, build/publish scripts,
22
+ and documentation/examples. No pre-existing production code or callers exist.
23
+
24
+ Release design reuses pypitrust's `release.sh` and `uvx gitnextver` for automatic
25
+ semver bumping, commit/push and three-package builds. `publish.sh` then sends the
26
+ tagged artifacts through the existing multi-package OIDC upload helper. Initial
27
+ pending publishers are bootstrapped one project at a time.
28
+
29
+ Remaining work: independently review the release-helper addition; reconcile,
30
+ commit and push the reviewed tree; publish the first 1.0.0 package releases;
31
+ verify exact-SHA CI and clean PyPI installs. Windows elevated silent installation
32
+ and script execution, and native MCP on a build with a working bridge, remain
33
+ separate native checks.