Packaging/bootstrap hygiene for the first release (PyPI 0.0.1 stub; bootstrap leftover)

[matthewholman]

Two release-hygiene items:

1. Stale PyPI stub. The layup name on PyPI is a 0.0.1 placeholder: an empty __init__.py, no __version__, no CLI, no extension. Anyone who tries pip install layup first gets a broken package. Yank/replace it as part of the first real release.
2. Bootstrap leftover. layup bootstrap leaves the intermediate debias_hires2018.tgz (~156 MB) in the cache after extraction — delete it post-untar.

Found during a clean-room, fresh-user install + test run-through (fresh venv + --recursive clone, following the README Quickstart), 2026-07-10.

[mschwamb]

Github can be set up to automatically push to pypi - that hasn't been set up. That should be set up to make it easier to push new versions. I'd recommend that this be set up.

[matthewholman]

Thanks, Meg. I'll look into this when I have a chance.

…

On Mon, Jul 13, 2026 at 7:37 AM Meg Schwamb ***@***.***> wrote: *mschwamb* left a comment (Smithsonian/layup#436) <#436 (comment)> Github can be set up to automatically push to pypi - that hasn't been set up. That should be set up to make it easier to push new versions. I'd recommend that this be set up. — Reply to this email directly, view it on GitHub <#436?email_source=notifications&email_token=AA5CVWMDPKH7EE5OQOSEV6L5ETCZFA5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTIOJVG42TENBWG43KM4TFMFZW63VGMF2XI2DPOKSWK5TFNZ2KYZTPN52GK4S7MNWGSY3L#issuecomment-4957524676>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AA5CVWKAXCESLSX4DWKJLKL5ETCZFAVCNFSNUABFKJSXA33TNF2G64TZHM4TCNRSHAYTGMRUHNEXG43VMU5TIOBVHA2DKMBXGE32C5QC> . Triage notifications, keep track of coding agent tasks and review pull requests on the go with GitHub Mobile for iOS <https://github.com/notifications/mobile/ios/AA5CVWLWT7UN4HEQFVRRG6L5ETCZFA5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTIOJVG42TENBWG43KM4TFMFZW63VGMF2XI2DPOKSWK5TFNZ2KUZTPN52GK4S7NFXXG> and Android <https://github.com/notifications/mobile/android/AA5CVWLQQD6UMZPHJKUVO335ETCZFA5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTIOJVG42TENBWG43KM4TFMFZW63VGMF2XI2DPOKSWK5TFNZ2K4ZTPN52GK4S7MFXGI4TPNFSA>. Download it today! You are receiving this because you authored the thread.Message ID: ***@***.***>

-- Matthew J. Holman, PhD Senior Astrophysicist Center for Astrophysics | Harvard & Smithsonian 60 Garden Street, MS #51 Cambridge, MA 02138 (617) 496-7775

[mschwamb]

I checked pypi and the github repo - we're setup for automatic publishing to pypi when a new version is tagged in github

[mschwamb]

The workflow has already been setup and confirmed with the lincc frameworks project builder template

[matthewholman]

Status check on this issue, because its two items close by different routes and neither is automatic.

Item 2 — bootstrap leftover: fixed, in review

PR #472 removes debias_hires2018.tgz after the untar. Open, CI green, with @kjnapier and @Little-Ryugu. It deliberately does not declare Closes on this issue, because it only addresses half of it.

Item 1 — the stale PyPI 0.0.1 stub: not fixable by a pull request

The issue says to yank or replace it "as part of the first real release", and that is exactly right — the placeholder is displaced when layup is actually published to PyPI, which no code change can do on its own.

⚠️ One correction to the record, so nobody plans around it

@mschwamb noted on 24 July that automatic publishing is configured, and confirmed publish-to-pypi.yml against the LINCC Frameworks template. That is accurate about the workflow existing — but publishing would still fail today, for three reasons found afterwards and filed as #471:

1. The workflow checks out without submodules. CMakeLists.txt references include/eigen and include/autodiff, so python -m build fails outright with fatal error: 'Eigen/Dense' file not found.
2. A direct-URL dependency on sorcha, which PyPI rejects in Requires-Dist.
3. A linux_x86_64 wheel tag, which PyPI will not accept — it wants manylinux.

PR #475 fixes all three, verified by building an sdist and installing it into a clean environment rather than by reading configuration. So the sequence is: #475 merges → publishing is actually possible → the first release displaces the stub.

How this issue closes

Both of these have to be true, and neither will close the issue by itself:

• Remove the extracted archive after bootstrap untars it (#436) #472 merged — bootstrap leftover removed
• the first real release published to PyPI — stub displaced (needs Make PyPI publishing possible: submodules, sorcha dependency, and sdist-only build (#471) #475 first)

Flagging it because no open pull request declares an auto-closing reference to this issue, deliberately. Whoever cuts the release should come back and close this by hand.

One related note for that moment: the documentation landing page in PR #478 currently warns readers not to run pip install layup, because today that command succeeds and installs the empty 0.0.1 package with no error. That warning becomes wrong as soon as a real version ships, so the install section and the release need to move together, in that order.