Opened 10 years ago
Closed 10 years ago
#45295 closed defect (fixed)
py34-aplpy @0.9.12 py34-pyregion is not available
Reported by: | epaell | Owned by: | robitaille@… |
---|---|---|---|
Priority: | Normal | Milestone: | |
Component: | ports | Version: | 2.3.1 |
Keywords: | Cc: | mperrin@…, petrrr | |
Port: | py34-aplpy |
Description
py34-pyregion doesn't appear to be available. It is required when overlaying DS9 regions onto FITS images e.g.
import aplpy fig = aplpy.FITSFigure("test.fits") fig.show_regions("test.reg")
results in
> python3.4 test.py WARNING: FITSFixedWarning: RADECSYS= 'FK5 ' RADECSYS is non-standard, use RADESYSa. [astropy.wcs.wcs] Traceback (most recent call last): File "/opt/local/Library/Frameworks/Python.framework/Versions/3.4/lib/python3.4/site-packages/aplpy/regions.py", line 88, in ds9 import pyregion ImportError: No module named 'pyregion' During handling of the above exception, another exception occurred: Traceback (most recent call last): File "test.py", line 4, in <module> fig.show_regions("test.reg") File "<string>", line 2, in show_regions File "/opt/local/Library/Frameworks/Python.framework/Versions/3.4/lib/python3.4/site-packages/aplpy/decorators.py", line 25, in _auto_refresh return f(*args, **kwargs) File "/opt/local/Library/Frameworks/Python.framework/Versions/3.4/lib/python3.4/site-packages/aplpy/regions.py", line 63, in show_regions PC, TC = ds9(region_file, self._header, **kwargs) File "/opt/local/Library/Frameworks/Python.framework/Versions/3.4/lib/python3.4/site-packages/aplpy/regions.py", line 90, in ds9 raise ImportError("The pyregion package is required to load region files") ImportError: The pyregion package is required to load region files
Perhaps pyregion should be added as a dependency or as a variant?
Attachments (1)
Change History (20)
comment:1 Changed 10 years ago by ryandesign (Ryan Carsten Schmidt)
Cc: | robitaille@… openmaintainer@… removed |
---|---|
Owner: | changed from macports-tickets@… to robitaille@… |
comment:2 Changed 10 years ago by petrrr
Cc: | petr@… added |
---|
comment:3 Changed 10 years ago by petrrr
In r126380 I replaces py31 and py32 subports (no dependents) with py33 and py34 as openmaintainer. This should solve this issue.
comment:4 Changed 10 years ago by epaell
I've tried to install py34-pyregion but I ran into an error (I've attached the log). I'm not sure if this is something associated with my system or whether it is an issue with the py34-pyregion port. It is probably worth pointing out that py27-pyregion installs fine on my system and also that it is a dependency of py27-aplpy.
comment:6 Changed 10 years ago by petrrr
For me py27-pyregion
fails as well. There is actually already an active ticket documenting this: #44391. I'd assume it is the same issue.
Can you tell when you installed py27-pyregion? May it predate the switch from distribute to setuptools?
comment:7 Changed 10 years ago by epaell
You may be right about this, I expect that it may have been a while since I last installed py27-pyregion. I checked the date of the python site-packages directory and it had 23 Jan 2014 - I'm not sure if this accurately reflects the last install/update date? I tried to uninstall/install py27-pyregion as a test and that was when I realised that it was a dependency of py27-aplpy and I was reluctant to uninstall aplpy as well since this is a package I actively use and didn't want to end up in a situation where it was no longer functional. If this will ultimately be resolved with a fix to #44391 then it is fine to close off this ticket.
comment:8 Changed 10 years ago by petrrr
I will try to have a look at #44391 at some occasion, at least if the maintainer does not do this before.
For now, I leave open this ticket. The maintainers of py27-aplpy
might want to check for correct dependencies.
comment:9 Changed 10 years ago by epaell
Since my last post I upgraded to Yosemite this gave me the opportunity to reinstall my entire macports tree. Interestingly, I was still able to install py27-pyregion despite starting from scratch. Alas, py34-pyregion still fails with the same error.
comment:10 Changed 10 years ago by petrrr
This ticket is compiled against py-aplpy
, so formally it would be better to track the py34-pyregion build failure elsewhere.
I would propose to track this in ticket #44391.
comment:11 Changed 10 years ago by petrrr
However, before closing this ticket, we should check if dependencies are specified correctly.
comment:12 Changed 10 years ago by petrrr
Changeset r127112 removes py32 in preparation of further changes.
comment:13 Changed 10 years ago by petrrr
r127114 removes to condition for special Py3 handling of variants. This is not necessary as Py3 should be fully supported.
comment:14 Changed 10 years ago by petrrr
I would propose to remove the +montage
variant which was deprecated in r105631 ca 18 month ago.
comment:15 Changed 10 years ago by petrrr
I hopefully fixed py-pyregion in r127116. Please check if all is okay now.
comment:16 Changed 10 years ago by epaell
That seems to have resolved the install issue with py34-region. Thanks.
comment:17 Changed 10 years ago by petrrr
comment:18 Changed 10 years ago by petrrr
In r129173 I updated to 0.9.14 and did some further changes as follows:
- fix livecheck
- PyPI pattern & minor formating
- remove +montage variant
- replace py{26,33} subports with py{27,34} respectively
I'd assume the port in now okay. So I will close this.
comment:19 Changed 10 years ago by petrrr
Resolution: | → fixed |
---|---|
Status: | new → closed |
Cc Me!