You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi, I am packaging Divio Django CMS packages for openSUSE, and I always want to run the tests in my builds to verify that the package is working, and breaks when dependencies become incompatible.
The tests in this repo are included in the sdist, which is great, but they can not be used.
setup.py includes
test_suite='tests.settings.run'
However tests/settings/ are not included in the sdist.
And lots of packages don't include or declare their tests, such as djangocms-icon.
Also, all setup.py use license='BSD'. It would be nice if they used "BSD-3-Clause", the https://spdx.org identifier for the specific license being used.
The text was updated successfully, but these errors were encountered:
No, that tell setuptools to include tests as part of the installed library, which is wrong. MANIFEST.in is the typical solution. There are alternatives, if using tools other than just setuptools. e.g. dephell automatically adds tests to the sdist.
Hi, I am packaging Divio Django CMS packages for openSUSE, and I always want to run the tests in my builds to verify that the package is working, and breaks when dependencies become incompatible.
The tests in this repo are included in the sdist, which is great, but they can not be used.
setup.py includes
However
tests/settings/
are not included in the sdist.The packaging is happening at https://build.opensuse.org/package/show/home:jayvdb:django/python-djangocms-bootstrap4
The collection of other Divio packages can be found at
https://build.opensuse.org/project/show/home:jayvdb:django
I encountered similar problems with
And lots of packages don't include or declare their tests, such as
djangocms-icon
.Also, all
setup.py
uselicense='BSD'
. It would be nice if they used "BSD-3-Clause", the https://spdx.org identifier for the specific license being used.The text was updated successfully, but these errors were encountered: