From nobody Wed Nov 17 07:58:07 2021 X-Original-To: python@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 458291899E24 for ; Wed, 17 Nov 2021 07:58:22 +0000 (UTC) (envelope-from sobomax@sippysoft.com) Received: from mail-ed1-f41.google.com (mail-ed1-f41.google.com [209.85.208.41]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1D4" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4HvFfh6T5Qz4blh for ; Wed, 17 Nov 2021 07:58:20 +0000 (UTC) (envelope-from sobomax@sippysoft.com) Received: by mail-ed1-f41.google.com with SMTP id w1so6945509edd.10 for ; Tue, 16 Nov 2021 23:58:20 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:from:date:message-id:subject:to:cc; bh=dSsImfnQok8Ow/f0XAshtDxbeuiLgmVAjy2xtw7BmqA=; b=cWIlPW0ySuAPZ2yNaFUAIrhGgm6YurWRjEjuoiaSidk5RuCtZrvy823u3YmRGUyGXc JYpnE4cZ7qyvqKzfOkRNSVH07ZhNnNb0ZVb8AQt5iBQqhgHOZ7YJKYVVMYoDgFgyQOrk WpMbaEQRL1ip8Gl6kUfTz3+gylXKjXSsXV8ZG+ng+J97GbHpzjLj++3iC0C9OMhC2zyp wgJhwDbER3Tum0mPObFi7bPbd1gQFVq9E5kLAlUkE03sV7qW4NYMo2wnDUk736jw1TQ5 p5o9BKQEiqmQCjGYz3OpbyRKiLyyNIZqc6sZ1LVQ/sayp9udYC7zJRIx0nGqAZMtzqcm I1aQ== X-Gm-Message-State: AOAM530wWUDTgo/obidpKKsB/8GDbgh3YXp4D6D47enSSQs1G8CCN+M+ vdr4Xp33zcqMIR1l+SnMBjNrbGaOLiG0XVpTU7I5UQ== X-Google-Smtp-Source: ABdhPJxxEYzX/t5TIdPRp1bWsuFhfx/Mt4q8+6urutOYUDbqvnuFrRlFSuLphIVDmBFxg+U7NcERqICZEi1Zpl4y7Zw= X-Received: by 2002:a05:6402:50c6:: with SMTP id h6mr18966396edb.228.1637135899588; Tue, 16 Nov 2021 23:58:19 -0800 (PST) List-Id: FreeBSD-specific Python issues List-Archive: https://lists.freebsd.org/archives/freebsd-python List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-python@freebsd.org X-BeenThere: freebsd-python@freebsd.org MIME-Version: 1.0 From: Maxim Sobolev Date: Tue, 16 Nov 2021 23:58:07 -0800 Message-ID: Subject: Bringing back lang/python27 with few modules? To: ports@freebsd.org, Rene Ladan Cc: portmgr@freebsd.org, python@freebsd.org Content-Type: multipart/alternative; boundary="000000000000be8cad05d0f76765" X-Rspamd-Queue-Id: 4HvFfh6T5Qz4blh X-Spamd-Bar: / Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=none; spf=pass (mx1.freebsd.org: domain of sobomax@sippysoft.com designates 209.85.208.41 as permitted sender) smtp.mailfrom=sobomax@sippysoft.com X-Spamd-Result: default: False [0.00 / 15.00]; SUBJECT_ENDS_QUESTION(1.00)[]; ARC_NA(0.00)[]; FREEFALL_USER(0.00)[sobomax]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_THREE(0.00)[4]; TO_DN_SOME(0.00)[]; R_SPF_ALLOW(-0.20)[+ip4:209.85.128.0/17]; MIME_GOOD(-0.10)[multipart/alternative,text/plain]; PREVIOUSLY_DELIVERED(0.00)[python@freebsd.org]; DMARC_NA(0.00)[freebsd.org]; NEURAL_SPAM_MEDIUM(1.00)[1.000]; NEURAL_HAM_LONG(-1.00)[-1.000]; TO_MATCH_ENVRCPT_SOME(0.00)[]; NEURAL_HAM_SHORT(-1.00)[-1.000]; RCVD_IN_DNSWL_NONE(0.00)[209.85.208.41:from]; FORGED_SENDER(0.30)[sobomax@freebsd.org,sobomax@sippysoft.com]; RWL_MAILSPIKE_POSSIBLE(0.00)[209.85.208.41:from]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+,1:+,2:~]; ASN(0.00)[asn:15169, ipnet:209.85.128.0/17, country:US]; FROM_NEQ_ENVFROM(0.00)[sobomax@freebsd.org,sobomax@sippysoft.com]; RCVD_TLS_ALL(0.00)[]; RCVD_COUNT_TWO(0.00)[2] X-ThisMailContainsUnwantedMimeParts: Y --000000000000be8cad05d0f76765 Content-Type: text/plain; charset="UTF-8" Hi, I am still a bit concerned with the total removal of python 2.7 year ago and its support, I think this was a somewhat swift decision that may need to be re-considered. I understand the urge for portmgr to move base over to a supported version, but also that caused few important packages to be dropped out of the FreeBSD without any fix in sight. I am specifically talking about the PyPy package, which needs 2.7 to bootstrap itself even when compiled as a "Python3" version. At the same time we still have a port of for example GCC 4.6, which is like what, 15 years old? Also things in the tree like jython or micropython are effectively python 2 implementations, so why are they allowed to be present while not rock solid and field tried 2.7? In fact jython specifically recommends using CPython2.7 to byte-compile some of the code that it cannot chew by itself, so it's somewhat broken as well*. Is there any chance to bring CPython2.7 at the very least as a NO_PACKAGE build tool that could be used for such cases now that we have moved most of the supported packages to 3.x land? I had always considered FreeBSD to be about "tools not policy", but in this particular case the policy seemingly took priority over tools and common sense. Sorry if I am beating a dead horse here, just wanted to gauge the position of the project before I go and open yet another bug report. Thanks! -Max *) Like the following: java.lang.RuntimeException: java.lang.RuntimeException: Encountered too large method code in /usr/ports/lang/pypy/work/pypy3.8-v7.3.7-src/rpython/rlib/unicodedata/unicodedb_6_0_0.py Please provide a CPython 2.7 bytecode file (.pyc) to proceed, e.g. run python -m py_compile /usr/ports/lang/pypy/work/pypy3.8-v7.3.7-src/rpython/rlib/unicodedata/unicodedb_6_0_0.py and try again. Alternatively provide proper CPython 2.7 execute command via cpython_cmd property, e.g. call jython -J-Dcpython_cmd=python or if running pip on Jython: pip install --global-option="-J-Dcpython_cmd=python" *** Error code 255 --000000000000be8cad05d0f76765--