Skip to content

Print fix #626

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

Merged
merged 4 commits into from
Sep 5, 2016
Merged

Print fix #626

merged 4 commits into from
Sep 5, 2016

Conversation

eino-makitalo
Copy link
Contributor

Some 2to3 partial changes to be done for future python 3 work.

  • exceptions
  • print statements
  • dictionary handlers
    These seems to go ok without extra modifications

@aaltat
Copy link
Contributor

aaltat commented Aug 5, 2016

I am on holiday, so will take a look after the holidays are over.

@eino-makitalo
Copy link
Contributor Author

Nice holiday. This is just small part of #479 (python 3)

@HelioGuilherme66
Copy link
Member

Hi,
I merged your PR but it make the tests fail in Python 3.
Compare with my branch at code_futurized with your PR merged

Let me call to attention that we have several PRs for Python 3 compatibility, mine is #564.

@eino-makitalo
Copy link
Contributor Author

Yes. I check your combined PR and this change is small bite. There are - I agree - plenty of issues to check and fix to make same code base running both python2 / python 3. I just tested in the first place those changes not violating python 2 code base and make code closer to python 3. Python 3 working tests need also more work to get work back to agile path. I also run those tests with Windows / Python 3.5 and they failed but you cant eat whole cake. So I just run those 2to3.py tests which did not break python 2 codebase.

@pekkaklarck
Copy link
Member

Thanks for the PR. I've promised to take care of S2L Py3 support and will review related PRs as soon as I got time. Current main blockers are finishing our move to a new home and getting new S2L release (w/p Py3 support) out with @aaltat. Realistically that means I can concentrate on this task at the end of this month.

@aaltat
Copy link
Contributor

aaltat commented Aug 25, 2016

The 1.8.0 is out and during the release process we changed few things. The changes caused a conflict(s) and by looking the pull request I can see at leas one problem. The doc/buildhtml.py was removed in 652410d Could you fix the problem? Also for my eyes it looks OK, but I am more of a Python 2 person than Python 3.

@aaltat aaltat merged commit f5229cf into robotframework:master Sep 5, 2016
@@ -28,7 +28,7 @@ def _run_on_failure_decorator(method, *args, **kwargs):
class KeywordGroupMetaClass(type):
def __new__(cls, clsname, bases, dict):
if decorator:
for name, method in dict.items():
for name, method in list(dict.items()):
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

list isn't needed here.

Gaurang033 pushed a commit to Gaurang033/Selenium2Library that referenced this pull request Oct 17, 2016
* 2to3.py runned for  print & except

* 2to3.py runned for  except

* 2to3.py -f dict
VitoAlbano pushed a commit to VitoAlbano/Selenium2Library that referenced this pull request Oct 18, 2016
* 2to3.py runned for  print & except

* 2to3.py runned for  except

* 2to3.py -f dict
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants