On 11.05.2014 13:18, Kenneth Loafman wrote:
> We'll get this in for now, then discuss how best to simplify urlparse
> handling. I'm not convinced, yet, that removal of our urlparse module was
> needed. Having that in place guaranteed more stability, like pexpect. But
> then we get into the downstream packagers that remove anything that might
> be a duplicate, so it's all tradeoffs.
>
> For now, it fixes the problem. We can always back it out.
>
>
>
> On Sun, May 11, 2014 at 6:06 AM, edso <email address hidden> wrote:
>
>> Ken: what about the compatibility suggestion you agreed upon? ..ede
>> --
>> https://code.launchpad.net/~mterry/duplicity/py2.6.0/+merge/219113
>> You are subscribed to branch lp:duplicity.
>>
>
fair enough :) ..ede
On 11.05.2014 13:18, Kenneth Loafman wrote: /code.launchpad .net/~mterry/ duplicity/ py2.6.0/ +merge/ 219113
> We'll get this in for now, then discuss how best to simplify urlparse
> handling. I'm not convinced, yet, that removal of our urlparse module was
> needed. Having that in place guaranteed more stability, like pexpect. But
> then we get into the downstream packagers that remove anything that might
> be a duplicate, so it's all tradeoffs.
>
> For now, it fixes the problem. We can always back it out.
>
>
>
> On Sun, May 11, 2014 at 6:06 AM, edso <email address hidden> wrote:
>
>> Ken: what about the compatibility suggestion you agreed upon? ..ede
>> --
>> https:/
>> You are subscribed to branch lp:duplicity.
>>
>