importtime-check 0.1.0a1__tar.gz

importtime_check-0.1.0a1/.gitignore

@@ -0,0 +1,36 @@
+# Project working files
+.tmp/
+
+# Byte-compiled and optimized Python
+__pycache__/
+*.py[cod]
+*$py.class
+
+# Virtual environments
+.venv/
+venv/
+env/
+ENV/
+
+# Test, type-checking, lint, and coverage caches
+.pytest_cache/
+.mypy_cache/
+.ruff_cache/
+.coverage
+.coverage.*
+coverage.xml
+htmlcov/
+
+# Packaging and build output
+build/
+dist/
+*.egg-info/
+.eggs/
+pip-wheel-metadata/
+*.whl
+
+# Local editor and operating-system files
+.idea/
+.vscode/
+.DS_Store
+Thumbs.db

importtime_check-0.1.0a1/CONTRIBUTING.md

@@ -0,0 +1,128 @@
+# Contributing to importtime-check
+
+Thank you for helping improve `importtime-check`. Every change starts with an
+issue created from an approved Issue Form. Blank issues and pull requests
+without an open, same-repository issue are not accepted.
+
+## Issues and planning
+
+Choose the Bug report, Feature proposal, Design proposal, Maintenance task, or
+Release checklist that best matches the work. The forms ask for the information
+needed for that kind of contribution without forcing unrelated questions.
+Reports containing secrets or suspected vulnerabilities must use the private
+process in [SECURITY.md](SECURITY.md), never a public issue.
+
+Maintainers assign implementation issues to a release milestone before a pull
+request is opened. Milestones own release progress; labels classify the kind
+of change. A project board may be introduced when concurrent work makes a
+second planning view useful, but it is not another source of release truth.
+
+Blank issues are disabled. Maintainers use review and normal triage to request
+missing context; submissions are not automatically closed because prose or
+headings differ.
+
+## Development environment
+
+Use Python 3.11 or newer and pip 25.1 or newer. From the repository root:
+
+```console
+python -m venv .venv
+python -m pip install --upgrade "pip>=25.1"
+python -m pip install --group dev --editable .
+```
+
+Activate the virtual environment using the command appropriate for your shell,
+or invoke its Python executable directly.
+
+## Required checks
+
+Run the complete local gate before requesting review:
+
+```console
+python -m ruff format --check .
+python -m ruff check .
+python -m mypy src tests tools
+python -m pytest
+```
+
+CI additionally checks each pull-request commit for a matching DCO sign-off,
+reviews changed dependencies, and scans Python source with CodeQL. These
+remote checks are included in the aggregate required `CI` result.
+
+When packaging or artifact behavior changes, also run:
+
+```console
+python -m build --outdir .tmp/dist
+python -m twine check .tmp/dist/*
+python -m tools.validate_artifacts .tmp/dist
+python -m tools.smoke_wheel .tmp/dist
+```
+
+The artifact directory must be fresh. The smoke check installs the exact wheel
+offline with no dependencies and imports it outside the source path.
+
+## Changes and tests
+
+- Keep pull requests focused on one issue, but include the production code,
+  tests, documentation, and migration details needed to make that issue whole.
+- Add deterministic tests for success, boundary, and failure behavior. Unit
+  tests must not require network access, production credentials, wall-clock
+  sleeps, execution order, or mutable global machine state.
+- Preserve the zero-runtime-dependency core unless an accepted design change
+  explicitly says otherwise.
+- Maintain compatibility with every Python version claimed in project metadata
+  and enforced by CI.
+- Do not weaken strict typing, linting, coverage, or artifact checks merely to
+  make a change pass.
+
+## Commits and pull requests
+
+Every commit must include a Developer Certificate of Origin sign-off. Create it
+with `git commit --signoff`; the resulting commit message contains a
+`Signed-off-by` line. By signing off, you certify the
+[Developer Certificate of Origin](https://developercertificate.org/).
+
+Pull request titles use this conventional shape:
+
+```text
+type(optional-scope): imperative summary
+```
+
+Allowed types are `build`, `chore`, `ci`, `docs`, `feat`, `fix`, `perf`,
+`refactor`, and `test`. Keep the complete title at 80 characters or fewer.
+
+Every pull request follows the tracked Apache-inspired template and contains a
+closing reference such as `Closes #123` to one open, milestone-assigned issue.
+Its eight sections explain the proposal, motivation, issue, user impact,
+validation, compatibility and rollback, documentation and follow-up, and a
+short practical checklist. Maintainers request corrections during review when
+context is missing; custom code does not police contributor prose.
+
+A design proposal and accepted design record precede changes to public APIs,
+serialized formats, compatibility promises, architecture, dependencies,
+security-sensitive behavior, release policy, or contributor governance.
+Repository rules require a pull request and aggregate `CI` before `main` can
+accept a merge.
+
+## Release notes and changelog
+
+Not every internal change is useful release news. Describe user-facing behavior
+and migration impact in the pull request, or write `None` when it is not
+applicable. Maintainers apply a generated-release-note category label to
+user-visible work and `skip-release-notes` to internal-only changes.
+
+The first alpha has curated notes in `docs/releases/`; the generated release
+note configuration can group later merged pull requests by labels. The
+project does not require every pull request to edit one shared `CHANGELOG.md`;
+that produces noise and merge conflicts for non-user-facing work. A curated
+changelog or per-pull-request news fragments may be added through a dedicated
+issue when release volume, backports, or multiple concurrent contributors make
+them valuable.
+
+## Security
+
+Do not report suspected vulnerabilities in a public issue. Follow
+[SECURITY.md](SECURITY.md) for private reporting instructions.
+
+This project is independent and is not affiliated with or endorsed by the
+Apache Software Foundation.

importtime_check-0.1.0a1/LICENSE

@@ -0,0 +1,201 @@
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "[]"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright [yyyy] [name of copyright owner]
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.

importtime_check-0.1.0a1/NOTICE

@@ -0,0 +1,4 @@
+importtime-check
+Copyright 2026 importtime-check contributors
+
+This product is licensed under the Apache License, Version 2.0.

importtime_check-0.1.0a1/PKG-INFO

@@ -0,0 +1,214 @@
+Metadata-Version: 2.5
+Name: importtime-check
+Version: 0.1.0a1
+Summary: Detect Python import-time regressions in CI.
+Project-URL: Repository, https://github.com/SEPURI-SAI-KRISHNA/importtime-check
+Project-URL: Issues, https://github.com/SEPURI-SAI-KRISHNA/importtime-check/issues
+License-Expression: Apache-2.0
+License-File: LICENSE
+License-File: NOTICE
+Keywords: ci,import-time,performance,pytest,regression-testing,startup-time
+Classifier: Development Status :: 3 - Alpha
+Classifier: Intended Audience :: Developers
+Classifier: Operating System :: OS Independent
+Classifier: Programming Language :: Python :: 3
+Classifier: Programming Language :: Python :: 3 :: Only
+Classifier: Programming Language :: Python :: 3.11
+Classifier: Programming Language :: Python :: 3.12
+Classifier: Programming Language :: Python :: 3.13
+Classifier: Programming Language :: Python :: 3.14
+Classifier: Topic :: Software Development :: Build Tools
+Classifier: Topic :: System :: Benchmark
+Classifier: Typing :: Typed
+Requires-Python: >=3.11
+Provides-Extra: pytest
+Requires-Dist: pytest>=9.1.1; extra == 'pytest'
+Description-Content-Type: text/markdown
+
+# importtime-check
+
+[![CI](https://github.com/SEPURI-SAI-KRISHNA/importtime-check/actions/workflows/ci.yml/badge.svg)](https://github.com/SEPURI-SAI-KRISHNA/importtime-check/actions/workflows/ci.yml)
+
+`importtime-check` is a CI gate for detecting regressions in Python import
+time. It measures imports in clean subprocesses, compares results with
+deterministic baselines, and reports actionable diagnostics when startup
+performance regresses.
+
+## Project status
+
+This project is in early alpha development; its public API is not yet a stable
+compatibility commitment.
+
+Version `0.1.0a1` is the first public alpha. Install it with:
+
+```console
+python -m pip install --pre importtime-check==0.1.0a1
+```
+
+CPython 3.11 through 3.14 are tested. Package metadata requires Python 3.11
+or newer; newer interpreter versions are not yet in the tested support matrix.
+The core install has no runtime dependencies. Pytest is available only through
+the optional `pytest` extra.
+
+The numeric stderr produced by CPython's `-X importtime` option can already be
+parsed without executing a subprocess:
+
+```python
+from importtime_check import parse_importtime
+
+result = parse_importtime(
+    "import time: self [us] | cumulative | imported package\n"
+    "import time:        12 |         34 | example"
+)
+event = result.events[0]
+assert (event.module, event.self_us, event.cumulative_us, event.depth) == (
+    "example",
+    12,
+    34,
+    0,
+)
+```
+
+This API remains an alpha API and may change before the first stable release.
+
+To measure one installed module in a fresh CPython process:
+
+```python
+from importtime_check import measure_import
+
+measurement = measure_import("json")
+print(measurement.target_event.cumulative_us)  # integer microseconds
+```
+
+The target must be installed in the selected interpreter. The child uses
+Python's isolated mode, so the current directory and user site packages are
+not import locations. This reports CPython's target import time, not total
+process startup time. For a less noisy observation, use repeated sampling:
+
+```python
+from importtime_check import sample_import
+
+result = sample_import("json", warmups=1, samples=5)
+print(result.median_cumulative_us)  # upper median, integer microseconds
+print([run.target_event.cumulative_us for run in result.samples])
+```
+
+Each warmup and sample uses a fresh child process. Warmups are preserved but
+excluded from the median. This reduces single-run noise; it does not guarantee
+that two machines or CI runs have comparable timings.
+
+The library also supports reviewable baselines and exact regression decisions:
+
+```python
+from importtime_check import (
+    check_baseline,
+    probe_environment,
+    record_baseline,
+    sample_import,
+    save_baseline,
+)
+
+baseline = record_baseline(
+    {"json": sample_import("json")},
+    probe_environment(),
+    max_increase_us=25,
+    max_increase_percent="10",
+)
+save_baseline("importtime-baseline.json", baseline)
+report = check_baseline(baseline)
+print(report.status)  # "pass" or "regression"
+```
+
+Baselines are versioned JSON and require the same Python minor version,
+platform, machine, and profile at check time. Review baseline changes before
+using them as CI policy; matching identity does not eliminate host noise.
+
+The installed command supports measuring, recording, inspecting, and checking:
+
+```console
+importtime-check measure --module json
+importtime-check baseline record --output importtime-baseline.json --module json --max-increase-us 25 --max-increase-percent 10
+importtime-check baseline show --file importtime-baseline.json
+importtime-check check --baseline importtime-baseline.json
+importtime-check check --baseline importtime-baseline.json --format json
+```
+
+`check` exits `0` when all targets pass, `1` for a regression, and `2` for
+invalid input or an operational failure. Its JSON output is a stable schema-1
+document on standard output, including for exit codes `1` and `2` (except
+command-line syntax errors).
+
+Pytest integration is optional and must be explicitly loaded. For a development
+checkout, install its extra and run against an approved baseline. After
+publication, install `"importtime-check[pytest]==0.1.0a1"` instead of the
+editable checkout:
+
+```console
+python -m pip install --editable ".[pytest]"
+python -m pytest -p importtime_check.pytest_plugin --importtime-baseline importtime-baseline.json
+```
+
+The plugin accepts repeated `--importtime-module` flags to assert the exact
+target set and `--importtime-python`, `--importtime-timeout-seconds`,
+`--importtime-working-directory`, and `--importtime-profile` to select the
+runtime. The corresponding `pytest.ini` settings are `importtime_baseline`,
+`importtime_modules`, `importtime_python`, `importtime_timeout_seconds`,
+`importtime_working_directory`, and `importtime_profile`. Explicit command-line
+values replace settings; otherwise the baseline supplies targets and sampling.
+Invalid configuration exits pytest with code `4` before tests. After a passing
+test session, a regression or measurement error exits with code `1`; an
+existing test failure or interruption is preserved without measuring. The
+plugin never refreshes baselines and is not loaded automatically.
+
+## Development
+
+Create a virtual environment with Python 3.11 or newer, then install the
+project and its unpublished development dependency group. Dependency-group
+installation requires pip 25.1 or newer.
+
+```console
+python -m venv .venv
+python -m pip install --upgrade "pip>=25.1"
+python -m pip install --group dev --editable .
+```
+
+Run the local quality gate from the repository root:
+
+```console
+python -m ruff format --check .
+python -m ruff check .
+python -m mypy src tests tools
+python -m pytest
+```
+
+Build validation uses fresh artifacts in the ignored `.tmp` directory:
+
+```console
+python -m build --outdir .tmp/dist
+python -m twine check .tmp/dist/*
+python -m tools.validate_artifacts .tmp/dist
+python -m tools.smoke_wheel .tmp/dist
+```
+
+See [CONTRIBUTING.md](https://github.com/SEPURI-SAI-KRISHNA/importtime-check/blob/main/CONTRIBUTING.md)
+for the complete contribution workflow and
+[SECURITY.md](https://github.com/SEPURI-SAI-KRISHNA/importtime-check/blob/main/SECURITY.md)
+for private vulnerability reporting.
+The [first alpha release notes](https://github.com/SEPURI-SAI-KRISHNA/importtime-check/blob/main/docs/releases/v0.1.0a1.md) summarize its
+capabilities, compatibility, and limitations.
+
+## Current limits
+
+Measurements are sensitive to host load, dependency changes, and interpreter
+configuration. Compare results only in controlled environments with reviewed
+baselines. The tool reports CPython's import-time diagnostics, not whole-process
+startup time, and it does not yet identify the cause of a regression automatically.
+
+## License
+
+Licensed under the Apache License, Version 2.0. See
+[LICENSE](https://github.com/SEPURI-SAI-KRISHNA/importtime-check/blob/main/LICENSE)
+and [NOTICE](https://github.com/SEPURI-SAI-KRISHNA/importtime-check/blob/main/NOTICE).
+
+This is an independent open-source project. It is not affiliated with or
+endorsed by the Apache Software Foundation.