Use built release for CI tests about django-components HOT 3 CLOSED

Hey!

While I agree there's a need to test .whl, I'm not sure using a build.django_component package is the way to go, as it's far from any packaging standard.

I believe tox can already use a wheel for its tests (it's currently using sdist):

[testenv]
package = wheel
wheel_build_env = .pkg

The issue here is that even if the wheel is installed in tox venvs, it is shadowed by the source code, as the package is a the top level.

After checking the pytest docs around import modes and their recommended best practices, the best solution would be to use the src layout. This way, no more issues of the installed package being shadowed by the source files, and no need for a custom solution.

To go further for wheel testing, check-wheel-contents can be used.
It's included in this handy Github Action: https://github.com/hynek/build-and-inspect-python-package

Running it locally, we see that there is already an error in the wheels, that ship a tests.components module.

from django-components.

@EmilStenstrom, sorry for delay (tax submission week). @GabDug's suggestion is great, and @GabDug's thanks for taking this over 🚀

from django-components.

@JuroOravec You OK with @GabDug's suggestion here? Looks good to me.

from django-components.