Community Packages

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#62348 - [weechat] Switch python to python 3

Attached to Project: Community Packages
Opened by Brett Cornwall (ainola) - Sunday, 14 April 2019, 18:56 GMT
Last edited by Eli Schwartz (eschwartz) - Wednesday, 24 July 2019, 17:18 GMT
Task Type Bug Report
Category Packages
Status Closed
Assigned To Christian Rebischke (Shibumi)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date 2019-04-14
Percent Complete 100%
Votes 3
Private No

Details

Now that we're starting to actively remove Python 2 support from the repositories, it would be nice to build Weechat against python 3 instead of python 2.
This task depends upon

Closed by  Eli Schwartz (eschwartz)
Wednesday, 24 July 2019, 17:18 GMT
Reason for closing:  Deferred
Additional comments about closing:  Upstream already has a schedule to switch to python3 by default, and we will switch at that time (as per the defaults in the build system).
Comment by Daniel M. Capella (polyzen) - Wednesday, 24 July 2019, 16:19 GMT
July 1st has passed: https://weechat.org/scripts/python3/
Comment by Eli Schwartz (eschwartz) - Wednesday, 24 July 2019, 17:17 GMT
Irrelevant. There is no new version of weechat, which could display the git master behavior of defaulting to python3. This will automatically occur as soon as weechat 2.6 is released.

Please don't abuse TU bugtracker privileges to reopen a bug that was already requested to be reopened for this exact reason, and rejected, without at least trying to address the justification for having declined to reopen it, weeks ago. No one here is unaware what the date is, and the weechat roadmap doesn't say anything about already existing stable releases.

Loading...