A previous release had provenance metadata, but this release does not. View details.
Dated Census and CEPR scripts (0.2.41)
- Paper PDF builder, November 4: standalone Python/pdfLaTeX scripts, templates, fonts, and example workbook.
- Apps build scripts as of November 3: the 19 scripts from the downloaded CEPR CMO bundle.
Both folders ship in the installed package and can be copied into the relevant Census/CEPR code directory. The paper folder contains all its rendering assets; the apps folder retains the original external CEPR paths and dependencies.
Re-release exhibit packet
The paper workflow builds a 17-page PDF with
Figures 1–3, Tables 1–7, Figures A2–A4, and Tables A1–A4. Every result defaults
to the new workbook and table values appear in red; figures keep their blue
and orange colors. All input variable names are editable in build_latex.py.
Panel E is omitted. The bundled workbook is an explicitly labeled preview,
not new release results.
School characteristics (0.2.39)
The package includes the national school covariate master pooled over 2009–2023, the school-name/NCES crosswalk, and a Census-side example script for selecting distinct schools, calculating 25+ grade-span weights, and producing Table 1 Panel E means and SDs. See the Census instructions and data definitions and coverage. Enrollment and FRPL cover all 225 mapped schools; teacher measures have documented gaps and the expenditure definition remains unresolved.
The school-covariate utilities remain available separately. The current exhibit packet does not include Panel E or require its inputs.
College scatter plots (0.2.32)
from ltc_code.plot_colleges import plot_colleges provides an OI-themed
scatter with explicit Polars x/y aggregations, college grouping, optional
filters and categorical color groups. Plotting additionally requires
oi-tools, plotnine, and pyarrow in the analysis environment; they are
not required to run the NSC build. See NSC extensions
for attendance definitions, coarsening names, and plotting examples.
Paper exhibits (0.2.33)
The complete standalone LaTeX PDF workflow is bundled under
src/ltc_code/paper (installed as ltc_code/paper). It includes the
fixed disclosed and replaceable pending Excel workbooks, Python scripts,
LaTeX templates, and table/figure exclusion controls. See
paper instructions. Copy that whole directory
to a writable working location and run bash run_latex.sh. The paper
workflow uses its own pinned Python dependencies and requires LaTeX;
the existing package dependencies are unchanged.
Metadata
Release files for ltc-code 0.2.50
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Loss of provenance
These files do not have provenance metadata, despite files in a prior release including this data.
We recommend further investigation before installing these files. View details.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| ltc_code-0.2.50.tar.gz | 67.2 MB | Without provenance | Details for ltc_code-0.2.50.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| ltc_code-0.2.50-py3-none-any.whl | Python 3 | none | any | Details for ltc_code-0.2.50-py3-none-any.whl |
Total release size: 134.6 MB
Release files / ltc_code-0.2.50.tar.gz
Loss of provenance
This file belongs to a release without provenance metadata, despite a prior release including this data.
We recommend further investigation before installing this file. View details.
| Download URL | ltc_code-0.2.50.tar.gz |
|---|---|
| Size | 67.2 MB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
77cef69e8a61324113c1ac9b9e58b338c7756e654c118fe0166256d02bcb5de9
|
|
BLAKE2b-256 checksum How to use checksums |
da990fa871ef5267dd2bb064638eb472a969dea9856894bd6a5a13a0255fd096
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.11.28 {"installer":{"name":"uv","version":"0.11.28","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"macOS","version":null,"id":null,"libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":null}
|
Release files / ltc_code-0.2.50-py3-none-any.whl
Loss of provenance
This file belongs to a release without provenance metadata, despite a prior release including this data.
We recommend further investigation before installing this file. View details.
| Download URL | ltc_code-0.2.50-py3-none-any.whl |
|---|---|
| Size | 67.3 MB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
1c215db5b9d14cd2e36b5d7214186256f8dd98b38191fce267a1065248de199d
|
|
BLAKE2b-256 checksum How to use checksums |
e1c21d5bb41e11e610c53f81c63cd8aa155041792e37171b02c05dea7b75d7c6
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.11.28 {"installer":{"name":"uv","version":"0.11.28","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"macOS","version":null,"id":null,"libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":null}
|
Security for ltc-code 0.2.50
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
Loss of provenance
A previous release of these files had provenance metadata, but this release does not.
While this could reflect a routine change by the project maintainers, it may also indicate that the release files have been compromised.
Release comparison
- Removed 0.2.49 2 files With provenance
- Added 0.2.50 2 files Without provenance
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.