[AstroPy] ANN: Astropy v0.4 released

[Derek Homeier]

On 17 Jul 2014, at 06:01 pm, Emmanuel Caux <emmanuel.caux at irap.omp.eu> wrote:

> Many thanks for that, just a question, I install software on my Mac with Fink and I have currently installed :
> 
> [Emmanuels-MacBook-Pro:~] caux% fink list astropy
> Information about 10660 packages read in 1 seconds.
>  i   astropy-py27     0.3-2        Python library for Astronomy
>      astropy-py32     0.3-2        Python library for Astronomy
>      astropy-py33     0.3-2        Python library for Astronomy
> 
> But if I run fink update-all or fink update astropy-py27, I have this answer :
> 
> [Emmanuels-MacBook-Pro:~] caux% fink update astropy-py27
> Information about 10660 packages read in 1 seconds.
> No packages to install.
> 
> Does that mean I hane to remove my install of atsropy 0.3 and install the new astropy 0.4 ?
> 
Umm, maintainers are certainly doing their best, but I think miracles are only performed on prior request ;-)
Even if their spare time (because that’s what it is) had allowed to get the update into fink in the 2 ½ hours
after it has been announced, it’s extremely unlikely that even the Fink mirrors had been synchronised this
quicky!
I had a look at the new release and actually ran into a problem right away building it on OS X 10.9:
File "/scratch.noindex/fink.build/astropy-py34-0.4-1/astropy-0.4/ah_bootstrap.py", line 435, in _check_submodule_using_git
    stderr = stderr.decode(stdio_encoding)
TypeError: decode() argument 1 must be str, not None

This is because locale.getdefaultlocale() returns (None, None) if LC_CTYPE is not set, which happens to
be the case in my default environment because Terminal for some reason only presets it to the useless
value ‘UTF-8’. But the Fink build environment is independent from the user’s settings anyway and should be.
So I could resolve this by explicitly setting LC_CTYPE in the build script, but maybe this is a matter to think
about upstream if the build could/should be supported without this setting (or if set to something like “C”!).

Then I came upon another problem when trying to build the py32 and py33 versions:

#!/bin/bash -ev
  export LC_CTYPE=en_US.ISO8859-1
  /sw/bin/python3.3 setup.py build --use-system-cfitsio --use-system-expat
Traceback (most recent call last):
  File "setup.py", line 8, in <module>
    import ah_bootstrap
  File "/scratch.noindex/fink.build/astropy-py33-0.4-1/astropy-0.4/ah_bootstrap.py", line 716, in <module>
    _main()
  File "/scratch.noindex/fink.build/astropy-py33-0.4-1/astropy-0.4/ah_bootstrap.py", line 713, in _main
    use_astropy_helpers(**kwargs)
  File "/scratch.noindex/fink.build/astropy-py33-0.4-1/astropy-0.4/ah_bootstrap.py", line 245, in use_astropy_helpers
    upgrade = _do_upgrade(dist, index_url)
  File "/scratch.noindex/fink.build/astropy-py33-0.4-1/astropy-0.4/ah_bootstrap.py", line 341, in _do_upgrade
    package_index = PackageIndex(index_url=index_url)
  File "/sw/lib/python3.3/site-packages/setuptools/package_index.py", line 269, in __init__
    Environment.__init__(self,*args,**kw)
  File "/sw/lib/python3.3/site-packages/pkg_resources.py", line 799, in __init__
    self.scan(search_path)
  File "/sw/lib/python3.3/site-packages/pkg_resources.py", line 829, in scan
    self.add(dist)
  File "/sw/lib/python3.3/site-packages/pkg_resources.py", line 849, in add
    dists.sort(key=operator.attrgetter('hashcmp'), reverse=True)
TypeError: unorderable types: str() < NoneType()

Strangely this succeeds when building it myself, so I suspect it must have to do with some other environment
variable that by default is not set for the Fink package build user, but I’ve no idea where to look at right now.
So I’ve uploaded an updated info file just for the 2.7 and 3.4 versions to
https://sourceforge.net/p/fink/package-submissions/4396/

(this is the new .info file at the bottom - or should I better open a new ticket for this?)

If you feel like becoming an early adopter and want to give this a try, you only need to install the file into your
local fink tree and fink update astropy-py27 should get you ready for testing.
But please report any problems first to me and not only to Sebastien!

Cheers,
					Derek