PyOpenGL 3, API changes in general
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi,
in followup to a bug from last year, I asked Jamie Wilkinson if he would let the
PyOpenGL package be maintained by the DPMT. He agreed, and I'm going to prepare
a package of PyOpenGL 3 for experimental in the coming weeks.
PyOpenGL 3 is not *completely* API-compatible with the 2.x series, notably error
types have changed. While this might not be a major problem, I'm still wondering
if there should be a general rule how to handle API breakages in Python
modules/libraries. We (the PyQt maintainers) got bitten by that majorly at least
one time, and the solution was to let PyQt3 conflict with all the old packages
that used it. This solution is possible if there are only a handful of packages,
but if the number grows this might not be feasible. The easiest solution would
be to let Python packages that are prone to such problem provide a special
package which other packages can then depend on. Versioned provides would be a
plus, but are they going to be implemented anytime?
Back to the original question, should PyOpenGL 3 become python-opengl3 or stay
python-opengl? List of (known) incompatibilities is at [1].
best,
Torsten
[1] http://pyopengl.sourceforge.net/ctypes/using.html
- --
Torsten Marek <shlomme@gmx.net>
ID: A244C858 -- FP: 1902 0002 5DFC 856B F146 894C 7CC5 451E A244 C858
Keyserver: subkeys.pgp.net
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFF5Ko2fMVFHqJEyFgRAmlUAJ96ZsV0XMJVljNo4vOd58O+AyBtEgCcD6nR
IcGOgIcH0kAptB9hbOq2LK4=
=WaTW
-----END PGP SIGNATURE-----
Reply to: