Skip to content

docs: surface the ifclite-geom Python wheel in README + docs site#1326

Merged
louistrue merged 1 commit into
mainfrom
docs/python-reach
Jun 23, 2026
Merged

docs: surface the ifclite-geom Python wheel in README + docs site#1326
louistrue merged 1 commit into
mainfrom
docs/python-reach

Conversation

@louistrue

Copy link
Copy Markdown
Collaborator

Why

The native Python wheel (ifclite-geom) had no entry point from the project's main discovery surfaces: the root README and the hosted docs site only mention the npm packages and Rust crates. Anyone who finds the wheel on PyPI (or hears about it) has nowhere on the site to land. This is the "reach" follow-up to #1325 (the package-level README + examples + stub).

What

  • docs/api/python.md — a Python API Reference page (install, both functions, output schema, notes, links to examples + source), wired into the mkdocs nav under API Reference alongside TypeScript / Rust / WASM.
  • Root README, "Choose your setup" — a Python (native wheel) row.
  • Root README, "Documentation" API row — a Python link.

All links point at the hosted page https://ltplus-ag.github.io/ifc-lite/api/python/, matching the existing API entries.

Notes

Related

Pairs with #1325. Together they give a pip user a documentation URL to land on (the original request that prompted this).

The native Python wheel (ifclite-geom) had no entry point from the
project's main docs surfaces. Add:

- docs/api/python.md: a Python API Reference page (install, both
  functions, output schema, notes) wired into the mkdocs nav under
  API Reference.
- README "Choose your setup": a Python (native wheel) row.
- README "Documentation" API row: a Python link.

Links target the hosted docs page (ltplus-ag.github.io/ifc-lite/api/python/),
matching the existing TypeScript / Rust / WASM entries.
@vercel

vercel Bot commented Jun 23, 2026

Copy link
Copy Markdown
Contributor

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
ifc-lite Ready Ready Preview, Comment Jun 23, 2026 10:32am
2 Skipped Deployments
Project Deployment Actions Updated (UTC)
ifc-lite-dev Ignored Ignored Jun 23, 2026 10:32am
ifc-lite-viewer-embed Ignored Ignored Jun 23, 2026 10:32am

@coderabbitai

coderabbitai Bot commented Jun 23, 2026

Copy link
Copy Markdown

Warning

Review limit reached

@louistrue, we couldn't start this review because you've reached your PR review rate limit.

More reviews will be available in 10 minutes and 13 seconds. Learn how PR review limits work.

Your organization has used up its prepaid credits, and credit purchases are no longer available. Enable the review add-on in the billing tab to keep reviews running — you're only billed for reviews past your plan's rate limits ($0.25/file).

⌛ How to resolve this issue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based credits.

🚦 How do rate limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan refill rate.

For paid Pro and Pro+ PR reviews, CodeRabbit uses rolling per-developer review limits. Reviews become available again as older review attempts age out of the rolling limit window.

Please see our Fair Usage Limits Policy for further information.

ℹ️ Review info
⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: faa96eb1-dac6-476f-9e1f-44061f61eccb

📥 Commits

Reviewing files that changed from the base of the PR and between 95eceff and 85f10cf.

📒 Files selected for processing (3)
  • README.md
  • docs/api/python.md
  • mkdocs.yml
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch docs/python-reach

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 85f10cf19f

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

Comment thread docs/api/python.md
for step_id, el in data["elements"].items():
verts = np.frombuffer(el["vertices"], dtype=np.float64).reshape(-1, 3)
faces = np.frombuffer(el["faces"], dtype=np.uint32 ).reshape(-1, 3)
print(step_id, el["ifc_type"], el["global_id"], verts.shape, faces.shape)

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Badge Do not read missing global_id from buffers

In the buffer path shown here, geometry_data_buffers() builds each element dict with only ifc_type, color, vertices, and faces in rust/python/src/lib.rs, and never inserts global_id or name. For any model, copy-pasting this quick start raises KeyError: 'global_id' before it can print the mesh shapes; either switch the example to the JSON API for metadata or add these fields to the buffer binding/docs.

Useful? React with 👍 / 👎.

@louistrue

Copy link
Copy Markdown
Collaborator Author

Re the Codex note on global_id/name in the buffer path: that field is added to geometry_data_buffers in #1325 (rust/python/src/lib.rs). #1325 will merge first, so this example is accurate against main once it lands. The two PRs touch disjoint files (no overlap).

@louistrue louistrue merged commit 46df2e7 into main Jun 23, 2026
14 checks passed
@louistrue louistrue deleted the docs/python-reach branch June 23, 2026 10:47
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant