You can use GDbus as a replacement for python-dbus
You can see how I have done it in the yumdaemon python api.
Same code is working unchanged in python 2 & 3
Tim
On Tue, Oct 22, 2013 at 2:22 PM, Daniel J Walsh <dwalsh@xxxxxxxxxx> wrote:
-----BEGIN PGP SIGNED MESSAGE-----On 10/17/2013 11:45 AM, Miloslav Trmač wrote:
Hash: SHA1
> On Thu, Oct 17, 2013 at 9:13 AM, Bohuslav Kabrda <bkabrda@xxxxxxxxxx>
> wrote:
>>> * The Change plan should be updated to take into account Dennis's
>>> Feedback * I suggeested that perhaps a better contingency plan would be
>>> to simply ship with some applications using python2 and others using
>>> python3.
>>>
>>
>> Personally I don't have problem with this, but: - Side tag is a good
>> contingency plan. If we have to revert for whatever reason, then without
>> sidetag we will have to rebuild everything with Python 2 again.
>
> Yes. In general it would be great to start frequently making disruptive
> changes on branches to not disrupt other people, and this is a very big
> change where at least having the option is very much warranted Mirek
>
Began working on porting all of the SELinux python code to python3. I plan on
shipping bindings for both 2 and 3, but tools are hung up on missing yum and
dbus python3 bindings.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.15 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
iEYEARECAAYFAlJmbgUACgkQrlYvE4MpobMUygCdFFfP2E4luT6+U1+y6sOdglWe
gK4AoMNhuRj8sB0ZuFvUD8nn3CZPDKqH
=4pTR
-----END PGP SIGNATURE-----
--
devel mailing list
devel@xxxxxxxxxxxxxxxxxxxxxxx
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
-- devel mailing list devel@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
