[PATCH 2 of 3] modulepolicy: create a module for the modulepolicy

[Pierre-Yves David]

On 03/09/2016 08:18 PM, timeless wrote:
> yuja asked me for it.
>
> I don't claim it's better.

What's yuya rational for this?

> On Wed, Mar 9, 2016 at 1:19 PM, Pierre-Yves David
> <pierre-yves.david at ens-lyon.org> wrote:
>>
>>
>> On 03/09/2016 04:19 PM, timeless wrote:
>>>
>>> # HG changeset patch
>>> # User timeless <timeless at mozdev.org>
>>> # Date 1457538421 0
>>> #      Wed Mar 09 15:47:01 2016 +0000
>>> # Node ID 71cb80801ec4e3b6aa519da48b4601c3c7a41615
>>> # Parent  f9363da1d708516fbf365d41c9075018b2ce020c
>>> modulepolicy: create a module for the modulepolicy
>>>
>>> Instead of rewriting __init__ to define the modulepolicy,
>>> write out a __modulepolicy__.py file like __version__.py
>>
>>
>> Why is this better?
>>
>> --
>> Pierre-Yves David
>>
>> _______________________________________________
>> Mercurial-devel mailing list
>> Mercurial-devel at mercurial-scm.org
>> https://www.mercurial-scm.org/mailman/listinfo/mercurial-devel
> _______________________________________________
> Mercurial-devel mailing list
> Mercurial-devel at mercurial-scm.org
> https://www.mercurial-scm.org/mailman/listinfo/mercurial-devel
>

-- 
Pierre-Yves David