pycs-devel — Python Community Server development/chat

Re: [PyCS-devel] CVS needs pycs_tokens.py

[Georg B. <gb...@mu...>]

Hi!

> Can you put pycs_tokens.py into the repository?  The current code
> there fails to install and run because pycsAdmin.py fails on importing
> pycs_tokens.

Ooops. Sorry, I thought I had. It's in CVS now.

> Also: I see that some files now expect to see pycs.css in the server
> root; to get this to go, I've added pycs.css into CVS, and changed the
> Makefile to install it into the www dir.

Ah, yes, that's better for new installations. I definitely will have to 
set up another community just so that I can throw it away and reinstall 
from scratch from time to time. Currently I am developing and debugging 
directly with muensterland.org :-)

Ok, I don't have any users to speak of, yet, so it's not that big a 
problem.

bye, Georg

Re: [PyCS-devel] Greetings All

[Georg B. <gb...@mu...>]

Hi!

> daemon like.  Right now that specifically includes incorporating 
> functionality from Optik

Hmm. Isn't that what getopt is for? Ok, I don't know "optik", it looks 
like getopt on dope, so it might be just the right tool for PyCS ;-)

> the list for review.  Next on the agenda will be creating a windows 
> service functionality for pycs.py, but as for that I'm still 
> researching.

You might want to look into Zope, they have a very nice simple tool 
(ZDaemon.py or something like that) for service integration that just 
can call any python server and stop it again. It's actually just a shim 
between the Windows service controller and the standard python daemon. 
The good thing is that you won't need to change anything with the python 
daemon, you just add the shim for Windows and that's it. Drop me a note 
at mailto:ba...@gw... when you want me to send you a stripped down 
version, I don't have any windows stuff back here at home, but we use 
this tool for other python daemons at work.

bye, Georg

[PyCS-devel] CVS needs pycs_tokens.py

[Phillip P. <pp...@my...>]

Georg,

Can you put pycs_tokens.py into the repository?  The current code
there fails to install and run because pycsAdmin.py fails on importing
pycs_tokens.

I've updated pycs.net -- creating a blank pycs_tokens.py got it to
start up OK.

Also: I see that some files now expect to see pycs.css in the server
root; to get this to go, I've added pycs.css into CVS, and changed the
Makefile to install it into the www dir.

Cheers,
Phil :)

[PyCS-devel] Greetings All

[Michael H. <Mic...@hd...>]

Phil and Georg--

Based on a suggestion from Phil, I joined the list, and I'll be moving 
any discussions to said list.

The things that I'm presently working on are related to making pycs 
more and more daemon like.  Right now that specifically includes 
incorporating functionality from Optik (http://optik.sourceforge.net) 
to allow for command line switches.  Right now these switches include:

pycs.py [--help,-h] [--version,-v] [--config=</path/to/pycs.conf>,-c 
</path/to/pycs.conf>] [--debug,-d]

The only thing which I will add a little extra data on is the 
--debug,-d flag, which starts the pycs process as a foreground process 
for debugging purposes.  I would expect that in the future this flag to 
take an integer defining a debug level that tunes the output 
appropriately.  This stuff is pretty close to being baked...  Once I'm 
happy with this stuff I'll post a patch to the list for review.  Next 
on the agenda will be creating a windows service functionality for 
pycs.py, but as for that I'm still researching.

However, all of this has to wait until the week of US Thanksgiving as I 
have vacation and work deadlines to attend to.

Regards,
name: Michael C. Hay
org: Hitachi Data Systems Corporation
businessUnit: Requirements and Architecture
title: Manager, Data Management and Security Architecture
work: 408-970-7404
mobile: 650-269-4203
url: http://www.hds.com
mail: mailto:mic...@hd...

Re: [PyCS-devel] New feature in CVS: shell tool for administrative commands - please comment on this

[Phillip P. <pp...@my...>]

Sounds interesting!

Sorry ... I'm in the middle of moving house right now, so don't have a
lot of time to experiment.  I like the idea though; it sounds very handy.

I'd like a way to make it so the midnight rollover can happen without
needing to use a crontab entry ... although that shouldn't be too hard
to retrofit.  Once PyCS has a built-in scheduler, we can get it to
call the rollover function at the right time without needing to break
anything else.

Thanks!
Phil.

On Wed, Nov 13, 2002 at 02:32:04PM +0100, Georg Bauer wrote:
> Hi!
> 
> I just checked in a new XML/RPC handler and a small tool that connects to
> this. It's a bit more complicated this time, so the description will be
> longer.
> 
> Files I created:
> 
> pycsAdmin.py: administrative functions that are available through XML/RPC
> pycsadm.py: simple tool that just uses the above interface
> pycs_tokens.py: helper functions for a challenge/response auth module
> 
> How does it work?
> 
> pycsAdmin connects to the pycsAdmin.* namespace in the XML/RPC interface.
> It gives out mostly two functions: "challenge" and "execute".
> 
> "challenge" just returns you a cryptographic challenge you have to use on
> calling other functions. This challenge is written in the filesystem to
> the RUNDIR of the PyCS, too. This function gets no parameters.
> 
> "execute" executes a command with parameters. It get's three parameters: a
> cryptographic token, the command name and a list of parameter values.
> 
> The token is constructed with the pycs_token.createToken function. It just
> takes the given challenge, creates an empty SHA1 context, and updates that
> with both the challenge and the password. The token is both the challenge
> and the hexdigest of the context (as a list).
> 
> The server now check wether it's own password using the given challenge
> gives the same response and check wether there is a remembered challenge
> of the given name. If there is a remembered challenge, it is deleted so
> that no other call can use this challenge.
> 
> Complicated? Yep, a bit. But it works. It gives the following nice results:
> 
> - the password is never sent over the line
> - challenges can't be sniffed, as they are one-time-only
> - challenges can't be predicted, as they are built from several aspects
> - since it uses XML/RPC, the client can run everywhere (even inside Radio)
> - since everything still goes through the server, functions can savely
> change data in Metakit
> - since the client stores it's password in a hidden and protected
> passwordlist, you can set the client up via crontab to do regular stuff
> - since you only can call defined functions, even if the password is
> compromised you won't open up your whole server, only the admin interface
> 
> It has the following drawbacks:
> 
> - the server needs to store the password in clear, so you have to protect
> it with unix rights (restrict the config to 700). The server checks wether
> the mode is 700, so this might not work on windows!
> 
> I just checked in everything and started to hack at additional functions
> that I need (for example the autodisable after inactivity will be coded
> using this tool, so I just can put the tool into the crontab of the pycs
> user, as will be the "shuffle hitstoday to hitsyesterday tool). Especially
> the problem with checking the rights of pycs.conf to be 700 might not work
> with non-unix systems, so somebody could check that with Windows and tell
> me - I only use Unix for servers, sorry. If the check doesn't work you can
> still use all the server provides, you just can't use pycsadm.py, that's
> all.
> 
> As allways, if you just ignore the stuff and don't change anything, PyCS
> will behave as before and you won't open up some holes, so it is safe to
> ignore this :-)

[PyCS-devel] Some more fun with pycsadm.py

[Georg B. <gb...@mu...>]

Hi!

Just to give you something to play with, I now checked in two more
functions for pycsAdmin.*:

list - gives a list of objects (currently users with filters)
shuffle - shuffles around data (currently only hits)

pycsadm.py list users - this gives you a list of all users from the shell
pycsadm.py list enabled
pycsadm.py list disabled

pycsadm.py shuffle hits - this shuffles hitstoday to hitsyesterday and
cleans out hitstoday.

there is an example crontab (file crontab.example) in the source
distribution so you can see how to setup the shuffle feature to run at 5
minutes after midnight every night. Today hits make much more sense when
they get cleaned out once every day ;-)

bye, Georg

[PyCS-devel] Additional info on pycsAdmin

[Georg B. <gb...@mu...>]

Hi!

One point I forgot: since it uses XML/RPC, one could write a GUI tool to
administer PyCS using for example Python/TK or other GUI tools. So this
might help in getting it up and running easier, especially if we pull more
functionality into the pycsAdmin namespace.

Functions currently return a dictionary with the following keys:

flError: a flag that tells you wether it was an error
message: a "Done!" message or the error message if it was an error
columns: a list of column names
table: a list of list of values (like a resultset from a database)

columns and table are optional, but if they occur, they occur together.
For example help has ['command', 'description'] in the columns value and
[['help','show ...'],...] as the table value.

As said, the interface might change, if others have better ideas how to do
it. The main idea with this stuff is to enable using standard OS
mechanisms to trigger administrative functionality in the server and to
allow the server to define what functionality is available. And it solves
the non-multiuser-ness of Metakit.

bye, Georg

[PyCS-devel] New feature in CVS: shell tool for administrative commands - please comment on this

[Georg B. <gb...@mu...>]

Hi!

I just checked in a new XML/RPC handler and a small tool that connects to
this. It's a bit more complicated this time, so the description will be
longer.

Files I created:

pycsAdmin.py: administrative functions that are available through XML/RPC
pycsadm.py: simple tool that just uses the above interface
pycs_tokens.py: helper functions for a challenge/response auth module

How does it work?

pycsAdmin connects to the pycsAdmin.* namespace in the XML/RPC interface.
It gives out mostly two functions: "challenge" and "execute".

"challenge" just returns you a cryptographic challenge you have to use on
calling other functions. This challenge is written in the filesystem to
the RUNDIR of the PyCS, too. This function gets no parameters.

"execute" executes a command with parameters. It get's three parameters: a
cryptographic token, the command name and a list of parameter values.

The token is constructed with the pycs_token.createToken function. It just
takes the given challenge, creates an empty SHA1 context, and updates that
with both the challenge and the password. The token is both the challenge
and the hexdigest of the context (as a list).

The server now check wether it's own password using the given challenge
gives the same response and check wether there is a remembered challenge
of the given name. If there is a remembered challenge, it is deleted so
that no other call can use this challenge.

Complicated? Yep, a bit. But it works. It gives the following nice results:

- the password is never sent over the line
- challenges can't be sniffed, as they are one-time-only
- challenges can't be predicted, as they are built from several aspects
- since it uses XML/RPC, the client can run everywhere (even inside Radio)
- since everything still goes through the server, functions can savely
change data in Metakit
- since the client stores it's password in a hidden and protected
passwordlist, you can set the client up via crontab to do regular stuff
- since you only can call defined functions, even if the password is
compromised you won't open up your whole server, only the admin interface

It has the following drawbacks:

- the server needs to store the password in clear, so you have to protect
it with unix rights (restrict the config to 700). The server checks wether
the mode is 700, so this might not work on windows!

I just checked in everything and started to hack at additional functions
that I need (for example the autodisable after inactivity will be coded
using this tool, so I just can put the tool into the crontab of the pycs
user, as will be the "shuffle hitstoday to hitsyesterday tool). Especially
the problem with checking the rights of pycs.conf to be 700 might not work
with non-unix systems, so somebody could check that with Windows and tell
me - I only use Unix for servers, sorry. If the check doesn't work you can
still use all the server provides, you just can't use pycsadm.py, that's
all.

As allways, if you just ignore the stuff and don't change anything, PyCS
will behave as before and you won't open up some holes, so it is safe to
ignore this :-)

Currently implemented commands:

help - gives a list of defined commands
enable - enables a user (user.disabled = 0)
disable - disables a user (user.disabled = 1)

More are planned, and will be announced on this list as other changes I
do. Documentation at pycs.net isn't updated yet, as this is some change
that might need more mulling over by others, so it's only in CVS to play
with. The interface might change if Phil (or somebody else on this list)
has objections against the design.

bye, Georg

[PyCS-devel] New feature in CVS: disabled users

[Georg B. <gb...@mu...>]

Hi!

Just checked in is a new feature for PyCs that adds a "disabled" property
to the user table (default 0, so nothing should break with current
systems) and adds a pycs_block_handler to block out URLs below the users
home folder.

This is implemented in the way that it matches the URL against
/users/[0-9]+, so it must run after the rewrite-handler, as that one
creates those URLs out of symbolic user handles and manila-style
hostnames.

This is the base for automatic disabling of users (due to long inactivity)
and administrative disabling (due to offensive content). As said, the flag
is default off, so nothing should happen. All automatic disabling will be
switchable with defaults like now (no automatic disabling).

I need this feature to have the ability to switch off users and to get rid
of "one-time-tryout" users. That's just something you are used to when
running a BBS and it makes much sense in that context. And as I want to
run PyCs as something like a "modern-style" BBS, it makes sense to have it
available there, too.

The "administrative disable" btw. is highly needed in Germany, as you are
required to take offensive or illegal content down immediately after
notification - if not, you might get in _very_ serious legal trouble.

Oh, and one for the "masses": the users.py now sorts the user attributes
alphabetically, so some attribute is always at the same place and not
jumping around randomly ;-)

bye, Georg

Re: [PyCS-devel] New feature in CVS

[Phillip P. <ph...@my...>]

Very cool!

Thanks Georg :-)

----- Original Message -----
From: "Georg Bauer" <gb...@mu...>
To: <pyc...@li...>
Sent: Tuesday, November 12, 2002 11:46 PM
Subject: [PyCS-devel] New feature in CVS


> A new feature was checked into CVS:
>
> modules/system/searches.py
>
> This module is much like referers.py, but it only shows search engines and
> pulls out the search term from the URL. Currently it is very crude and
> only supports google and yahoo and only simple searches (as those are the
> only two that are in my referrer list currently ;-) ), but new search
> engines and search types can be easily added into the module (look for the
> engines dictionary in the head of the module, you can add several regexps
> to a search engine if it has different ways of search links).
>
> The reason for this is a better way to see what people are looking for
> when hitting your pages, as that can maybe help with better designing
> content, or it might be just plain fun to look at :-)

[PyCS-devel] New feature in CVS

[Georg B. <gb...@mu...>]

Hi!

A new feature was checked into CVS:

modules/system/searches.py

This module is much like referers.py, but it only shows search engines and
pulls out the search term from the URL. Currently it is very crude and
only supports google and yahoo and only simple searches (as those are the
only two that are in my referrer list currently ;-) ), but new search
engines and search types can be easily added into the module (look for the
engines dictionary in the head of the module, you can add several regexps
to a search engine if it has different ways of search links).

The reason for this is a better way to see what people are looking for
when hitting your pages, as that can maybe help with better designing
content, or it might be just plain fun to look at :-)

bye, Georg

Re: [PyCS-devel] Reviving the list: It's been a while ...

[Robert B. <rba...@ma...>]

Welcome, Georg!

Thanks for lending Phil a hand!  I look forward to seeing what 
"develops". ;-)

Regards,

Robert Barksdale
http://www.pycs.net/archetypes
http://zopenx.net

On Monday, Nov 11, 2002, at 05:33 US/Central, Phillip Pearson wrote:

> Hi all,
>
> It's been a while since this list saw the light of day, but with the 
> recent
> activity around PyCS I think it's a good time to bring it back into 
> action.
>
> I've set Georg Bauer up with CVS developer access on SourceForge, so 
> it will
> now be the two of us maintaining stuff rather than just me.  Because of
> this, it would make sense for PyCS-related conversations to happen 
> here on
> the list rather than in private e-mail with me.
>
> Besides, I'm sure more people are interested in hearing about what's 
> going
> on, so let's bring this out into the open ;-)
>
> A brief intro: Georg is a programmer and sysadmin from Germany who is
> running his own PyCS over there at http://muensterland.org/ ... he has 
> his
> own blog at http://hugo.muensterland.org/ and apparently there is 
> another
> user there already.  He's sent in heaps of patches to the code -- 
> basically
> picking up all the things I never got around to doing -- and is making 
> PyCS
> into a much better application in the process.
>
> Hopefully we can keep on building up the PyCS community!
>
> Cheers,
> Phil
> http://www.myelin.co.nz/
> http://www.pycs.net/devlog/
> http://blogs.salon.com/0000002/
>
>
>
>
> -------------------------------------------------------
> This sf.net email is sponsored by:ThinkGeek
> Welcome to geek heaven.
> http://thinkgeek.com/sf
> _______________________________________________
> PyCS-devel mailing list
> PyC...@li...
> https://lists.sourceforge.net/lists/listinfo/pycs-devel

[PyCS-devel] Re: Small Bug in pycs_settings.py

[Georg B. <gb...@mu...>]

Hi!


> http://www.soapware.org/xmlStorageSystem has some useful bits in it ...

Yep, just stumbled across that one on my search for documentation for
rssPleaseNotify. Helpfull page.

> the signon/signoff thing is there.  That's not really relevant any more
> though ... it was only important when Radio was a music sharing app!

Hmm. It was? Funny. Never watched it much in the older times, as I don't
like the UserTalk language that much. I still don't like it that much, but
nowadays most is already done so I don't need to touch it.

> BTW, I see that RCS returns xmlrpclib.DateTime objects for all the date
> variables.  There's something we'll have to look at fixing up sometime

Oh. Yeah, I noticed that Radio gives out localized date strings, so we
should change that. Maybe that can be included when changing everything to
epoch storage instead of string storage for dates and times.

Maybe we should collect such stuff in the sourceforge tasks or
bugtracking, so we don't lose track of them?

Oh, I am replying to the list, so that we transfer our current threads
there :-)

bye, Georg

[PyCS-devel] Reviving the list: It's been a while ...

[Phillip P. <ph...@my...>]

Hi all,

It's been a while since this list saw the light of day, but with the recent
activity around PyCS I think it's a good time to bring it back into action.

I've set Georg Bauer up with CVS developer access on SourceForge, so it will
now be the two of us maintaining stuff rather than just me.  Because of
this, it would make sense for PyCS-related conversations to happen here on
the list rather than in private e-mail with me.

Besides, I'm sure more people are interested in hearing about what's going
on, so let's bring this out into the open ;-)

A brief intro: Georg is a programmer and sysadmin from Germany who is
running his own PyCS over there at http://muensterland.org/ ... he has his
own blog at http://hugo.muensterland.org/ and apparently there is another
user there already.  He's sent in heaps of patches to the code -- basically
picking up all the things I never got around to doing -- and is making PyCS
into a much better application in the process.

Hopefully we can keep on building up the PyCS community!

Cheers,
Phil
http://www.myelin.co.nz/
http://www.pycs.net/devlog/
http://blogs.salon.com/0000002/

[PyCS-devel] Just a hello from the "new" guy

[Georg B. <gb...@mu...>]

Hi (or "Moin" as we say around here)!

Just want to say hello to all at the list and tell something about me. I
am build-date 1966-12-25, located in Directory Germany, Subdirectory
Münster, work as a programmer in a software company and it's subsidiaries
since 1986. First big mainframe shop, later on in a subsidiary of that
company, hacking away at ERP solutions and nowadays internet solutions. I
am the lead developer for Internet and communication solutions and the
main systems architect in our company. I do the internet production, too
(setting up systems, keep-them-running and make-them-break-in-funny-ways
sometimes, too). Part of this work is running one of the biggest
Zope-clusters in Germany ...

Private hobbies are maintaining an old and ugly BBS based on an old DOS
software and modem connections (I even once wrote a mail/news gateway
software for that beast, nowadays it's more of the
keep-running-and-put-up-bypasses stuff), running my own private internet
provider (since 1993 up and running, nice little system, provides dialin,
news, mail, web and funny stuff, around 45 users), photography
(http://leicaesk.de/ and http://hugo.f-2.org/ if anybody cares) and
hacking up weird programs and software.

PyCs is an option I was investigating to build something with internet
software that's more in the philosophy of a BBS - users login and can
start right ahead, the admin mostly does keep-the-system-running and
hit-lusers-over-the-head stuff. Just something that can be left alone
running happily for years (as does my BBS). PyCs looks like it might be a
very valuable option for this.

Another thing I am currently investigating is using PyCs for our company
to provide some customer groups easy access to webhosting. Of course,
regardless of wether I use the stuff personal or for the company, I will
make my changes available in the PyCs style and under PyCs license
options. It's just that I get paid for some of the stuff I choose to do
;-)

My personal blogs are at http://hugo.muensterland.org/, my PyCs
installation at http://muensterland.org/ and my personal
sysadmin-rant-blog at http://hugo-.livejournal.com/ (one has to let off
steam from time to time).

bye, Georg

[PyCS-devel] Everything going again

[Phillip P. <pp...@my...>]

Right ... all of pycs.net should be working again.  I've got the updates page functional once more:

	http://www.pycs.net/system/weblogUpdates.py

All this is in SourceForge CVS now.

Cheers,
Phil :)

[PyCS-devel] Wiki moved

[Phillip P. <pp...@my...>]

Hi,

I just renamed the PycsWiki to CommunityServerWiki and moved it here:

	http://www.myelin.co.nz/cgi-bin/wcswiki.pl

The rationale here is that I want it to be a wiki about *all* community servers, not just PyCS.  There's plenty to discuss, and I want to be able to involve people like Charles Miller and Dave Bryson (authors of java community servers) as well, and talk about general things like xmlStorageSystem.

Note that the RSS feed has also moved, so if you are subscribed, you'll want to unsubscribe and resubscribe to the link from the front page.

Cheers,
Phil :)

[PyCS-devel] pycs database crash

[Phillip P. <pp...@my...>]

Hey guys,

I've had a bit of a disaster on pycs.net; the main database has become corrupted.  That means weblogs are visible on pycs.net, but comments don't work and nobody can upstream or use any of the dynamic functions.

I'm pretty busy right now so if anyone wants to help me debug my DB scripts, please check out pycs from CVS:

        cvs -d:pserver:ano...@cv...:/cvsroot/pycs login

        cvs -z3 -d:pserver:ano...@cv...:/cvsroot/pycs co pycs

and take a look at rescue_data.py and rescue_return_data.py.  They're almost working; rescue_data.py will dump your database out as Python code (to regenerate it) and rescue_return_data.py will *almost* turn a dumped database back into a real one.  The comments aren't coming out right at the moment.  I'll finish debugging that tonight, and hopefully get pycs.net going once more.

Also, for the future, check out mymetakit/mymetakit.py.  It's a Metakit-like wrapper for MySQL.  So far it's not very far along: it parses MK table definitions, I think, but doesn't do any DB stuff.  Anyone interested in DB abstraction please take a look at this.

Also, I've started a Wiki.  Nothing much there yet.  Dean might be interested in this ;)

	http://www.myelin.co.nz/cgi-bin/pycswiki.pl

Cheers,
Phil :)

[PyCS-devel] A few notes on what's been going on

[Phillip P. <ph...@my...>]

Hi all,

I've been making a few smallish changes to the PyCS code and pycs.net over
the last while.  There's been no traffic on this mailing list for ages, so
here's a note to summarise what's been happening.

- Individual referrer pages

Now everyone has a referrer page for their blog (feature req from Rogers).
For example:

    http://www.pycs.net/workbench/referrers.html

Link to that rather than http://www.pycs.net/referrers.html if you want to
put a referrer page in your blogroll.  It's a bit more relevant ;)

- No e-mail addresses

Comments don't show e-mail addresses now (feature req from Robert).  I may
hack up the mail-blog-author page (/system/mailto.py) to let you mail
comment writers as well.  Not sure yet.

-

That's about it, I think.  Minor presentation changes as well.  I've moved
one of my blogs (/devlog) over from Radio to bzero (www.myelin.co.nz/bzero),
so I can update it when I'm away from home.  Added some redirects for that
(documented on pycs.net/devlog, I think).

How's everyone else going?  We have had a few new users - seeing lots of
posting on pycs.net/sqr (Dean Goodmanson) and a bit on pycs.net/zia (Doug
Landauer, who has also been testing out bzero for me - thanks!).  Gillian
Kerr of realworldsystems.net dropped in on pycs.net/gkerr for a few days,
but seems to have disappeared.

Any things people would like to see?

I'm planning on getting the code to support running under CGI so I can shift
pycs.net off onto, say, the host that's doing myelin.co.nz for me, which
will hugely improve its availability.  It's been bad for the last few weeks
due to hardware failure and the ecosystem (www.myelin.co.nz/ecosystem)
crawler sucking up all the bandwidth.  If anyone wants to help out there (it
overlaps a bit with what Scott was originally planning on doing), please get
in touch.

Cheers,
Phil :)

[PyCS-devel] Welcome to Dean Goodmanson

[Phillip P. <ph...@my...>]

This message didn't come through on the old mailing list, so here's the
news: we have a new blogger on PyCS!  Welcome to Dean, editor of 'Square
Rutabega' (http://www.pycs.net/sqr/) ...

----- Original Message -----
From: "Dean Goodmanson" <goo...@ya...>
To: <pyc...@my...>
Sent: Wednesday, August 28, 2002 5:31 PM
Subject: subscribe pycs


> No specific plans.  Figuring out where to get the
> source before I crashed, noticed the mailing list &
> request to post development plans.
>
> I've coded small non-Gui app's in Python, and develop
> in a C/C++/C# shop for specialized client/server
> information system products.  Spent some pilot time in
> Java.   I thrive on collaboration and spent the last
> year's hobby time in the edges of the world of Python
> & Zope, with a recurring interest in collaboration
> tools from wikis (ZWiki primarily) to Weblogs and
> Groove.  I'm a windows guy out of convenience not
> zealotry, with a fascination for OS X and admiration
> for the unix cli.
>
> - Dean
> http://pycs.net/sqr

[PyCS-devel] Python Community Server mailing list moved to SourceForge

[Phillip P. <pp...@my...>]

Hi guys,

With any luck, you will have just received a message from SourceForge to
welcome you to the pycs-devel list.  This is because I have moved everyone
onto that after realising that the old list wasn't actually going any more
(due to a disaster with the myelin.co.nz domain a few weeks back).

As such, from now you should post to pyc...@li... rather
than py...@my... (which now sends directly to me).

This will mean we'll have an archive of posts on the web, as well as
hopefully a more responsive list.

Cheers,
Phil :)

[PyCS-devel] Testing

[Phillip P. <ph...@my...>]

I think we lost a list message a minute ago; this is a test to make sure
list messages go through.