IIRC we started doing that so that consumers building their own packages can run the tests for the packages easily. I don't know how many people are doing that, and apparently at least some downstream consumers aren't packaging everything anyway so they couldn't run those tests.
Excerpts from Andrey Kurilin's message of 2018-02-19 17:39:11 +0200: > Can someone explain me the reason for including "tests" module into > packages? > > 2018-02-19 17:00 GMT+02:00 Michael Bayer <mba...@redhat.com>: > > > Hi list - > > > > Apparently Cinder was misled by my deprecations within the > > oslo_db.sqlalchemy.test_base package of DbFixture and DbTestCase, and > > in https://review.openstack.org/#/c/522290/ the assumption was made > > that these should be imported from oslo_db.tests.sqlalchemy. This > > is an immense mistake on my part that I did not expect people to go > > looking for the same names elsewhere in private packages and now we > > have a serious downstream issue as these modules are not packaged, as > > well as the possibility that the oslo_db.tests. package is now locked > > in time and I have to add deprecations there also. > > > > If anyone knows of projects (or feels like helping me search) that are > > importing *anything* from oslo_db.tests these must be reverted ASAP. > > > > __________________________________________________________________________ > > OpenStack Development Mailing List (not for usage questions) > > Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe > > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > > > __________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev