On Friday 19 July 2002 18:42, Glyph Lefkowitz wrote:

I know about this bug and I have a fix for it, although it's heavily hacked up because I was working around MacOS X kernel bugs related to WebDAV at the time (long story...)

You have webdav support in twisted too? I'm looking at the source (I've got 0.19 'final') and I don't see webdav. Where is it? btw. out of curiosity, a python programmer and enthusiast is a "pythonista", a zope enthusiast is a "zopista"...what's a twisted enthusiast? "twista"? -- Regards, Mukhsein Johari

On Fri, 19 Jul 2002 08:16:48 -0500, Chris Armstrong wrote:

...

[snip "what do we call people who like twisted?"] twisted.minion. :-)

This may have more to do with the fact that I'm gathering an eccentric cult of personality almost as fast as Twisted is acquiring new enthusiasts. Not that understanding Twisted *requires* a fanatic, dogged analyisis of my personal life... but it helps. -- | <`'> | Glyph Lefkowitz: Traveling Sorcerer | | < _/ > | Lead Developer, the Twisted project | | < ___/ > | http://www.twistedmatrix.com |

Glyph Lefkowitz wrote:

The most frequently applied term I've heard is "twister". I'd sure like to have occasion to need a term which refers to someone who is a Twisted enthusiast who isn't directly on the development team ;-).

How about "twistor" (resonates with the Twistors theory (physics) of Roger Penrose et al. :^) or "twisties"? (The "-ies" carries some of the cult-y flavor ... :^) So far, I've only done some simple experiments with twisted web and twisted enterprise, but even just from that and reading the docs, I can already see that twisted rocks! IMO it's by far the most advanced, most flexible, and best architected application framework in the Python world (which is the only language I would consider using for our application -- which BTW has nothing to do with twistors ... ;^). Thanks for the recently-added tutorial on Twisted Plugins; very cool! Need more ... (see the following ... :^) Context: the application we're developing is a "collaborative engineering environment", to include a repository, data transformation engine, multiprotocol communications hub, set of api's, and a gui client for browsing data and integrating desktop tools. Not all that different from a multi-player game, so twisted fits the paradigm to a tee -- as soon as I read the ipc10paper, I knew that if twisted was half as good as it sounded on paper, it could provide most if not all of the infrastructure we need right out of the box. Twisted has allowed me to consider implementing some advanced features sooner that I had anticipated, like replicating the communications hub within the thick gui client (a wxPython app with a ZODB local object cache), so that for a power user, the client could be configured as essentially a peer to the server nodes, but also support very simple interfaces (web browser-based or very thin clients) for users with simple perspectives. We have a prototype client, but haven't even begun to integrate twisted into it yet -- I'll ask questions about that later, like integrating the twisted event loop with wxPython's, which could be really nice. I had already selected PostgreSQL for the repository database, so twisted.enterprise is perfect, and trying out the example gave me the impression that it will be quite easy to work with. One thing I need to implement quickly is efficient support for "perspectives" (views with role-based access), so I'd like to get a little more documentation or somewhat better examples for how that is done with twisted. I would love to have an example that would illustrate something like the following: * Each user is assigned one or more roles. Each role will carry some set of permissions relative to objects and functions in the system. As I understand cred, a user is subclassed from Perspective, which maps to a "user-with-roles", I think. My initial idea is to have a "mask" assigned to each object that needs view-sensitivity, and whether that object is accessible and how is determined by comparing the user's (Perspective's) role mask to the masks of the objects that would be operated on by the user's request. Is this an appropriate concept to map to the twisted framework (from what I've read, it would involve cred and Perspective Broker)? And if so, how? Or if not, what would be the correct approach? * Speaking in terms of the role thing a bit further, some roles would be standardized, with pre-defined permissions like "read-only permission for all projects and create/mod permission for object type X on project Z." But we also need to enable certain admin or project leader roles to create customized roles for their projects, etc. How does this map? * I'd like to maintain the state of each user-with-roles in the PostgreSQL repository (syncing as necessary across thick clients and replicated servers, as was suggested on the list recently), and use hashed passwords over SSL. I'm sure from what I've read that cred either supports this or will soon, but I'd like to get more info on how to implement it. Gotta go now ... will send more questions soon. Thanks again for a truly awesome piece of work! Cheers, -- Steve. Stephen C. Waterbury http://misspiggy.gsfc.nasa.gov/people/waterbug.html

On Fri, Jul 19, 2002 at 03:53:43PM -0400, Levi wrote:

On Fri, Jul 19, 2002 at 08:18:01PM +0800, Mukhsein Johari wrote:

...

a python programmer and enthusiast is a "pythonista", a zope enthusiast is a "zopista"...what's a twisted enthusiast? "twista"?

"Twista" is fun in that it can be claimed to be derived from either: 1) A not too unusual pronouciation of "Twister". A twister, being litealy one-who-twists, is one of the people that "twist" python to produce "Twisted Python".

Being the semi-official "Twista"-who-corrects-usage-of-the-old-Twisted-name, I must inform you that Twisted is no longe "Twisted Python", but simply "Twisted". Thank you, and have a nice day.

On Tue, Jul 23, 2002 at 09:17:42AM +0100, Andrew Stribblehill wrote:

Quoting Christopher Armstrong (2002-07-19 09:11:36 BST):

...

Being the semi-official "Twista"-who-corrects-usage-of-the-old-Twisted-name, I must inform you that Twisted is no longe "Twisted Python", but simply "Twisted".

...and to reflect that, the Debian package has been renamed from 'twisted' to 'python-twisted-*' :)

That's policy for Python libraries in Debian. :P

tis 2002-07-23 klockan 15.48 skrev Glyph Lefkowitz:

On Tue, 23 Jul 2002 07:07:14 -0500, Chris Armstrong wrote:

...

On Tue, Jul 23, 2002 at 09:17:42AM +0100, Andrew Stribblehill wrote:

...

...and to reflect that, the Debian package has been renamed from 'twisted' to 'python-twisted-*' :)

That's policy for Python libraries in Debian. :P

Nevertheless, Zope is "zope".

First of all, I'm pretty sure it's not official policy yet. Second, it's much more important to do this for libraries that you do "import foo" on, than a big application written in Python that you happen to use. For an application, it doesn't matter to you if it uses python2.1 or python2.2 as long as it works. The pythonX-foo naming scheme comes from a need to have libraries for several versions of python. Martin -- Martin Sjögren martin@strakt.com ICQ : 41245059 Phone: +46 (0)31 7710870 Cell: +46 (0)739 169191 GPG key: http://www.strakt.com/~martin/gpg.html