Shooting from the hip answer: Python 2.5 requires 'from __future__
import as_statement' or some such to make this work. I have not
researched this, and others are probably better qualified to answer it.
Though I'm not curious: why is this script using 2.5-isms? Shouldn't
we aim for 2.4 compat? (Note that in a few weeks, it will be moot,
since this script will break horribly against 1.7-era working copies.)
-Hyrum
On Apr 14, 2009, at 9:29 PM, Edmund Wong wrote:
> Hi,
>
> I'm currently using Python 2.5.2 (no new packages for slackware
> yet) and have the latest trunk revision, which when compiled
> gives me 1.7.0. (Compiled from the dev trunk + installed
> at /usr/local.)
>
> Under the aforementioned condition, change-svn-wc-format.py
> is broken because of the 'as' syntax with the except syntax.
>
> File "tools/client-side/change-svn-wc-format.py", line 93
> except UnrecognizedWCFormatException as e:
> ^
> SyntaxError: invalid syntax
>
> I don't understand this since by the v2.5 "what's new" at
> the Python.org site, the "as" syntax should be
> available, or did I misunderstand by 'available' it isn't
> available until a much later release in the v2.5 tree?
>
> Anyway, let us assume that I patched the python script to
> use the comma instead of the 'as' keyword. I run it with
> "1.5" as the version. It chokes because of a missing
> folder. So I give up and log in as root and do a 'svn
> cleanup' and 'svn update'. Nope. 'svn update' tells
> me to run 'svn cleanup'. The same issue that cropped
> up before. Up to now, I get the feeling I might have screwed
> up my dev_tree so I rm -rf * the whole thing so I can
> svn co http://svn.collab.net/repos/svn/trunk again.
>
> Unfortunately, this no longer works.
>
> svn co http://svn.collab.net/repos/svn/trunk
>
> produces the following error:
>
> svn: Unrecognized URL scheme for 'http://svn.collab.net/repos/svn/trunk'
>
> Now I can't check out anything using the built binaries from
> the trunk. (I hope I'm making sense here. I'm a little
> under the weather so my thought processes are little hindered.)
>
> At this point, the only thing I can do is download the 1.6.1
> source and reinstall from that to get the latest trunk.
>
> Is what I experienced a bug or did I fubar something that
> I shouldn't have?
>
> Any clarifications appreciated.
>
> Edmund
>
> ------------------------------------------------------
> http://subversion.tigris.org/ds/viewMessage.do?dsForumId=462&dsMessageId=1719873
------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=462&dsMessageId=1720548
Received on 2009-04-15 05:24:15 CEST