Building & publishing artifacts
P35.build-publish.02 · Audience: guest, it-ml, language-pro · Prerequisites: Dependencies, lockfiles & environments
pip install wordcount downloads a wheel and unzips it. That wheel isn't
magic — it's a ZIP with a fixed layout you can open and read. This module has you
inspect one, so "what does my package actually ship?" is a question you can
answer, not guess.
ⓘ Concept: Two artifacts, one built, one to build from
.whl) is already built — pip just unpacks it into place. An sdist is a source tarball a machine builds from. Pure-Python code ships one py3-none-any wheel that runs anywhere; compiled code ships many, one per interpreter and platform. You publish both so every consumer is covered.Why it matters — A wheel installs with no build step; an sdist is the source fallback. Knowing which is which is how you reason about install speed and compatibility.
Ask the mentor about this module
Ask a question about this content. The mentor explains and grounds its answer in what you are studying; asking is recorded as a learning signal, not a grade.
Keeping your files on this device
Off by default. The mentor always gets your file; this only decides whether your own copy stays here. Copies live in this browser only - they do not follow you to another device, and clearing site data removes them.
🎓 Practice ladder
2 graded rungs · ~23 minInspect a wheel's metadata and manifest from its bytes, then reason about building and publishing in an interview-style prompt.
Rung 1 — inspect a wheel
Loading exercise…
Rung 2 — building & publishing (interview)
Loading exercise…
You can build and read an artifact. The last track ties the loop together — automating the checks so quality doesn't depend on anyone remembering.
My notes on this module
Loading your notes...