> > > So: > 1. Sources -- everything in git repo (docs, etc...) > 2. sdist -- everything needed to build the wheel > 3. pypi wheel -- the executable python artifact > > Exactly.
> Currently I was referring to (1) and (2) as the same. Re: documentation -- > in the table I didn't put it as part of the sources (tgz) that we vote on. > You implied it should be there -- thoughts? It might be simplest just to > package up the whole git repo, go file-by-file on licenses, etc... Package > it all, easy, not much fancy stuff. > Yes. We use `git archive` essentially to produce source tarballs. You can even explicitly exclude some of the things you **really** would like to exclude from it with .gitattributes https://stackoverflow.com/questions/38737765/how-do-i-exclude-files-from-git-archive - this is what we do in airflow https://github.com/apache/airflow/blob/main/.gitattributes . What we also do in airflow to reprocess the archive to be bit-to-bit reproducible https://github.com/apache/airflow/blob/3428dc98fc1958049f301ee6dea635d4833cd1e1/dev/breeze/src/airflow_breeze/utils/reproducible.py#L79 - but this is optional and just helps us to verify it quickly > Then the sdist is what we have now (minimal, stripped down), and the pypi > wheel is the built artifact. > Yep; > > And yes, agreed, the documentation after the table needs to be cleaned up > (too precise on individual files) -- that's a good pointer. > Cool.
