This slack thread has nice screenshots explaining what this PR does. Please read the whole thread and contemplate the screenshots as well as the code changes.
This PR defines how every part of this repo will be published for production use, so it affects all parts of the project: testing, frontend, backend, infrastructure, etc. It'll be really helpful if any contributors that can understand this strategy do--because it impacts how all of our work is released/shipped and therefore how we write our code.
Please ask questions!
If you understand the ideas in this thread and the code that makes it happen (setup.py, setup.cfg, MANIFEST.in) ... you probably understand python packaging better than 90% of python developers 😆.
This slack thread has nice screenshots explaining what this PR does. Please read the whole thread and contemplate the screenshots as well as the code changes.
https://rootskiio.slack.com/archives/C03847X2PRP/p1670831392141859
This PR defines how every part of this repo will be published for production use, so it affects all parts of the project: testing, frontend, backend, infrastructure, etc. It'll be really helpful if any contributors that can understand this strategy do--because it impacts how all of our work is released/shipped and therefore how we write our code.
Please ask questions!
If you understand the ideas in this thread and the code that makes it happen (
setup.py,setup.cfg,MANIFEST.in) ... you probably understand python packaging better than 90% of python developers 😆.