Re: Python bindings using cppyy (was: An update on Python bindings)
Luca Beltrame <[email protected]>
| Newsgroups | gmane.comp.kde.devel.core,gmane.comp.kde.devel.bindings,gmane.comp.kde.devel.frameworks |
|---|---|
| Organization | KDE e.V. |
| Message-ID | <[email protected]> |
Il giorno Thu, 2 Nov 2017 23:53:00 +0000 Shaheed Haque <[email protected]> ha scritto: Hello Shaheed, > Firstly, we have existence proofs in the form of PyQt and the PyKDE4 PyQt doesn't really fit the model. It's developed by one person, and with no source control access to anyone but the maintainer. PyKDE4 had serious problems with maintenance (stuff got broken for months, at times), although that was in pre CI times. > Also, I wonder how easy that will be given the need to keep source > compatibility? I've hardly done a comprehensive survey, but if the > Akonadi example is anything to go by, I don't think there is a short I would suggest to avoid anything that's not part of Frameworks for now. The policies for ABI and API compatibility make things easier. The rest can come later, once the finer issues have been dealt with. I'd rather have the bindings in the frameworks, to ensure that if something breaks, it can be fixed instead of bitrotting. -- Luca Beltrame - KDE Forums team GPG key ID: A29D259B
signature.asc
(application/pgp-signature, 488 B)
-----BEGIN PGP SIGNATURE----- iQEzBAEBCgAdFiEEkxcLGs5Ymg3lt6kxjfYx/QIdsMUFAln8CQcACgkQjfYx/QId sMUQ+QgAjA+2SAb3ShJtS9S3MydUQJvYKwYV0k4S4YJpneUIS9fJnDBynJo6RD5E 4j1V03UFdSeqUu4bcFLM7hehJ/t2jcJK8tJRh+XpC5AO1NfHjmoO7TwEIWjO9Iam 1yyOgkBjpBck+jJVgbJqLoSevrg6rvK3IYNRyVnPM+COO/sn56Ik75oMhWJ7F42r Maomy7mifGvl9Ow33K48hzEt3qHTGx9sLfaaHNEvNTERnukUh0Z9NHWDKNqPJCLC L8LG1/TEd13vrgBS3RDR25bn2SNnCzCnAo3BMABJF1sUDsjZyM4p3ihvzVquAVMP JSyUFKVVXBF41a2LMg0FZn6UfQvCcQ== =6WTo -----END PGP SIGNATURE-----