[Bug 251019] New port: lang/tauthon: Backwards-compatible fork of Python 2.7 interpreter with Python 3.x features

bugzilla-noreply at freebsd.org bugzilla-noreply at freebsd.org
Tue Nov 10 15:42:38 UTC 2020


https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=251019

            Bug ID: 251019
           Summary: New port: lang/tauthon: Backwards-compatible fork of
                    Python 2.7 interpreter with Python 3.x features
           Product: Ports & Packages
           Version: Latest
          Hardware: Any
                OS: Any
            Status: New
          Severity: Affects Some People
          Priority: ---
         Component: Individual Port(s)
          Assignee: ports-bugs at FreeBSD.org
          Reporter: olivier.freebsd at free.fr

Created attachment 219523
  --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=219523&action=edit
Patch file for new port

Small description (see pkg-desc in diff):

"""
Tauthon is a backward-compatible fork of Python's 2.7.18 interpreter with new
syntax, builtins, and libraries backported from Python 3.x.

Python code and C-extensions targeting Python 2.7 or below are expected to run
unmodified on Tauthon and produce the same output. But with Tauthon, that code
can now use some of the new features from Python 3.x.
"""

Tauthon can be used with old code bases that will take time to migrate (or
won't be migrated at all). My use case is the build infrastructure for New
Moon, which I'll submit next as a new port.

This port is modeled after lang/python27, with irrelevant bits (AFAIK) removed,
and specific ones added. As lang/python*, core modules with big dependencies
are omitted, and should be re-enabled in other ports (I did not do it since I
don't have any immediate use for them).

No changes were made to Uses/python.mk, so currently no existing py-* port can
use this version automatically. bapt@ is against such a change, but it might be
useful for folks that want to install some packages under Tauthon (I currently
don't have any use for this), although I guess that 'pip' could be used
instead.

I intend to maintain it, but I'd be happy to defer to python@ (and participate
there from time to time) if you prefer.

-- 
You are receiving this mail because:
You are the assignee for the bug.


More information about the freebsd-ports-bugs mailing list