I've started pulling out these methods. One potential pain point is the old fps limiting functions from the clock module. There are a few references to this in other parts of the code base, but It's a good time to clean that up. -Ben
On Monday, December 4, 2017 at 1:11:21 PM UTC+9, Benjamin Moran wrote: > > Hi guys, > > This is a heads-up for everyone, especially for projects that are making > use of pyglet under the hood. In an effort to clean up the codebase, I'm > planning on removing most of the long deprecated methods and attributes > from pyglet. Most of these have been deprecated for a few releases (a year > or more), so hopefully this won't cause too much inconvenience. If anyone > has any specific use case for deprecated methods, please share them so that > we can understand your need. > > There are a few deprecated methods/attributes in each module, so I'll try > to reply here with a list of what will be removed and the new way to do it. > For example, the *sprite.set_position(x, y)* method has been replaced > with a position attribute: > *sprite.position = x, y* > The upcoming 1.4 and 1.5 releases should hopefully be nice stable releases > with minimal cruft. > -Ben > > -- 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.
