Skip to content
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

pyterm: use python3 by default #10992

Merged
merged 1 commit into from
Feb 12, 2019
Merged

Conversation

cladmi
Copy link
Contributor

@cladmi cladmi commented Feb 11, 2019

Contribution description

Python3 has been the default in our scripts for some time now, but pyterm still
requested python which uses python2 on ubuntu stable.

This pushes toward only needing to install python3 python
dependencies.

Testing procedure

If you are using a distribution where python == python3 by default, it should not change anything.
Running tests with murdock here should not help as tests are not run with pyterm I think.

Running make term and make test with boards using pyterm should still work by default:

BOARD=samr21-xpro make --no-print-directory -C examples/hello-world/ info-debug-variable-TERMPROG
/home/harter/work/git/RIOT/dist/tools/pyterm/pyterm

Then testing make term in examples/default for example and running the tests should work the same as without this pull request.

./dist/tools/compile_and_test_for_board/compile_and_test_for_board.py . samr21-xpro

Vagrant

The vagrant image already installs python3-serial but would be nice to verify too.

  • Vagrant test of make term on a board.

Issues/PRs references

Found while testing on a machine where only python3 dependencies were installed.

#10870

Python3 has been the default in our scripts for some time now, but pyterm still
requested python which uses python2 on ubuntu stable.

This pushes toward only needing to install `python3` python
dependencies.
@cladmi cladmi added Type: enhancement The issue suggests enhanceable parts / The PR enhances parts of the codebase / documentation Area: tools Area: Supplementary tools labels Feb 11, 2019
@cladmi cladmi requested a review from aabadie February 11, 2019 16:35
@cladmi cladmi added the CI: ready for build If set, CI server will compile all applications for all available boards for the labeled PR label Feb 11, 2019
@jcarrano
Copy link
Contributor

I think this is OK, in fact, in my system python==python3, so I was already using pyterm with python3 anyways.

Just in case, though, I'd wait to see it it is working for others too before we merge.

@cladmi
Copy link
Contributor Author

cladmi commented Feb 12, 2019

I ran the test suite with samr21-xpro and all tests working in master were working.

Copy link
Contributor

@jcarrano jcarrano left a comment

Choose a reason for hiding this comment

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

I have been running pyterm with python3 since always with no issues.

@jcarrano jcarrano merged commit 505e7d8 into RIOT-OS:master Feb 12, 2019
@cladmi cladmi deleted the pr/pyterm/python3 branch February 12, 2019 12:55
@cladmi
Copy link
Contributor Author

cladmi commented Feb 12, 2019

Thank you for the review.

@aabadie aabadie added this to the Release 2019.04 milestone Feb 22, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Area: tools Area: Supplementary tools CI: ready for build If set, CI server will compile all applications for all available boards for the labeled PR Type: enhancement The issue suggests enhanceable parts / The PR enhances parts of the codebase / documentation
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants