Skip to content

Python 3 support #17

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
pekkaklarck opened this issue Mar 18, 2014 · 4 comments
Closed

Python 3 support #17

pekkaklarck opened this issue Mar 18, 2014 · 4 comments
Assignees
Milestone

Comments

@pekkaklarck
Copy link
Member

This would be especially handy because Robot Framework itself doesn't yet support Python 3. Most likely we will target Python 3.3 or newer and will at the same time drop support from versions prior to Python/Jython 2.5.

@mkorpela
Copy link
Member

mkorpela commented May 7, 2016

Pabot will not support Python 3 before this is done

mkorpela/pabot#54

invalid syntax (robotremoteserver.py, line 103)

@molsky
Copy link

molsky commented Aug 17, 2016

I have tried to implement Python3 support but 24 acceptance tests are failing with Python3 and I have not yet figured out why. With Python2.7 atests and utests goes with 100% success.

Changes:
https://github.com/molsky/PythonRemoteServer/tree/python2-3

screen shot 2016-08-17 at 11 09 55 2

screen shot 2016-08-17 at 11 43 46 2

@userzimmermann
Copy link

Hi @molsky
Great work :) I took your approach a bit further:
https://github.com/userzimmermann/PythonRemoteServer/tree/python2-3

Only 3 failing atests left with python3, but all due to different unicode string display in comparison.
@pekkaklarck Those well known Expected error 'Hyv\xe4' but got 'Hyvä'. like problems from my earlier robotframework-python3 fork... ;) How did you unify those tests in robotframework 3.0?

BTW: Is the six dependency ok or better replace with custom definitions?

pekkaklarck added a commit that referenced this issue Jan 9, 2017
At the same time also dropped support from Python < 2.6. Docs and
setup.py needs to be updated before #17 can be considered done.
pekkaklarck added a commit that referenced this issue Jan 9, 2017
- Python 3 support. Related to #17.
- Documentation cleanup.
- Make it explicit example works on a single machine only. Fixes #30.
pekkaklarck added a commit that referenced this issue Jan 9, 2017
@pekkaklarck
Copy link
Member Author

The code should now support Python 3. Acceptance tests run successfully with Python 3.3-3.6 both on Linux and Windows and also with PyPy 3 on Linux.

Tasks still todo:

  • Go through docs. Should update them to mention Python 3 is supported and also that we support PyPy.
  • Update setup.py. Need to add correct classifiers there.

pekkaklarck added a commit that referenced this issue Jan 10, 2017
- Use setuptools when available.
- Update classifiers. Includes Python 3 support (#17).
- Add me as author instead of generic RF Developers.
@pekkaklarck pekkaklarck self-assigned this Apr 13, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants