Not importing omero first leads to strange OmeroPy errors

[jamoore]

from omero_model_ImageI import ImageI as ImageI

print ImageI.NAME
print ImageI.DATASETLINKS                     

leads to the following error:

python OmeroClients/staticfields.py --Ice.Config=/Users/josh/GlencoeSoftware.git/git/omero.git/dist/etc/ice.config
Traceback (most recent call last):
  File "OmeroClients/staticfields.py", line 1, in <module>
    from omero_model_ImageI import ImageI as ImageI
  File "/Users/josh/GlencoeSoftware.git/git/omero.git/dist/lib/python/omero_model_ImageI.py", line 13, in <module>
    from omero.rtypes import rlong
ImportError: No module named rtypes
scons: *** [OmeroClients/staticfields.py] Error 1

[jmoore]

Carlos, would adding all = rtypes? solve this?

[jmoore]

A fix for this might also include other issues:

• import omero shouldn't report PIL warnings (too much imported)
• #1392 (too little imported)

[jmoore]

After the addition of numpy and pytables imports (r4833 et al), several things broken (including bin/omero help !). import omero imports too much. This can be fixed by moving the client class to omero/clients.py (or similar), but how much user usage does this break?

For example:

import omero
omero.model.FooI()

won't work.

import omero
c = omero.client("localhost")
omero.model.FooI()

will.

import omero.clients
omero.model.FooI()

also works.

We could alternatively offer something like:

import omero_all # or similar

which does the whole startup, but it will need to be clear.

[jmoore]

r4898. Doesn't yet include import omero_all, but does include import omero.clients

[cneves]

r5480 moved UnloadedEntityException? and UnloadedCollectionException? back to the omero namespace, reverting that change from r4898 because that's where omero classes expect it to be.

[jmoore]

r5505

[jmoore]

The various commits have stopped the recursion, but in future releases (especially 4.2 with #1359) we will need to work on usability. E.g., sage uses:

 from sage.all import *