On Friday 02 October 2009 19:23:52 Robert Kern wrote: > On Fri, Oct 2, 2009 at 08:45, Matti Airas <[email protected]> wrote: > > With all of this in mind, I believe it would be now a perfect time to > > begin planning any backwards-incompatible changes to PySide, as the > > Python 3 transition would be the perfect instant to incorporate them. So, > > start discussing those PSEP ideas! ;-) > > The Python team *very* much discourages libraries from using the > Python 3 transition in order to introduce backwards-incompatible > changes. If all of our libraries also change out from under us, it > makes transitioning to Python 3 too difficult. It will already be > fairly challenging to port from PyQt to PySide and Python 2 to Python > 3 separately. Please do not make it more difficult. >
IMO is better to add backwards-incompatible changes when the user already have to worry about some other backwards-incompatible changes than when the user don't need to worry about that (2.x series). So you can push all desired changes at once, because will be impossible to do this later. The Python developers just want to see everyone moving on to Python3, so they want to remove any barrier, but if they can put some sand-bags in the barrier, why negate the extension developers to do so? -- Hugo Parente Lima "Precisamos de mais gênios humildes no mundo, hoje somos poucos!" JID: [email protected]
signature.asc
Description: This is a digitally signed message part.
_______________________________________________ PySide mailing list [email protected] http://lists.openbossa.org/listinfo/pyside
