Ticket #59 (closed defect: fixed)

Opened 1 year ago

Last modified 6 months ago

PyRAF has the wrong search path for finding parameters not in the called task's parameter list

Reported by: rij Assigned to: sontag
Priority: normal Milestone: PyRAF 1.5 stsci_python 2.6
Component: none Version:
Severity: normal Keywords:
Cc:

Description (Last modified by rij)

As an example:

the gemini package defines the gnirs package

the gnirs package loads the gemtools package

the gemtools package loads the specred package

the specred package defines the apall task (spp)

The apall task, called from a script in the gnirs package, accesses the parameter 'database'

apall doesn't have a parameter 'database', so it has to get it from somewhere else.

Running the script under the cl, apall appears to get specred.database

Running the script under PyRAF, apall appears to get gnirs.database

Change History

03/27/07 15:10:09 changed by rij

  • description changed.

07/20/07 20:24:37 changed by rij

  • status changed from new to closed.
  • resolution set to fixed.

Fixed by Chris S in r796

11/21/07 11:05:29 changed by sontag

  • status changed from closed to reopened.
  • resolution deleted.

11/21/07 11:05:46 changed by sontag

  • status changed from reopened to new.
  • owner changed from somebody to sontag.

11/21/07 11:05:57 changed by sontag

  • status changed from new to closed.
  • resolution set to fixed.

11/21/07 13:43:13 changed by sontag

  • milestone set to stsci_python 2.6 release.

02/28/08 09:03:05 changed by sontag

  • milestone changed from stsci_python 2.6 release to PyRAF 1.5 stsci_python 2.6.

Milestone stsci_python 2.6 release deleted