Ticket #68 (closed defect: fixed)

Opened 1 year ago

Last modified 8 months ago

PyRAF assigns wrong package to a task if the package script loads another package

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

Description

This problem is seen when the noao.imred.specred package is loaded. The offending code is in specred.cl:

#{ SPECRED package definition
 
proto           # bscale

package specred
 
# Slitproc
cl < doslit$doslittasks.cl
task    sparams         = "specred$sparams.par"

specred.cl loads proto before executing the package statement. It then loads the doslittasks.cl task which defines a number of new tasks. These tasks think they are in the proto package, because the current package and current package binary aren't passed to doslittasks.

It's very easy to fix; just make sure that the IrafPkg? run function appends the current package to loadedPath: that is where the current package and current package binary are evaluated from.

Change History

07/20/07 20:48:25 changed by rij

  • status changed from new to assigned.
  • owner changed from somebody to rij.

08/01/07 15:05:11 changed by rij

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

12/11/07 11:53:16 changed by rij

  • 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