• State Verified Answer
  • Replies 3 replies
  • Subscribers 62 subscribers
  • Views 2553 views
  • Users 0 members are here
Attachments (0)
Nordic Case Info
  • Case ID: 222825
Options
This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

NRFUtil Python3 Support 2019?

JRitzenhoff

My company has developed an application in Python3. We need to integrate the pc-nrfutil scripts (https://github.com/NordicSemiconductor/pc-nrfutil) with our application.

I know that Python3 development is underway (https://devzone.nordicsemi.com/f/nordic-q-a/28554/nrfutil-python3-support), but believe that a Python3 codebase has not been released yet. 

I was able to install the “nrfutil” module using pip3 which gives me the impression that the primary holdback is now the pc-ble-driver.py file (https://github.com/NordicSemiconductor/pc-nrfutil/issues/158).

Is the current pc-nrfutil version in fact Python3 compatible? If not, are there any work-arounds we can implement until the Python3 compatible version is released.

Thanks in advance

Parents
  • +1

    Hi.

    It really depends on what you want to use nrfutil to.

    If you require BLE DFU, it will not work since py3 is not yet supported in pc-ble-driver.py, it will however soon be released (I cannot comment more details about this, read more here).

    If you dont require BLE DFU, I think that you should be able to make it work by removing imports which has to do with the pc-ble-driver.py.

    I hope this answer is satisfactory.

    Best regards,

    Andreas

  • 0 in reply to AndreasF

    You guys do realize that Python 2 will be COMPLETELY unsupported in only 120 days from now, right? That's the end of the line. Less than three months away.

    This has been causing me grief for a while because all of my other client infrastructure has been upgraded to Python 3 for more than 18 months, and it's needlessly difficult to have to make Python 3 code interoperate with a Python 2 only library.

Reply
  • 0 in reply to AndreasF

    You guys do realize that Python 2 will be COMPLETELY unsupported in only 120 days from now, right? That's the end of the line. Less than three months away.

    This has been causing me grief for a while because all of my other client infrastructure has been upgraded to Python 3 for more than 18 months, and it's needlessly difficult to have to make Python 3 code interoperate with a Python 2 only library.

Children
No Data
Related