On Oct 16, 11:12 pm, Remy Blank <[EMAIL PROTECTED]> wrote:
> Christian Boos wrote:
> > I think it will be
> > simpler to use the reponame (mount point) as the key.
> > If the goal is simply to be able to change that mount point without
> > doing a whole resync, we could add a `trac-admin <env> remount old new"
> > command, which could do that in one go.
>
> After hitting "send" on my first message, I figured the two issues are
> actually orthogonal: currently, the reponame is used both as a unique
> key and as the mount point, but nothing prevents us from separating the
> two uses and adding a .mount option later. So yes, I went ahead and used
> the reponame as the key.

I'm not sure I get the importance of adding this abstraction? I
haven't been tracking the branch as closely as I should, but is it
really important? Changing the mount point would invalidate all links
and more, so it might as well invalidate everything and require a
resync? Please don't make it too complex for the rest of us... :-)

> >> and would also allow having a mount point with
> >> caps or the "." character, as requested at the bottom of
> >> MultipleRepositorySupport.
> > That's a detail, we can easily get that by splitting at the last "." seen.
>
> That will work for "." characters, but not for the case where mount
> points should have uppercase letters like "MyModule", as the keys are
> converted to lowercase by ConfigParser.

The ConfigParser does support case-sensitive option names, but not by
default:
from ConfigParser import ConfigParser
myconfig = ConfigParser()
myconfig.optionxform = str   # support case-sensitive option names
myconfig.options('trac')
==> [..... , 'MyOption', .....]


:::simon

https://www.coderesort.com


--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Trac 
Development" 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-dev?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to