-
Notifications
You must be signed in to change notification settings - Fork 96
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Separate test code from lib389 #3082
Comments
Comment from vashirov (@vashirov) at 2018-11-12 17:57:57 Metadata Update from @vashirov:
|
Comment from mreynolds (@mreynolds389) at 2018-11-15 17:52:37 Metadata Update from @mreynolds389:
|
Comment from vashirov (@vashirov) at 2018-12-12 17:09:22 Metadata Update from @vashirov:
|
Comment from mreynolds (@mreynolds389) at 2020-02-12 16:45:47 Metadata Update from @mreynolds389:
|
Bug Description: `topologies` module is used only in tests. But because it's part of lib389, it pulls in pytest and its dependencies. Additionally, lib389 contains tests that are installed, but not needed for lib389 to function. `perftools` module is also used only for tests and depends on `topologies`. Fix Description: `topologies` and `perftools` modules have been converted into Python packages. Fixes: 389ds#3082 Reviewed by: Signed-off-by: Stanislav Levin <[email protected]>
As said in issue #5924, IMHO while removing lib389 dependency over pytest we should also redesign the topology framework: |
Cloned from Pagure issue: https://pagure.io/389-ds-base/issue/50023
Issue Description
topologies
module is used only in tests. But because it's part of lib389, it pulls in pytest and its dependencies. Additionally, lib389 contains tests that are installed, but not needed for lib389 to function:The text was updated successfully, but these errors were encountered: