hello again;
sorry to follow-up on my own question, but i wanted to be able to use
this.
if i break the argument parsing regular expression as follows:
for arg in re.split(r'(?<!\\),', args):
arg = arg.replace(r'\,', ',')
m = re.match(r'\s*[a-zA-Z_]\w+~?=', arg)
if m:
kwargs[arg[:m.end()-1].lstrip()] = arg[m.end():]
else:
largs.append(arg)
then at least it does not error on the ~= in the query, but that just
raised more questions as to why the macro processor has been changed
in this fashion. is there any document which describes the end-user
effect and the intention behind this change?
...
On 2007-04-01, at 18:42 , james anderson wrote:
>
> hello;
>
> the above error occurs when one tries to use that macro form for a
> ticket query on a wiki page from a 0.11dev server.
> i have used it in the past with <= 0.10 servers and verified that it
> works in 0.10.4dev.
>
> TicketQuery(keywords=value, compact)
>
> succeeds, as does a conjunction, as in
>
> TicketQuery(status=closed&keywords~=value, compact)
>
> i note that the tickets/query.py definition for query processing has
> changed .10 -> .11, but the comments indicate that the older form
> should still work.
>
> apropos which comments: i trust you do not really intend to deprecate
> the old form and the comment was a poor choice of words.
>
> thank you,
> ...
>
>
> >
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Trac
Users" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/trac-users?hl=en
-~----------~----~----~----~------~----~------~--~---
