[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: svn commit: rev 3434 - trunk/tools/hook-scripts

From: Branko Čibej <brane_at_xbc.nu>
Date: 2002-10-22 19:30:33 CEST

Karl Fogel wrote:

>kfogel@tigris.org writes:
>
>
>>New Revision: 3434
>>Log:
>>* tools/hook-scripts/svnperms.py,
>> tools/hook-scripts/svnperms.conf.example: New access control script
>> and sample conf file from Gustavo Niemeyer <niemeyer@conectiva.com>.
>>
>>* tools/hook-scripts/README: Mention svnperms.py. Reorganize a bit.
>>
>>
>
>Gustavo, I put these in tools/hook-scripts now. If you'd like to just
>maintain them there, just send me a username/password pair (plaintext
>please) and I'll set you up for commit access on that area.
>
>Note that I commented out this line near the top of the script:
>
> from __future__ import generators
>
Yes, I was wondering about that, too. IIRC generators are slated to be a
Python 2.3 feature, and are __future__-proofed in 2.2. We require 2.0
for everythng else.

I don't know whether replacing the generator usage with 2.0 features is
worth the trouble; using them makes the script much more concise.

>because it caused this error for me in Python 2.1:
>
> $ ./svnperms.py
> File "./svnperms.py", line 2
> from __future__ import generators
> SyntaxError: future feature generators is not defined
>
>Not sure what's going on there; is my Python already too old? Then we
>probably want a minimum version check. Anyway, you can fix it in the
>tree...
>
>
Yes, your Python is too old.

BTW, Gustavo, why are you parsing the config explicitly, instead of just
using the ConfigParser module?

-- 
Brane Čibej   <brane_at_xbc.nu>   http://www.xbc.nu/brane/
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Tue Oct 22 19:31:20 2002

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.