Bug 50590 – Client lib could not depend on univention software

Bug 50590 - Client lib could not depend on univention software


Summary:	Client lib could not depend on univention software

Status:	NEW

Product:	UCS
Classification:	Unclassified
Component:	UMC (Generic)
Version:	UCS 4.4
Hardware:	Other Linux

Importance:	P5 normal (vote)
Target Milestone:	---
Assigned To:	UMC maintainers
QA Contact:	UMC maintainers

URL:
Keywords:

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2019-12-04 10:47 CET by Dirk Wiesenthal
Modified:	2019-12-04 11:13 CET (History)
CC List:	1 user (show)

See Also:
What kind of report is it?:	Development Internal
What type of bug is this?:	---
Who will be affected by this bug?:	---
How will those affected feel about the bug?:	---
User Pain:
Enterprise Customer affected?:
School Customer affected?:
ISV affected?:
Waiting Support:
Flags outvoted (downgraded) after PO Review:
Ticket number:
Bug group (optional):
Max CVSS v3 score:

Attachments
Try to avoid using UCR (3.07 KB, patch) 2019-12-04 11:02 CET, Dirk Wiesenthal	Details \| Diff
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

Description Dirk Wiesenthal

2019-12-04 10:47:06 CET

Currently,

univention.lib.umc imports univention.config_registry. This is the only import besides the python standard lib. Maybe we can import it only if needed, not at the beginning?

The benefit would be that it could be used outside UCS.

See Bug#50589

Comment 1 Dirk Wiesenthal

2019-12-04 11:02:47 CET

Created attachment 10245 [details]
Try to avoid using UCR

This is what I came up with. It also adds some Python3 support. One could cache the UCR instance, but I found it unnecessary.