Bug 1656633

*** Bug 1656632 has been marked as a duplicate of this bug. ***

I found a little more info, and maybe this is supposed to be an upstream bug, maybe not, you will tell me I suppose : 

Following the report on an older opened bug on upstream github repo : https://github.com/weechat/weechat/issues/420

I found out that the linking info for the python plugin was way shorter than the one for the perl one for example :
$ ldd /usr/lib64/weechat/plugins/python.so                                        
        linux-vdso.so.1 (0x00007fff6ed9b000)
        libc.so.6 => /lib64/libc.so.6 (0x00007f4e6dc17000)
        /lib64/ld-linux-x86-64.so.2 (0x00007f4e6de4d000)
$ ldd /usr/lib64/weechat/plugins/perl.so                                          
        linux-vdso.so.1 (0x00007ffd1f119000)
        libperl.so.5.28 => /lib64/libperl.so.5.28 (0x00007f7de8559000)
        libc.so.6 => /lib64/libc.so.6 (0x00007f7de8393000)
        libpthread.so.0 => /lib64/libpthread.so.0 (0x00007f7de8371000)
        libdl.so.2 => /lib64/libdl.so.2 (0x00007f7de836b000)
        libm.so.6 => /lib64/libm.so.6 (0x00007f7de8226000)
        libcrypt.so.1 => /lib64/libcrypt.so.1 (0x00007f7de81eb000)
        /lib64/ld-linux-x86-64.so.2 (0x00007f7de88fb000)

Therefore, I tried, like in the github issue I mentioned, to use LD_PRELOAD to force the issue :

$ LD_PRELOAD=/lib64/libpython2.7.so weechat

And now the symbol that weechat/plugins/python.so struggles to find actually changes (message is in french below) :

23:21 ⚠ Erreur : impossible de charger l'extension "/usr/lib64/weechat/plugins/python.so" : /usr/lib64/weechat/plugins/python.so: undefined symbol: PyUnicode_AsUTF8String

So I suppose this is an issue of correctly setting link dependencies when compiling, just as mentioned on the github issue, but I don't really know how to fix it, and why I started just now having issues with this python extension (I use 2 python scripts since I started using weechat, so I know it worked before)

And now I've found out how to make them work again : 

$ LD_PRELOAD=/lib64/libpython3.7m.so.1.0 weechat

starts without issue. No idea if there's anything to change to avoid having to preload the library.

I updated the package on rawhide and I still have the issue on

weechat.x86_64  2.3-2.fc30  @rawhide

diff -up weechat-2.4/cmake/FindPython.cmake.orig weechat-2.4/cmake/FindPython.cmake
--- weechat-2.4/cmake/FindPython.cmake.orig	2019-02-22 17:58:30.307952375 +0100
+++ weechat-2.4/cmake/FindPython.cmake	2019-02-22 17:58:43.763103598 +0100
@@ -67,7 +67,7 @@ if(PYTHON_EXECUTABLE)
     )
   if(ENABLE_PYTHON3)
     find_library(PYTHON_LIBRARY
-      NAMES python3.7 python3.6 python3.5 python3.4 python3.3 python3.2 python3.1 python3.0 python3 python2.7 python2.6 python2.5 python
+      NAMES python3.7m python3.7 python3.6 python3.5 python3.4 python3.3 python3.2 python3.1 python3.0 python3 python2.7 python2.6 python2.5 python
       HINTS ${PYTHON_POSSIBLE_LIB_PATH}
       )
   else()

Fixes it for me.

Seeing this on F30 that is now in beta. Could we get an update with the fix please?

weechat-2.3-3.fc30.x86_64

Opened a PR that updates to 2.4.1 and includes the fix Michele provided: https://src.fedoraproject.org/rpms/weechat/pull-request/6

weechat-2.4-1.fc29 has been submitted as an update to Fedora 29. https://bodhi.fedoraproject.org/updates/FEDORA-2019-bb4f83f667

weechat-2.4-1.fc28 has been submitted as an update to Fedora 28. https://bodhi.fedoraproject.org/updates/FEDORA-2019-9dc1c8a671

weechat-2.4-1.fc30 has been submitted as an update to Fedora 30. https://bodhi.fedoraproject.org/updates/FEDORA-2019-582e7a757b

weechat-2.4-1.fc30 has been pushed to the Fedora 30 testing repository. If problems still persist, please make note of it in this bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2019-582e7a757b

weechat-2.4-1.fc28 has been pushed to the Fedora 28 testing repository. If problems still persist, please make note of it in this bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2019-9dc1c8a671

weechat-2.4-1.fc29 has been pushed to the Fedora 29 testing repository. If problems still persist, please make note of it in this bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2019-bb4f83f667

weechat-2.4-1.fc28 has been pushed to the Fedora 28 stable repository. If problems still persist, please make note of it in this bug report.

weechat-2.4-1.fc29 has been pushed to the Fedora 29 stable repository. If problems still persist, please make note of it in this bug report.

weechat-2.4-1.fc30 has been pushed to the Fedora 30 stable repository. If problems still persist, please make note of it in this bug report.

This bug appears to have been reported against 'rawhide' during the Fedora 31 development cycle.
Changing version to '31'.

This bug appears to have been reported against 'rawhide' during the Fedora 31 development cycle.
Changing version to 31.

This message is a reminder that Fedora 31 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora 31 on 2020-11-24.
It is Fedora's policy to close all bug reports from releases that are no longer
maintained. At that time this bug will be closed as EOL if it remains open with a
Fedora 'version' of '31'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 31 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.