On Tuesday 07 October 2008, Sundance wrote: > Henrik Pauli wrote: > >> And we could have just as many Viper versions as we'd damn well > >> please within any given Python and Qt release timeframe -- we'd > >> simply import from Viper2, Viper3... rather than Viper. > > > > Hmmm, true that, but since Py2 and Py3 are completely different > > matters (as far as I understand), thus have completely separate module > > bases, it could be just Viper in both, without clashing whatsoever. > > Hi, > > Maybe I didn't express myself clearly, but in my thinking, 'Viper' > versions and Python versions would be orthogonal, so Viper2, Viper3... > would be referring to the respective versions of the bindings, NOT the > versions of Python. The whole /point/ would be to be independant of the > Python versioning scheme. :)
If you read it again, you'll see I wrote pretty much that; or at the very least a completely different issue :) _______________________________________________ PyQt mailing list PyQt@riverbankcomputing.com http://www.riverbankcomputing.com/mailman/listinfo/pyqt
