On Fri, Aug 20, 2010 at 8:45 AM, Virgil Dupras wrote:
> On Thu, Aug 19, 2010 at 1:23 PM, Phil Thompson
> wrote:
>> On Tue, 17 Aug 2010 16:06:07 +0200, Virgil Dupras
>> wrote:
>>> I recently ported one of my apps to Python 3, and one of the headaches
>>> I had was because import statements in com
On Thu, Aug 19, 2010 at 1:23 PM, Phil Thompson
wrote:
> On Tue, 17 Aug 2010 16:06:07 +0200, Virgil Dupras
> wrote:
>> I recently ported one of my apps to Python 3, and one of the headaches
>> I had was because import statements in compiled UI files aren't
>> relative ("from . import foo"). In pyt
On Tue, 17 Aug 2010 16:06:07 +0200, Virgil Dupras
wrote:
> I recently ported one of my apps to Python 3, and one of the headaches
> I had was because import statements in compiled UI files aren't
> relative ("from . import foo"). In python 2, it wasn't a problem
> because the lookup was made in th
I recently ported one of my apps to Python 3, and one of the headaches
I had was because import statements in compiled UI files aren't
relative ("from . import foo"). In python 2, it wasn't a problem
because the lookup was made in the same folder as the module importing
the thing, but under Python