Summary: pyosaf: Ensure compatibility with Python 3 [#2492] Review request for Ticket(s): 2492 Peer Reviewer(s): Srikanth, Hans Pull request to: Affected branch(es): develop Development branch: ticket-2492 Base revision: db1965d634eac2f375f455b7b7d3e9f70ff0c47c Personal repository: git://git.code.sf.net/u/anders-w/review
-------------------------------- Impacted area Impact y/n -------------------------------- Docs n Build system n RPM/packaging n Configuration files n Startup scripts n SAF services n OpenSAF services y Core libraries n Samples n Tests n Other n Comments (indicate scope for each "y" above): --------------------------------------------- revision 312674e5ca8bb4ec50a1d2d843d3db3bcbddfe02 Author: Anders Widell <[email protected]> Date: Tue, 13 Jun 2017 15:05:42 +0200 pyosaf: Ensure compatibility with Python 3 [#2492] Ensure compatibility with Python 3 by running the Python source code files through the Automated Python 2 to 3 code translation tool "2to3". For more information about this tool, see: https://docs.python.org/3/library/2to3.html Complete diffstat: ------------------ python/pyosaf/saEnumConst.py | 6 +++--- python/pyosaf/utils/immoi/__init__.py | 8 +++---- python/pyosaf/utils/immoi/implementer.py | 36 ++++++++++++++++---------------- python/pyosaf/utils/immom/__init__.py | 6 +++--- python/pyosaf/utils/immom/ccb.py | 17 ++++++++------- python/pyosaf/utils/immom/iterator.py | 8 +++---- python/pyosaf/utils/immom/object.py | 2 +- 7 files changed, 42 insertions(+), 41 deletions(-) Testing Commands: ----------------- Run regression tests for the Python bindings using both Python 2 and Python 3 Testing, Expected Results: -------------------------- Regression tests shall pass both when using Python 2 and Python 3 Conditions of Submission: ------------------------- Ack from reviewer(s) Arch Built Started Linux distro ------------------------------------------- mips n n mips64 n n x86 n n x86_64 y y powerpc n n powerpc64 n n Reviewer Checklist: ------------------- [Submitters: make sure that your review doesn't trigger any checkmarks!] Your checkin has not passed review because (see checked entries): ___ Your RR template is generally incomplete; it has too many blank entries that need proper data filled in. ___ You have failed to nominate the proper persons for review and push. ___ Your patches do not have proper short+long header ___ You have grammar/spelling in your header that is unacceptable. ___ You have exceeded a sensible line length in your headers/comments/text. ___ You have failed to put in a proper Trac Ticket # into your commits. ___ You have incorrectly put/left internal data in your comments/files (i.e. internal bug tracking tool IDs, product names etc) ___ You have not given any evidence of testing beyond basic build tests. Demonstrate some level of runtime or other sanity testing. ___ You have ^M present in some of your files. These have to be removed. ___ You have needlessly changed whitespace or added whitespace crimes like trailing spaces, or spaces before tabs. ___ You have mixed real technical changes with whitespace and other cosmetic code cleanup changes. These have to be separate commits. ___ You need to refactor your submission into logical chunks; there is too much content into a single commit. ___ You have extraneous garbage in your review (merge commits etc) ___ You have giant attachments which should never have been sent; Instead you should place your content in a public tree to be pulled. ___ You have too many commits attached to an e-mail; resend as threaded commits, or place in a public tree for a pull. ___ You have resent this content multiple times without a clear indication of what has changed between each re-send. ___ You have failed to adequately and individually address all of the comments and change requests that were proposed in the initial review. ___ You have a misconfigured ~/.gitconfig file (i.e. user.name, user.email etc) ___ Your computer have a badly configured date and time; confusing the the threaded patch review. ___ Your changes affect IPC mechanism, and you don't present any results for in-service upgradability test. ___ Your changes affect user manual and documentation, your patch series do not contain the patch that updates the Doxygen manual. ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot _______________________________________________ Opensaf-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/opensaf-devel
