Visitar URL original
Port to Python 3 · Issue #34 · namecoin/nmcontrol · GitHub
Skip to content

Port to Python 3 #34

Open
Open

Description

@JeremyRand

Python 3 is becoming the default on many Linux distros, and Python 2 is not receiving feature updates anymore. We should port to Python 3.

--- Want to back this issue? **[Post a bounty on it!](https://www.bountysource.com/issues/3033117-port-to-python-3?utm_campaign=plugin&utm_content=tracker%2F435873&utm_medium=issues&utm_source=github)** We accept bounties via [Bountysource](https://www.bountysource.com/?utm_campaign=plugin&utm_content=tracker%2F435873&utm_medium=issues&utm_source=github).

Activity

  1. phelixbtc commented on Jul 9, 2014

    @phelixbtc

    IMHO Python 2 still has the upper hand by far. I think pyinstaller which I would like to use with nmcontrol may not yet work with Python 3. I suggest we at least stay Python 2 compatible.

  2. indolering commented on Nov 23, 2014

    @indolering

    Pyinstaller has experimental Python 3 support. NMControl is about to see a lot of functionality added (possible rewrite due to licensing issues, porting Unbound and namecoin2bind, adding a standard JSON-RPC library, etc) and sticking to Python 2 will just add to the technical debt.

    Has anyone run NMControl through 2to3 to see how hard this will be?

  3. JeremyRand commented on Jan 5, 2015

    @JeremyRand
    MemberAuthor

    @indolering I'm not sure how much I trust PyInstaller's "experimental" support, particularly since I can't find any documentation for it.

    That said, we're planning on integrating mitmproxy, and they're planning to switch to Python 3 in the foreseeable future. So we will probably have to make the switch when they do.

  4. JeremyRand commented on Jan 5, 2015

    @JeremyRand
    MemberAuthor

    @phelixbtc are there any objections to Python 3 other than PyInstaller compatibility?

  5. indolering commented on Jan 5, 2015

    @indolering

    Shouldn't our proxy software use the RPC interface? I doubt that, for
    example, Tor would use mitmproxy.
    On Jan 4, 2015 7:52 PM, "JeremyRand" notifications@github.com wrote:

    @phelixbtc https://github.com/phelixbtc are there any objections to
    Python 3 other than PyInstaller compatibility?

    —
    Reply to this email directly or view it on GitHub
    #34 (comment).

  6. phelixbtc commented on Jan 17, 2015

    @phelixbtc

    I doubt any major distro will remove Python2 anytime soon: https://wiki.ubuntu.com/Python/3
    2020!

  7. JeremyRand commented on May 14, 2015

    @JeremyRand
    MemberAuthor

    To repeat my previous question: @phelixbtc are there any objections to Python3 other than PyInstaller compatibility?

    FYI As far as I can tell, Fedora 22 (coming out this month) will only include Python3 by default, according to http://www.phoronix.com/scan.php?page=news_item&px=Fedora-22-Python-3-Status . Python2 will still be available via yum.

  8. alejandro-colomar commented on May 25, 2020

    @alejandro-colomar

    I doubt any major distro will remove Python2 anytime soon: https://wiki.ubuntu.com/Python/3
    2020!

    The time has come.

    Python2 is officially not supported: python/devguide#344
    Debian Bullseye (11) is going to remove python2: https://lists.debian.org/debian-python/2019/07/msg00080.html

    How is the state of the port to python3?

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