Hi, I've figured out a better solution than changing PYTHON_TARGETS and then revbumping the packages to have users upgrade (which may happen before they change PYTHON_TARGETS). Instead, I'll revbump these few packages and remove Python 2 in new revisions.
The majority of users will get the py2-less versions on next @world upgrade, and the few that need renpy, old mongodb, old kodi... will stay at current revision. This involves some temporary duplication on version bumps but I don't think this will be major issue. In other changes, I've included recommended upgrade/cleanup instructions and a warning to add python:2.7 to @world if you need it for your projects. -- Best regards, Michał Górny Michał Górny (2): 2020-09-28-python-2-7-cleanup: add a new news item 2020-02-07-python-2-7-eol: remove superseded news item .../2020-02-07-python-2-7-eol.en.txt | 51 ---------------- .../2020-09-28-python-2-7-cleanup.en.txt | 58 +++++++++++++++++++ 2 files changed, 58 insertions(+), 51 deletions(-) delete mode 100644 2020-02-07-python-2-7-eol/2020-02-07-python-2-7-eol.en.txt create mode 100644 2020-09-28-python-2-7-cleanup/2020-09-28-python-2-7-cleanup.en.txt -- 2.28.0
