Comment #21 on issue 1506 by [email protected]: Python 3 support
http://code.google.com/p/robotframework/issues/detail?id=1506
Merged with 2.8.4 and made the whole robot code directly Python 2.7/3.3+
compatible,
by applying backwards compatible 2to3 diffs and integrating six.
I also simplified and/or extended some of the existing workarounds.
I used six for the following cases:
- all version queries with six.PY2/PY3
- basestring --> six.string_types
- (int, long) --> six.integer_types
- to keep 'unicode' --> from six import text_type as unicode
- __metaclass__ --> @six.add_metaclass
Diff of direct compatibility step:
https://bitbucket.org/userzimmermann/robotframework-python3/branches/compare/3da31c1..939ab93#diff
Complete diff to 2.8.4:
https://bitbucket.org/userzimmermann/robotframework-python3/branches/compare/3da31c1..2.8.4#diff
I didn't test the code with Jython/IronPython 2.7 so far.
I will continue with the utest/atest py code.
I still do dynamic PY3 conversions of the atest data in run_atests:
- Remove u prefixes and replace \u and \x codes with chars for matching
string reprs
- Remove L suffixes for evaluating number literals and matching reprs
This needs a static solution... maybe someone interested in helping? :)
I also need to implement a generic way to check for PY2/3 in testdata/
And finally... there are some remaining PY3 bytes/str issues in Remote
library,
which let some atests fail...
--
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings
--
---
You received this message because you are subscribed to the Google Groups "robotframework-commit" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/groups/opt_out.
