Package pki client library for Python 3

[pki-bot]

This issue was migrated from Pagure Issue #1739. Originally filed by cheimes (@tiran) on 2016-01-22 15:01:33:

• Closed as Fixed
• Assigned to cheimes (@tiran)

---

Dogtag's Python code is compatible with Python 3 for a while now. So far the code hcryptomilk't been packaged for Python 3 yet. FreeIPA is making progress in its Python 3 porting effort and will soon need the pki client libraries for its dogtag plugin.

My patch 48 adds a new package python3-pki. Neither pki-base and pki-server nor any of the command line tools are modified. pkispawn, pkidestroy etc. still use Python 2 to reduce any risk. After all the Python 3 port hcryptomilk't been tested thoroughly yet.

[pki-bot]

Comment from mharmsen (@mharmsen) at 2016-01-27 01:20:07

Internal change

[pki-bot]

Comment from mharmsen (@mharmsen) at 2016-02-16 03:01:02

If this ticket is completed in the 10.3 time frame, 'python3-pki' should be called 'pki-python3' to be consistent with all other 'pki' packages.

Additionally, if PKI TRAC Ticket 1399 Split pki-base into Java and Python client packages is completed in the 10.3 time frame, additional changes should potentially be considered to split client functionality (pki-python3-client) from server functionality (pki-python3-server).

[pki-bot]

Comment from cheimes (@tiran) at 2016-02-16 12:47:59

The new Python 3 package contains only the client libraries for Python 3. In my opinion it makes more sense to either name it pki-python3-client from the start or keep the name pki-python3 after 1399.

pki-python3 feels more natural because the name also reflects the Python name spaces. All client libraries are in the pk namespace. The server and installers are in pki.server. On the other hand pki-python3-client is more descriptive.

Names are tough!

[pki-bot]

Comment from cheimes (@tiran) at 2016-03-04 20:17:32

Pushed to master in 4dc934a

[pki-bot]

Comment from cheimes (@tiran) at 2017-02-27 14:05:42

Metadata Update from @tiran:

• Issue assigned to tiran
• Issue set to the milestone: 10.3.0.a1