Re: absolute_import, app names, dots, and a bug

2009-01-29 Thread Todd O'Bryan
On Wed, Jan 28, 2009 at 11:49 PM, Malcolm Tredinnick wrote: > > On Wed, 2009-01-28 at 22:50 -0500, Karen Tracey wrote: >> >> No, I don't think that's an accurate representation of the status. >> The triage state is Accepted and furthermore Malcolm even assigned it >> to

Re: absolute_import, app names, dots, and a bug

2009-01-28 Thread Malcolm Tredinnick
On Wed, 2009-01-28 at 22:50 -0500, Karen Tracey wrote: > On Wed, Jan 28, 2009 at 9:51 PM, Todd O'Bryan > wrote: > > On Sun, Jan 25, 2009 at 7:13 PM, Karen Tracey > wrote: > > Sounds related to: > > > >

Re: absolute_import, app names, dots, and a bug

2009-01-28 Thread Karen Tracey
On Wed, Jan 28, 2009 at 9:51 PM, Todd O'Bryan wrote: > On Sun, Jan 25, 2009 at 7:13 PM, Karen Tracey wrote: > > Sounds related to: > > > > http://code.djangoproject.com/ticket/8193 > > > > Karen > > > > That's exactly what it is, and that hasn't been

Re: absolute_import, app names, dots, and a bug

2009-01-28 Thread Todd O'Bryan
On Sun, Jan 25, 2009 at 7:13 PM, Karen Tracey wrote: > On Sun, Jan 25, 2009 at 7:03 PM, Todd O'Bryan wrote: >> >> I've been trying to convert my apps to use the relative imports from >> __future__ and have noticed a problem. I think it may be something

Re: absolute_import, app names, dots, and a bug

2009-01-25 Thread Karen Tracey
On Sun, Jan 25, 2009 at 7:03 PM, Todd O'Bryan wrote: > > I've been trying to convert my apps to use the relative imports from > __future__ and have noticed a problem. I think it may be something > Django is doing, but I'm not sure. > > In the __init__.py module inside an

absolute_import, app names, dots, and a bug

2009-01-25 Thread Todd O'Bryan
I've been trying to convert my apps to use the relative imports from __future__ and have noticed a problem. I think it may be something Django is doing, but I'm not sure. In the __init__.py module inside an app, I have from __future__ import absolute_import from ..another_app.models import