Jeremiah Paige

I did want to bring up the idea of when to package tests. The current python-package-structure recommends a top-level tests/ alongside the top-level src/ and then mentions how this will...

> Another point is that I disagree with the no- tests policy on wheels. For pure Python packages? Sure. For wheels that ship compiled code? Please send me your tests...

The changes that I would propose right now: - specify that any resources necessary to build a wheel need to be included in the sdist - this means the pyproject.toml...

> this is explicitly required by the [sdist spec](https://packaging.python.org/en/latest/specifications/source-distribution-format/#source-distribution-file-format) Good to know! I didn't realize this preference made it into any formal specification. It should still be noted though that...

I believe I've taken us somewhat off-topic. We are not building a backend here that has to make some of these decisions, only making recommendations of current tools. I guess...

As an attempt to put a pin in this here is my updated proposal: * clarify in `The src/ layout and testing` and/or `Sometimes tests are needed in a distribution`...

I also wonder looking back at the page if the hierarchy could be reconsidered Currently: - Python Package Structure for Scientific Python Projects - The src/ layout and testing -...

What I'm getting from the earlier thread is that we **do** want to put forward Python's official [EOL timeline](https://devguide.python.org/versions/) (recommend supporting the latest stable version, and no further back than...

I believe you read that diagram exactly right Leah. Hmm, I don't think this rises to the level of new page (maybe we'll see when it's written). I think it...

I think this is the best summary of PyOS recommendations