--user option

Vlad Skvortsov vss at 73rus.com
Mon Mar 5 12:10:47 PST 2007


Ivan Glushkov wrote:


[skipped]

>>>
>>> We should create some "synonym" for abstract "ditrack user" to use it
>>> in the filters. Without it we can't ensure our announcement.
>>> I suppose it can be $USER (as it actually is). Not in the meaning of
>>> environment variable, but in the meaning of "ditrack user".
>>>
>>
>> It's a separate issue and I was also thinking about addressing it. I 
>> propose to stick to the current syntax to refer to environment 
>> variables and come up with alternative notation for DITrack-provided 
>> values. We might, for example, use something like:
>>
>> my: Status=open,Owned-by=%DTUSER
>
> Great!
> We should allow users to use environment variables through '$'. And we
> could also address to DITrack variables with '%'.

Exactly. See below though.

> But if '%' already means that it's DITrack-provided value, why do you use
> prefix 'DT'. Why not simply '%USER':
> my: Status=open,Owned-by=%USER

That was just an example, I don't really care.

>
> Or may be to simplify parsing we should use both-side-percent-symbol:
> my: Status=open,Owned-by=%DTUSER%
> ?

I'm in favor of using standard library by all means, so I'd prefer to 
use "String Templates" for all that 
(http://docs.python.org/lib/node40.html).  To distinguish between 
environment and DITrack variables I suggest using 'DT:' prefix (see i#123).
>
> Vlad, will you open new issue on me about using DITrack-provided values?

I've reassigned i#123 to you.

-- 
Vlad Skvortsov, vss at 73rus.com, http://vss.73rus.com



More information about the Dev mailing list