Visitar URL original
Python 2 EOL · Issue #381 · chipsec/chipsec · GitHub
Skip to content

Python 2 EOL #381

Description

@DropBearWare

Chipsec seems to be done in Python 2 which enters official end of life phase on Jan 1st 2020. Time remaining now to port is < two years which probably is a good bit to keep in mind for a project of this complexity.

We could get started on an early analysis of what it would take to upgrade to Python 3.

-- References --

Activity

  1. ErikBjorge commented on May 1, 2018

    @ErikBjorge
    Member

    Yes, this is on our list to do this year. The current plan is to enable Python 2/3 compatibility so we don't break people too bad. Once we have Python 3 support released we can define a date where we may not support Python 2 failures in CHIPSEC.

    Our current plan is to start enabling chipsec_util with the mixed python support and thus get to the HAL/Helper modules as well. Once we know how much fun it will be from enabling chipsec_util we can complete the chipsec_main support conversion and module updates.

    To support this development we should also create a shared development branch.

    If you have comments or suggestions please let us know.

  2. DropBearWare commented on May 2, 2018

    @DropBearWare
    Author

    Glad to assist with testing, dev as this develops. Is the mentioned TO-DO for the year public or internal? If public, could you please share the link ?

  3. ErikBjorge commented on May 2, 2018

    @ErikBjorge
    Member

    We have just started scoping the task. Once we have a plan we will post it on the wiki for all to see and track progress.

  4. ErikBjorge commented on Jul 24, 2018

    @ErikBjorge
    Member

    Added Wiki page and branch for this task.
    https://github.com/chipsec/chipsec/wiki/Python-3-Conversion

  5. hughsie commented on Mar 27, 2019

    @hughsie
    Contributor

    If it's a datapoint, I can't use CHIPSEC in the LVFS until it can run on Python3.

  6. BrentHoltsclaw commented on Mar 27, 2019

    @BrentHoltsclaw
    Member

    The python-3 beta branch is almost feature complete at this point. There are issues with the compress and decompress functionality which will be addressed soon. We are going to merge the python 3 branch with the main branch again soon. After that the focus will be on fixing up the unit testing.

  7. hughsie commented on May 10, 2019

    @hughsie
    Contributor

    We are going to merge the python 3 branch with the main branch again soon

    Do you have a rough ETA? I'm being pushed for a feature and I don't know whether to use chipsec or uefi-firmware-parser for decompression. I'd obviously like to use the former if possible :)

  8. BrentHoltsclaw commented on May 13, 2019

    @BrentHoltsclaw
    Member

    All necessary pull requests have been merged into master. I'm going to create a python3 rc1 branch and release by tomorrow. There is still an issue with signed files that I need to put in a pull request for, but will work to get that updated by the end of the week.

  9. kuqin12 commented on May 22, 2019

    @kuqin12

    Hi may i know whether py3 change is in the feature branch yet? I am interested in this feature :) Thanks

  10. BrentHoltsclaw commented on May 22, 2019

    @BrentHoltsclaw
    Member

    We are working to get python3 RC-1 release out on 5/24.

  11. BrentHoltsclaw commented on May 24, 2019

    @BrentHoltsclaw
    Member

    python3-rc1 has been released with linux support. We will be working to enable other major OS support in the coming weeks. Please let us know if you run into any issues.

  12. BrentHoltsclaw commented on Oct 10, 2019

    @BrentHoltsclaw
    Member

    Python3 support has been added. Please open any problems with the python3 implementation as new issues. We will open a new issue for UEFI shell support.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions