Dogtag's Python code is compatible with Python 3 for a while now. So far the code hasn'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 hasn't been tested thoroughly yet.
Internal change
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).
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-client
pki-python3
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.
pk
pki.server
Names are tough!
Pushed to master in 4dc934a5f3fbeea7e877aaadcb13a6eabb635463
Metadata Update from @cheimes: - Issue assigned to cheimes - Issue set to the milestone: 10.3.0.a1
Dogtag PKI is moving from Pagure issues to GitHub issues. This means that existing or new issues will be reported and tracked through Dogtag PKI's GitHub Issue tracker.
This issue has been cloned to GitHub and is available here: https://github.com/dogtagpki/pki/issues/2297
If you want to receive further updates on the issue, please navigate to the GitHub issue and click on Subscribe button.
Subscribe
Thank you for understanding, and we apologize for any inconvenience.
Login to comment on this ticket.