Hi, The refactor will go into 1.3.x only. We can see if we can do a compatibility release in 1.2.x that supports both old and new, to give a transition path. Currently I do not know when 1.3 will hit pypi. It will probably take a couple of months still.
Rob On 2 April 2016 at 16:44, claudio canepa <[email protected]> wrote: > Hello, on behalf of cocos library I want to ask > > 1. Will the @property refactor in pyglet default keep out of the 1.2.x > releases ? > 2. Can we have a ballpark date when that refactor will land in a release > to pypi ? > > This is so in cocos library we can plan when to switch pyglet supported > version > > thanks > > -- > You received this message because you are subscribed to the Google Groups > "pyglet-users" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To post to this group, send email to [email protected]. > Visit this group at https://groups.google.com/group/pyglet-users. > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "pyglet-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/pyglet-users. For more options, visit https://groups.google.com/d/optout.
