Create a package for SSSD python code

[sssd-bot]

Cloned from Pagure issue: https://pagure.io/SSSD/sssd/issue/759

• Created at 2011-01-04 14:17:49 by jzeleny
• Closed as Invalid
• Assigned to sgallagh

---

Currently some (maybe all) python files of SSSD are directly in site-packages directory. This approach is wrong for two reasons:

1. it brings more mess to the site-packages directory
2. Under some unusual circumstances it could cause unpleasant issues

An example of the issue I was referring to in second point: I just spent couple hours tracking an error in FreeIPA which was caused by import error of a module ipachangeconf (it has the same name in IPA and SSSD). I found out, that the underline cause of this error was that I deleted all files/dirs in site-packages beginning with ipa*. If the file ipachangeconf.py (which really belongs to SSSD and not IPA) was in sssd subdirectory, the confusion and subsequent error would be avoided.

Comments

---

Comment from sgallagh at 2011-01-04 15:05:12

Fields changed

component: SSSD => Build Environment
milestone: NEEDS_TRIAGE => SSSD 1.5.1
owner: somebody => sgallagh

---

Comment from sgallagh at 2011-01-17 17:10:27

Reducing the priority on this. We'll get to it if we get to it, but it's purely cosmetic.

priority: major => trivial
upgrade: => 0

---

Comment from sgallagh at 2011-01-24 22:04:09

Fields changed

status: new => assigned

---

Comment from sgallagh at 2011-01-25 14:19:44

Moving this out to 1.6.0. Changing the import location of these python files is too big of a change for a point release.

milestone: SSSD 1.5.1 => SSSD 1.6.0
status: assigned => new

---

Comment from dpal at 2011-02-07 15:52:45

Decided we are not going to change the location of the python code.

resolution: => wontfix
status: new => closed

---

Comment from jzeleny at 2017-02-24 14:47:26

Metadata Update from @jzeleny:

• Issue assigned to sgallagh
• Issue set to the milestone: SSSD 1.6.0

---

Comment from jhrozek at 2017-04-07 13:15:59

Metadata Update from @jhrozek:

• Custom field rhbz adjusted to 0

---

Comment from jhrozek at 2017-04-07 13:15:59

Metadata Update from @jhrozek:

• Custom field rhbz adjusted to 0