Opened 10 years ago
Closed 8 years ago
#46934 closed defect (invalid)
py-astropy: fitscheck script conflicts with py-pyfits
Reported by: | cdeil (Christoph Deil) | Owned by: | macports-tickets@… |
---|---|---|---|
Priority: | Normal | Milestone: | |
Component: | ports | Version: | |
Keywords: | Cc: | robitaille@…, lpsinger (Leo Singer), petrrr, skymoo (Adam Mercer), kurthindenburg (Kurt Hindenburg) | |
Port: | py-astropy py-pyfits |
Description
During the update from Astropy 0.4 to 1.0 I got this error:
---> Activating py27-astropy @1.0_0 Error: org.macports.activate for port py27-astropy returned: Image error: /opt/local/Library/Frameworks/Python.framework/Versions/2.7/bin/fitscheck is being used by the active py27-pyfits port. Please deactivate this port first, or use 'port -f activate py27-astropy' to force the activation. ---> Activating py34-astropy @1.0_0 Error: org.macports.activate for port py34-astropy returned: Image error: /opt/local/Library/Frameworks/Python.framework/Versions/3.4/bin/fitscheck is being used by the active py34-pyfits port. Please deactivate this port first, or use 'port -f activate py34-astropy' to force the activation.
I didn't even know I had pyfits
installed ... the reason is that py-montage
still uses it:
$ port dependents py27-pyfits py27-montage depends on py27-pyfits
Change History (8)
comment:1 Changed 10 years ago by mf2k (Frank Schima)
Port: | py-astropy, py-pyfits → py-astropy py-pyfits |
---|
comment:2 Changed 10 years ago by robitaille@…
comment:3 Changed 10 years ago by cdeil (Christoph Deil)
Is it possible to get rid of pyfits
in Macports completely in the near future?
I guess it's still maintained, but I don't see the point of having it available to astropy.io.fits
for years in parallel.
comment:4 Changed 10 years ago by robitaille@…
Yes, that would be good. I am not familiar with how to deprecate packages, but I will look into it.
comment:5 Changed 10 years ago by lpsinger (Leo Singer)
We could have one of the two packages move its fitscheck script into /opt/local/libexec/pyNN-astropy or /opt/local/libexec/pyNN-pyfits.
comment:8 Changed 8 years ago by kurthindenburg (Kurt Hindenburg)
Cc: | kurthindenburg added |
---|---|
Resolution: | → invalid |
Status: | new → closed |
py-pyfits has been replaced by py-astropy
Note: See
TracTickets for help on using
tickets.
I haven't fixed this yet, but in the mean time I updated the py-montage port to no longer depend on pyfits in r133178.
The issue with the scripts is that I had to change the Portfile for astropy to rename the scripts in the post-destroot, but I guess that by that point it is too late. The scripts can no longer be renamed in the package because we use the entry_points functionality of distutils. One solution would be to patch the setup.py file to rename the entry points there. Does anyone else have any ideas/suggestions?