Itamar Shtull-Trauring wrote: |The ChangeLog usually doesn't cover code that is unstable. In general, |*always* use the latest version of Twisted.
Well, that sounds nice; but it's kinda impractical in a lot of contexts. As I mentioned in an upthread comment, my web host at python-hosting.com has 1.0.3 installed. I've emailed Remi asking him to upgrade--and I suppose he will--but not everyone maintains their own installation/host, nor does everyone want to reinstall large libraries every time s/he writes a new script.
Moreover, for me in particular, I want to write some examples for articles. If I write something that works in 1.0.5, but breaks in 1.0.6 and past, that's bad for readers (and makes me look a little worse). And as things go, probably the next Twisted version will be out before my article current article is published. But the story is pretty much the same if I were to implement something for a client--I don't want my software breaking everytime the library changes.
I'm not really complaining about any of this. Publishers pay me money to make informed guesses about what software will be stable and what will change (among many other judgements). But it does make it challenging to write the sort of thing I write that covers Twisted. I'll probably wind up going a little light on woven because of this--which is a little bit too bad, since templating is a technology a lot of readers would be interested in.
On Fri, 30 May 2003 02:28:13 -0400 david mertz firstname.lastname@example.org wrote:
the same if I were to implement something for a client--I don't want my software breaking everytime the library changes.
We do have *backwards* compatability! the problem you have now is with using new features with old versions of the software, which is a totally different problem. Some unstable parts will break in the future - if you're unsure about specific code, ask us.
I doubt anything that works with current Woven will break in the future, given we have quite a few apps using it.
On Fri, 30 May 2003, david mertz email@example.com wrote:
Moreover, for me in particular, I want to write some examples for articles. If I write something that works in 1.0.5, but breaks in 1.0.6 and past, that's bad for readers (and makes me look a little worse).
But you missed what Itamar said: we treat backwards compatibility seriously. If you'll check the FAQ, we even have questions for upgrading scripts from before woven was called woven. Software doesn't break when Twisted upgrades. But if you try and run scripts from one version of Twisted on a *lower* one you're on your own.
On Friday, May 30, 2003, at 02:07 PM, Moshe Zadka wrote:
Software doesn't break when Twisted upgrades.
While I echo the general sentiment, I think it's a little overconfident to be making this claim unqualified. We _try_ to make sure that software doesn't break when Twisted upgrades, but we don't have a build farm for external applications, and we don't have any backwards-compatibility regression tests.