Thomas Wouters wrote: > > On Wed, Jul 19, 2000 at 07:27:37PM +0000, Peter Schneider-Kamp wrote: > > > > How about putting them on sourceforge? > > python.sourceforge.net/peps/pep-0206.txt and friends > > +1 if we can do it automatically. +0 if it has to be done by whoever commits > new versions ;) I can do it (and keep up with the changes) for now. But in the long run this probably should be automated. I only see the password barrier: scp pep-*.txt nowonder@shell.sourceforge.net:/home/groups/python/htdocs/peps will make me enter my password/passphrase. How would one go about doing something like that? One "solution" I can think of is to checkout a copy of nondist/peps from the CVS to htdocs/peps. Then the peps could be held up to date by running cvs up in that directory once a day (or 4 times a day). But this would require some action of SF to add it to their cron, wouldn't it?! Peter -- Peter Schneider-Kamp ++47-7388-7331 Herman Krags veg 51-11 mailto:peter@schneider-kamp.de N-7050 Trondheim http://schneider-kamp.de
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4