On 22/01/09 22:18, Neil McGovern wrote: > On Wed, Jan 21, 2009 at 10:33:55AM +0000, Andrew Price wrote: >> I realise there are restrictions on unfreezing packages where there are >> substantial upstream changes. However, the Twitter API has changed >> substantially since twyt 0.8.5 was released and has effectively >> obsoleted 0.8.5. >> > > Given that the API changed once, what's the chance of it happening again > during the lenny cycle? This package may be better suited to volotile or > something. > > Thoughts?
The Twitter API has been fairly stable over recent months. Although, it being closed and unversioned means that I have no way of knowing the chances of it changing significantly in the future. I have a feeling it will change during Lenny's released lifetime, though. I wonder if the python-twitter package has a similar problem to python-twyt? What is its strategy for staying compatible during Lenny's lifetime? (CCing the maintainer.) -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
