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

BSL: Change PYTHON value to python3 #1448

Merged
merged 2 commits into from Nov 26, 2020
Merged

BSL: Change PYTHON value to python3 #1448

merged 2 commits into from Nov 26, 2020

Conversation

jeppenodgaard
Copy link

Should fix #1444

@g-oikonomou
Copy link
Member

Thanks.

We are excluding #1441 from the upcoming release (but keeping it in develop), it looks like there is a little bit of work to be done in order to transition cleanly to Python 3, but it's good that we've started this already.

@g-oikonomou g-oikonomou added this to the Version 4.7 milestone Nov 23, 2020
@g-oikonomou g-oikonomou added the pr/bugfix Used for PRs that fix a bug of any severity label Nov 23, 2020
@jeppenodgaard
Copy link
Author

jeppenodgaard commented Nov 23, 2020

I consider removing the $(PYTHON) ... from the BSL lines because the script uses shebang to choose the correct interpreter. Would this be a better approach?

@g-oikonomou
Copy link
Member

So you are saying we should make the script executable and run it in itself?

@jeppenodgaard
Copy link
Author

That is my suggestion yes. The file already seems to have executable permissions.
This allows removing the PYTHON variable and the need to maintain it.
I'm not sure if there's any cons to this approach..

@g-oikonomou
Copy link
Member

@atiselsts how do you feel about this?

@atiselsts
Copy link
Member

I prefer the shebang approach (just learned that is the name of the thing!). It reduces the number of times python version is referenced in the codebase and is consistent with the approach already used in older platforms (Sky and Z1).

@g-oikonomou
Copy link
Member

OK, I too would be happy with that. @jeppenodgaard do you have time to work on it?

@jeppenodgaard
Copy link
Author

jeppenodgaard commented Nov 25, 2020

@g-oikonomou Yes. I should be able to test it tomorrow.

@jeppenodgaard
Copy link
Author

Ready for review

@atiselsts atiselsts merged commit bbff460 into contiki-ng:develop Nov 26, 2020
@atiselsts atiselsts mentioned this pull request Nov 26, 2020
11 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
pr/bugfix Used for PRs that fix a bug of any severity
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Build problems for openmote-cc2538 (inconsistent Python version)
3 participants