Re: Import name conflicts

2017-04-18 Thread Tim Johnson
* Steve D'Aprano [170418 16:08]: > On Wed, 19 Apr 2017 04:28 am, Tim Johnson wrote: > > > Using python 2.7~ > > > > For testing and edification purposes: > > > > I have a project which has a controllers package at the directory > > level just below the root. > > Do you mean the root of the fil

Re: Import name conflicts

2017-04-18 Thread Steve D'Aprano
On Wed, 19 Apr 2017 04:28 am, Tim Johnson wrote: > Using python 2.7~ > > For testing and edification purposes: > > I have a project which has a controllers package at the directory > level just below the root. Do you mean the root of the file system? >>From the top-level (root) of the project

Re: Import name conflicts

2017-04-18 Thread Tim Johnson
* Ben Finney [170418 14:58]: > Tim Johnson writes: > > > Using python 2.7~ > > In Python 2, you should turn on the “default import is absolute” by > issuing the statement:: > > from __future__ import absolute_import > > as one of the first statements in each module. > > When you migrate

Re: Import name conflicts

2017-04-18 Thread Ben Finney
Tim Johnson writes: > Using python 2.7~ In Python 2, you should turn on the “default import is absolute” by issuing the statement:: from __future__ import absolute_import as one of the first statements in each module. When you migrate your code to PYthon 3, that will be the default behavi

Import name conflicts

2017-04-18 Thread Tim Johnson
Using python 2.7~ For testing and edification purposes: I have a project which has a controllers package at the directory level just below the root. >From the top-level (root) of the project, I start my python interpreter. The packages is called 'controllers' and has a submodule named 'imp' I