-
Notifications
You must be signed in to change notification settings - Fork 35
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
Python2 compatibility #39
Comments
As you're probably well aware Python 2 hit EOL over a year ago. And having hung out with some slow-moving distributions like RHEL when projects demand it, I know not all of the world has moved on and I don't have a problem trying to continue to support it (even though I don't have a GDB build that can use it myself). This is a tiny project. I don't think we'll be able to just cherry-pick due to the extent of changes made to fully move to python3 but we can adapt. I don't anticipate adding new features to the python2 branch but bug fixes are fine. The latest commit I thought was python2 compatible was 8b2fe14 back in November 2020. Can you confirm? https://github.com/bnahill/PyCortexMDebug/tree/python2 Thanks! |
Of course I am. :-) The commit 8b2fe14 leads to:
No need to spend much time on it, people can find this issue if they run into it. The commit 76fe009 worked fine for me. |
Alright, updated the python2 branch to 76fe009. Good to close? |
Seeing similar issues as @mrquincle with the latest arm gdb release. Of course Python 2 is EOL but many embedded developers work in environments where recompiling everything just isn't an option (Windows systems and/or high security environments). A proper fix/acknowledgment would be welcome as this tool looks very useful and is referenced from many places! |
@radix07 You realize that there's now the https://github.com/bnahill/PyCortexMDebug/tree/python2 branch? |
The tar balls of cross-compilers tend to come nowadays with python support, e.g.
arm-none-eabi-gdb-py
, but this not yet the case for python3, there's noarm-none-eabi-gdb-py3
binary.This means that your much appreciated code won't work out of the box for developers who don't compile their cross-compilers themselves.
The following commit is still python-2 compatible:
However, maybe it's nice to tag that release (or maybe a later release which is still not python3) and indicate that towards the users of this repository in the
README.md
? Or alternatively, create apython2
branch and cherry-pick a few of the bugs that have been fixed over time.Thanks for your work, much appreciated!
The text was updated successfully, but these errors were encountered: