Re: [ANNOUNCEMENT] python38 3.8.0-0.2.a3
On 2019-05-07 05:33, Oleksandr Gavenko wrote:
> On 2019-03-29, Yaakov Selkowitz wrote:
>> Eventually we will probably stop building most(*) modules for 3.6 too,
>> but not before the 3.7 transition is 100% complete, and more likely
>> just before or as part of the eventual 3.8 transition (in 2020 at the
> After upgrade I haven't found rst2html utility from python3-docutils. Can't
> tell you apt-cyg or what caused a problem.
> I found it in python37-docutils-0.14-1:
It is in the following packages, where python => python2 => python27, and
python3 => python36.
$ apt-cyg listall python*-docutils
python-docutils 0.14-1 noarch
python2-docutils 0.14-1 noarch
python27-docutils 0.14-1 noarch
python3-docutils 0.14-1 noarch
python36-docutils 0.14-1 noarch
python37-docutils 0.14-1 noarch
> Assuming that Python versions live in parallel now how should I upgrade on
> next major rebuild from 3.7 to 3.8, etc?
> My concern is that obsolete python37-docutils-0.14 should depends on new
> python38-docutils-0.xx for some period of time and after python37-docutils has
> been removed there won't be easy way path to migrate.
> Does that mean I need to keep syncing my Cygwin installation periodically?
> What is recommended period for upgrades?
Subscribe to cygwin-announce list, and any time security patches are made to any
package you have installed, or valuable updates to python or other packages you
depend on, download setup and upgrade everything.
If you explicitly install releases like python36, python37, and/or python38
rather than python3-..., you will also have to install corresponding packages
python3?-... as they become available, rather than waiting and getting all the
updated modules, when the the python3 default gets updated from python36 to
python37, and later to python38.
For python and other collections of modules, maintainers will not update the
default release for e.g. python3, from python36 to python37, until all Cygwin
supported modules will build and pass test runs cleanly, or modules need to be
dropped from Cygwin, because features used in new releases of the modules,
require support of libraries which won't work under Cygwin.
As Cygwin is a rolling release, package maintainers stay behind the bleeding
edge to avoid breakage, as they often use those packages for work, and they may
also support groups of users who do. If they are unsure of the reliability or
stability of a new release, they will make it available as a test release for
some time, before making that release current and upgradable by setup.
Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada
This email may be disturbing to some readers as it contains
too much technical detail. Reader discretion is advised.
Problem reports: http://cygwin.com/problems.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple