On Sun, Sep 13, 2009 at 6:48 AM, Yuki KODAMA <[email protected]> wrote:
> On Sun, Sep 13, 2009 at 17:56, Adrian Buehlmann <[email protected]> wrote:
>> On 13.09.2009 08:14, Yuki KODAMA wrote:
>>> On Sun, Sep 13, 2009 at 14:08, Steve Borho <[email protected]> wrote:
>>>> I'm about to start work on the rename improvements for commit,
>>>> history, and datamine.
>>>>
>>>> To kick start this, I plan to reorganize the repository to give the
>>>> rename code a good workout.  The primary goal is to move the two
>>>> Python packages into a single, obviously named, tortoisehg package.
>>>> So
>>>>
>>>> hggtk -> tortoisehg/hgtk
>>>> thgutil -> tortoisehg/thgutil
>>>>
>> [snip]
>>>> Any votes?
>>
>> I trust Steve to do the right thing. Steve, please go ahead.
>>
>>> +1: * Renaming tortoisehg/thgutil to tortoisehg/util
>>>
>>> "thg" is abbrev of "torotoisehg". It's a bit redundant.
>>
>> What about current code like:
>>
>>  from mercurial util
>>  from thgutil import hglib
>>
>> How would this work if we use "util" instead of "thgutil"?
>
> No problem. The name "util" of Mercurial points "util.py",
> but TortoiseHg's "util" is just directory, not "util.py" file.
> So we can use like this:
>
> from mercurial import util
> from tortoisehg.util import i18n, paths
>
> If we choose "tortoisehg/thgutil":
>
> from tortoisehg.thgutil import i18n, paths

This is, indeed, what the code looks like right now.  I think I'll go
ahead and rename thgutil to util.  Still debating with myself whether
to drop the logview directory.

--
Steve

------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day 
trial. Simplify your report design, integration and deployment - and focus on 
what you do best, core application coding. Discover what's new with 
Crystal Reports now.  http://p.sf.net/sfu/bobj-july
_______________________________________________
Tortoisehg-discuss mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/tortoisehg-discuss

Reply via email to