Created attachment 1086482 [details] the reproducer sources Description of problem: If I have a union type in my GObject-based code and try to use it from python 3, the right value doesn't get to the "C side". However, this works just fine with python 2. Running the attached reproducer I get this: $ GI_TYPELIB_PATH=. LD_LIBRARY_PATH=. python reproducer.py got unit with int value: 1 got unit with int value: 2 got unit with int value: 3 $ GI_TYPELIB_PATH=. LD_LIBRARY_PATH=. python3 reproducer.py got unit with int value: 1 got unit with int value: 1 got unit with int value: 1 How reproducible: 100% Steps to Reproduce: 1. unpack the attached reproducer 2. run rebuild_test_data.sh 3. run $ GI_TYPELIB_PATH=. LD_LIBRARY_PATH=. python reproducer.py 4. run $ GI_TYPELIB_PATH=. LD_LIBRARY_PATH=. python3 reproducer.py Actual results: different behaviour for python 2 (correct) and python 3 (wrong) Expected results: the same (correct) behaviour in python 3 as in python 2 Additional info: this blocks python-blivet [1] from starting to use the new libbytesize library [2] [1] https://github.com/rhinstaller/blivet [2] https://github.com/rhinstaller/libbytesize
One more piece of info -- this seems to be an issue in all F21-Rawhide.
Anything more I could do to help things move on here? It's really a big issue blocking us from using new, better code.
This package has changed ownership in the Fedora Package Database. Reassigning to the new owner of this component.
This message is a reminder that Fedora 23 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 23. 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 '23'. 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 23 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.
Still the same in F24.
This message is a reminder that Fedora 24 is nearing its end of life. Approximately 2 (two) weeks from now Fedora will stop maintaining and issuing updates for Fedora 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 '24'. 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 24 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.
Fedora 24 changed to end-of-life (EOL) status on 2017-08-08. Fedora 24 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.