sdist and the pure (and universal) wheel is generated in a build job.
Tests download the wheel, install it and run the tests against the installed package.
Both the sdist and the wheel are built using https://github.com/pypa/build (in the pyavb PR, only the sdist is built using that tool).
Move the source code to use the src layout, for the same reasons provided in the pyavb PR. Which si making sure the code tested is the one installed from the wheel and prevent accidents.
The produced wheel is now universal (which means it's platform agnostic and compatible with both python 2 and 3). So we will only have a single wheel.
python_requires is correctly set.
The wheel will now be published to PyPI. This will shave some build minutes in OTIO :) (since when a wheel is not available, installers have to download the sdist, build the wheel from the sdist and install the wheel).
And that should be the last package (of yours) that I'll do packaging and CI improvements like these :)
Hello, it's me again with packaging and CI improvements. This PR is similar to https://github.com/markreidvfx/pyavb/pull/12, but it's a lot simpler.
buildjob.And that should be the last package (of yours) that I'll do packaging and CI improvements like these :)
Let me know if you have any questions!