Ticket #23 (new enhancement)

Opened 3 years ago

changes to import behavior with regard

Reported by: perry Assigned to: somebody
Priority: normal Milestone:
Component: none Version: 1.1.2
Severity: normal Keywords:
Cc:

Description

comments from Rick White and Perry Greenfield regarding this issue:

p.1 (and others): I've gradually developed the opinion that having

'from iraf import images' load the package 'images' was a bad idea and have been wondering whether we should deprecate it. I know we haven't agreed on that, but as a start I would recommend that we not emphasize it much in the documentation. For this example, instead of using the import to load images, add this to the run_imstat function:

iraf.images()

In other words, do what you do in IRAF and just load the package by executing it. I'm open to argument on this, but if we got rid of this functionality we could eliminate the overloading of the import mechanism (which would be a Good Thing.)

So if this variant works now, I'd agree that we should indicate that the import scheme should be deprecated.[pg]

We might consider asking for user feedback on the issue just in case there are people out there that really love 'from iraf import package'. (Unlikely, I'd guess.)