From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-wm1-x32e.google.com (mail-wm1-x32e.google.com [IPv6:2a00:1450:4864:20::32e]) by sourceware.org (Postfix) with ESMTPS id D5C3A3858C27 for ; Mon, 3 Jan 2022 21:42:36 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.1 sourceware.org D5C3A3858C27 Authentication-Results: sourceware.org; dmarc=pass (p=none dis=none) header.from=gmail.com Authentication-Results: sourceware.org; spf=pass smtp.mailfrom=gmail.com Received: by mail-wm1-x32e.google.com with SMTP id o30so19602204wms.4 for ; Mon, 03 Jan 2022 13:42:36 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=message-id:date:mime-version:user-agent:subject:content-language:to :references:from:in-reply-to:content-transfer-encoding; bh=qhQTOLRpNmFg+g6tZ4PAJWXLxN3DXA68QHibfOCcf2o=; b=C0ACqTBOv/7D485jUOIUeJV0xacp0gZg1KyS+Jdf55julseX5eSW4KA8piO9+9rKo5 rlWO6zX74ZJuviUlSMefd8snmM1xsXLebiuD2+Dt0+GtTDQaZvQX4MW9Uh1HBIH7D23V W0GCeKX6yv04JKuNO9Z3O5ca4udyMN/IMXCvStDtxrqhsCwtDwjYD8r9bnkcMG2l3mBF 0d/zBDhKuWYVQrNzW/R7l0Lc6/mBbnM8Icd80CNgyUGSVwGQ92m59h1DwkoRre/opJXK ycLLTLgRuhLuvSrAIJ1F2VYVHGrgXFtQPOGKo3KSKN7s5PDpluFiAmZXkSW83k+kCZGP 2pAQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:message-id:date:mime-version:user-agent:subject :content-language:to:references:from:in-reply-to :content-transfer-encoding; bh=qhQTOLRpNmFg+g6tZ4PAJWXLxN3DXA68QHibfOCcf2o=; b=UBS0DIh/RZkMAJtTaHAajgH77TcvVtMfiIagWj+TZT1g37BrbVS4vp6l1GXsUXaAOL MP1PCTYk8zZlU7CoMu9WCxGSQuUn+MIK5YT0uksLpiwBAuV0ZVtnsV/JvNtE47VqKHH6 WpcsV6ktczUHGGhTOo/gLrGQoWyhF7fdNQq22vbFkK/yaH8FK5DDzzbY7VZdRd3NmHXY itY197mHeCYJvUGKvcbBOZCs9vtvBN51NaSZ9vX3kIOQN0tigjKNx7AoKi1X/kYTZ1xy y2n4CU2hIo4yS6GTapEg2aSSHnFrQoCztO9GvSOYqHPDQ/DcOQj5glIXZhzwIw2whwzu fvEQ== X-Gm-Message-State: AOAM532DDaJXDROGHfWpuu30XDdNBofYr5IVuApeJ/FmK7gxPZ72ZaAu iU3E8UjV0B+72m5fuTK8c4noYHBjGkA= X-Google-Smtp-Source: ABdhPJzUdo8uCP3I+QHWiOLDatMTiOWPfbPPIHMPzz+99OBXGVBM3qZaJ3gdg4JTeeAYVk5qpF+mRw== X-Received: by 2002:a05:600c:35d1:: with SMTP id r17mr33378571wmq.147.1641246155798; Mon, 03 Jan 2022 13:42:35 -0800 (PST) Received: from ?IPV6:2003:cc:9f2f:3e52:f11c:7fc6:6c05:1276? (p200300cc9f2f3e52f11c7fc66c051276.dip0.t-ipconnect.de. [2003:cc:9f2f:3e52:f11c:7fc6:6c05:1276]) by smtp.gmail.com with ESMTPSA id h14sm36123146wrz.31.2022.01.03.13.42.35 for (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Mon, 03 Jan 2022 13:42:35 -0800 (PST) Message-ID: Date: Mon, 3 Jan 2022 22:42:34 +0100 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:91.0) Gecko/20100101 Thunderbird/91.4.1 Subject: Re: [patch] cygport : update to python 3.9 Content-Language: it To: cygwin-apps@cygwin.com References: <9eb22f83-e7e9-1ec5-1aed-5e0b6c8c7848@gmail.com> From: Marco Atzeri In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit X-Spam-Status: No, score=-1.8 required=5.0 tests=BAYES_00, BODY_8BITS, DKIM_SIGNED, DKIM_VALID, DKIM_VALID_AU, DKIM_VALID_EF, FREEMAIL_FROM, KAM_NUMSUBJECT, NICE_REPLY_A, RCVD_IN_DNSWL_NONE, SPF_HELO_NONE, SPF_PASS, TXREP autolearn=ham autolearn_force=no version=3.4.4 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on server2.sourceware.org X-BeenThere: cygwin-apps@cygwin.com X-Mailman-Version: 2.1.29 Precedence: list List-Id: Cygwin package maintainer discussion list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 03 Jan 2022 21:42:38 -0000 On 03.01.2022 18:37, Jon Turney wrote: > On 31/12/2021 10:00, Marco Atzeri wrote: >> Attached patch moves "default" from 3.6 to 3.9 >> Other point: >> >> As 3.5 was never really deployed, I think we can remove it from the >> distribution. >> >> As we have a lot of python3-* is obsoleted py python36-* >> what is the best way to updated to python39-* when available ? > > Good question.  Note the comment before this hunk: > >> @@ -128,7 +128,7 @@ >>                 # and MUST NOT be updated when defaults change >>                 case ${ver} in >>                 2.7)    declare -g >> python27_${PYTHON_WHEEL_NAME//[-\.]/_}_OBSOLETES="python-${PYTHON_WHEEL_NAME} >> python2-${PYTHON_WHEEL_NAME}" ;; >> -               3.6)    declare -g >> python36_${PYTHON_WHEEL_NAME//[-\.]/_}_OBSOLETES="python3-${PYTHON_WHEEL_NAME}" >> ;; >> +               3.9)    declare -g >> python39_${PYTHON_WHEEL_NAME//[-\.]/_}_OBSOLETES="python3-${PYTHON_WHEEL_NAME}" >> ;; >>                 esac >>                 declare -g >> python${ver/.}_${PYTHON_WHEEL_NAME//[-\.]/_}_CONTENTS="usr/lib/python${ver}/site-packages/ >> usr/share/doc/python${ver/.}-${PYTHON_WHEEL_NAME}" >>         done > > which in full reads: > > " >         # these were 2&3 at the time of the XY-version split, >         # and MUST NOT be updated when defaults change > " > > So it seems to me that either that hunk is wrong, or that comment needs > updating > > I'm not sure what the intent is here. I guess Yaakov was thinking of python3 as the older alias of python36, and **only** for that. As Python2 is the older alias of python27. In that case make sense to leave as the comment says. Probably I should write entries in the FAQ and documentation to clarify this scope. Following is a sort of RFC, so let me know your opinion. Currently we have two type of Python packages 1) Pure python that exists at max as 2.7 3.6 3.7 3.8 3.9 plus 2 and 3 in that case 2/2.7 3/3.6 are EOL; I stopped last year to update the 2.7 and I am thinking to do the same for 3.6 now. I do not see the need to continue to update 3.7, it never become default as we jumped from 3.6 to 3.8 and it is not more active upstream: https://www.python.org/dev/peps/pep-0537/#lifespan We can update the 3.8 and 3.9 while preparing/testing for 3.10 source package will continue to use the "python-*" form, while "python3-*" should not be used. 2) python packages derived from other packages, where the nomenclature is not uniform: Where we have all variants libxml2 python27-libxml2 libxml2 python36-libxml2 libxml2 python37-libxml2 libxml2 python38-libxml2 Only one as I moved from supporting 2 to supporting only 3 postgresql postgresql-plpython To hybrid version openbabel python2-openbabel (not updated anymore) openbabel python38-openbabel I think we should stop to call derived packages "python3-*". Or we use the full version as python38-openbabel or no version at all as python-gdal In general We should also stop to pull as dependency "python3" or "python3-devel" as build dependency. Use the full version for dependencies. Plus use "python3_fix_shebang SCRIPT" for setting the proper interpreter and avoid the issue seen on mercurial and dblatex https://cygwin.com/pipermail/cygwin/2021-December/250282.html I used a cruder version but python3_fix_shebang should do the work Regards Marco