Well, you are welcome to use this one, but like I said I simply ran the
alien rpm->deb utility on the .rpm. Although this looks pretty close to
the old .deb and seems to work fine for me.
Rimon Barr wrote:
> I plead ignorance regarding .debs. I gave access to one of the people on
> this list for this explicit purpose. Hopefully a .deb will appear soon.
> If not, I'm certain that someone else will eventually pick up the ball.
> All the best,
> On Wed, 23 Feb 2005, Jonathan Taylor wrote:
>> Super. I changed the python wiki page.
>> For debian/ubuntu etc users it might be helpful to post a .deb . I just
>> ran alien on the .rpm and had no problems with the .deb it created.
>> Maybe it would be enough to point out on the web page that a .deb can be
>> easily created via fakeroot alien spyce-*.rpm
>> Cheers and good to hear from you.
>> Rimon Barr wrote:
>>> Hello Spyce users,
>>> After a long quiet period, Spyce v1.3.13 was released today. The release
>>> notes are pasted at the end of this email. It's a grab-bag of things,
>>> but mostly bug fixes reported by users, a few performance tweaks and
>>> nice-to-have point changes.
>>> There is isn't as much testing on this release as I would have liked,
>>> mostly due to lack of time. But, it should be fine. Please report any
>>> problems you find. Many of these changes have been sitting in the CVS
>>> for a while, and I know that numerous users have been using them.
>>> In reponse to a number of recent posts to this list:
>>> - It's good to read that I am still alive. In fact, that's one of the
>>> primary reasons I read this list. :)
>>> - I have been unusually quiet on this list of late, but I don't think
>>> that this is a problem. Spyce continues to work without me in the
>>> loop, and the community continues to grow. I'm happy to see this. I've
>>> been busy with graduating, and then with the transition thereafter. I
>>> will continue to attend to this project as time permits.
>>> - A number of users have expressed willingness to maintain Spyce and
>>> help develop it further. I welcome and encourage this. That's what
>>> open source development is all about. I will be adding some developers
>>> to the project shortly. I look forward to their contributions. If you
>>> have ideas, just speak up.
>>> - There was some debate as to whether the project is "alive". In my
>>> opinion, Spyce does not require frequent releases, for a number of
>>> reasons, and this is a plus.
>>> First, it is platform independent, primarily as a consequence of being
>>> pure Python. Effort has also been taken to make it work on multiple
>>> versions of Python, when it does not adversely affect performance.
>>> Consequently, what worked yesterday should continue to work in the
>>> future, within limits, even as distributions change, and other
>>> components continue to advance.
>>> Finally, Spyce is very modular, by design, and therefore tends to
>>> progress as a function of its sub-components. Most notably, Spyce
>>> leverages Python and all its wonderful libraries. I wouldn't call that
>>> being "feature complete", as has been suggested, but rather a lack of
>>> unnecessary duplication, and a minimalistic design. The lines of code
>>> in the main codebase, as of this release, are:
>>> Code Files Lines
>>> core *.py 5071
>>> modules modules/* 2101
>>> tags tags/* 394
>>> For what it does, Spyce is very compact. As an aside, this means that
>>> new developers can learn the codebase quickly.
>>> - That said, I think that there is a LOT of work that can still be done
>>> on Spyce to improve it. It is far from complete. The fact that it does
>>> not require frequent releases, does not mean that frequent releases
>>> are bad, especially in order to incorporate new features. Of course,
>>> backwards compatability is a strong incentive to rationalize and test
>>> any design before releasing it, but that should not prevent progress.
>>> I won't list all of my ideas for the sake brevity, but here are some
>>> examples of interests to me, should I ever find the time to pursue
>>> them. If any of these suits your fancy, feel free to run with it:
>>> - improve the tag library to subsume the functionality of JSP,
>>> Java Faces, and Jakarta Taglibs among others.
>>> - ability to define user tags on-the-fly, just like you define
>>> Python functions.
>>> - improvements to the automaton (state machine) module, and an
>>> entire infrastructure to support stateful applications, along with
>>> a rendering engine and a component library. There are many
>>> projects to glean ideas from. I particularly like the design of
>>> Tapestry (http://jakarta.apache.org/tapestry/), and I think that
>>> there can be significant advantages gained by losing the Java/XML
>>> combo and doing things in a more "Pythonic" way. Any takers?
>>> - Perhaps a good sub-project or a baby-step in this direction would
>>> be a module for form validation.
>>> - Building more examples, and examples that are more meaningful.
>>> Perhaps a sample website would be nice.
>>> - On a related note, one could build generic web applications in
>>> Spyce: bulletin boards, webmail, web logs (blogs), portals, wikis.
>>> - An interactive documentation site. Perhaps translating the
>>> documentation into multiple languages. One very good documentation
>>> site that we may wish to emulate is that of PHP. I think it's
>>> fantastic: http://www.php.net/docs.php. It's not that difficult:
>>> all their PHP sources are available.
>>> - Deal with multi-user issues, so that Spyce can be more easily
>>> hosted by ISPs.
>>> ... and many more. Most of these are already listed at:
>>> The change log for the current release is:
>>> improved performance (approx. 3x) of single-threaded print
>>> exceptions in non-default modules reported like errors in script code
>>> fix: mysession.spy: session depends on pool, so switched import order
>>> fix: faulty session handlers thrown out on error
>>> - takes care of annoying NameError: 'pool' not found
>>> fix: sys.path always returned to original state, even on error
>>> globals accessible via python modules
>>> - applied patch contributed by: Niko Matsakis
>>> iterable objects allowed within 'for' tag
>>> - modified patch submitted by: Stefan Behnel
>>> spyce lambdas can return values
>>> updated spyceLock.py to eliminate Python FutureWarning for large
>>> added include.spyceStr(), idea from Santtu Pajukanta
>>> fix: error module performs response.clearFilters
>>> - thanks to Colin Gillespie for reporting this
>>> turning on spyce.DEBUG_ERROR will also display when modules
>>> For now, that's my 2c. Happy Spyceing.
>>> All the best,
>> SF email is sponsored by - The IT Product Guide
>> Read honest & candid reviews on hundreds of IT Products from real users.
>> Discover which products truly live up to the hype. Start reading now.
>> Spyce-users mailing list
> SF email is sponsored by - The IT Product Guide
> Read honest & candid reviews on hundreds of IT Products from real users.
> Discover which products truly live up to the hype. Start reading now.
> Spyce-users mailing list