dogtagpki

#1738 RPM build should check for flake8 and py3k violations
Closed: Fixed Opened by cheimes.

Closed: Fixed
Reopen Issue

The spec file for pki-core already checks the Python code with pylint. The checks are only performed with Python 2. No checks ensures compatibility with Python 3. Further more there are no automated tests for PEP 8 conformity with flake8 in the build process.

I've already posted a patch set on the mailing list:

  • Patch 45 runs pylint with --py3k options as well as runs flake8 under Python 2 and Python 3.
  • Patch 46 fixes a couple of PEP 8 violations.

Pushed to master in 0d2d97f9bf6802f6f81090eca6e135e50fea7883 (pylint and flake8 checks) and cb6b0c4855885c03d056acb8f98c96de986e081e (fix violations)

Internal change

Metadata Update from @cheimes:
- Issue set to the milestone: 10.3.0

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/2296

If you want to receive further updates on the issue, please navigate to the
GitHub issue and click on Subscribe button.

Thank you for understanding, and we apologize for any inconvenience.
Metadata
None
None
None
None
Normal
enhancement
Packaging
Packaging/ Upgrade
0
Community
edewata
Static archive. pagure.io was sunset in 2026; this is a read-only snapshot.
Red Hat Logo

Fedora is sponsored by Red Hat. Learn more about the relationship between Red Hat and Fedora »

© Red Hat, Inc. and others.