From jmwalawender at gmail.com  Tue Dec  1 18:10:59 2015
From: jmwalawender at gmail.com (Josh Walawender)
Date: Tue, 1 Dec 2015 13:10:59 -1000
Subject: [AstroPy] Time/IERS Question
Message-ID: <798E994E-4D04-44A3-B882-14B5B3A54DA9@gmail.com>

Hi all,

I?m getting some behavior I don?t understand from astropy.time.  I?m trying to make a quick tool for printing out the current time in UT, MJD, and sidereal (LMST).  When I run it, I get an error on the step of calculating the sidereal time:

LST_string = now.sidereal_time('mean').to_string(sep=':',  precision=1)


Traceback (most recent call last):
  File "time_example.py", line 20, in <module>
    LST_string = now.sidereal_time('mean').to_string(sep=':',  precision=1)
  File "/Users/joshw/anaconda/lib/python2.7/site-packages/astropy/time/core.py", line 523, in sidereal_time
    gst = self._erfa_sidereal_time(available_models[model.upper()])
  File "/Users/joshw/anaconda/lib/python2.7/site-packages/astropy/time/core.py", line 539, in _erfa_sidereal_time
    for jd_part in ('jd1', 'jd2')]
  File "/Users/joshw/anaconda/lib/python2.7/site-packages/astropy/time/core.py", line 704, in __getattr__
    tm._set_scale(attr)
  File "/Users/joshw/anaconda/lib/python2.7/site-packages/astropy/time/core.py", line 372, in _set_scale
    args.append(get_dt(jd1, jd2))
  File "/Users/joshw/anaconda/lib/python2.7/site-packages/astropy/time/core.py", line 834, in _get_delta_ut1_utc
    delta = iers_table.ut1_utc(jd1, jd2)
  File "/Users/joshw/anaconda/lib/python2.7/site-packages/astropy/utils/iers/iers.py", line 234, in ut1_utc
    raise IndexError('(some) times are outside of range covered '
IndexError: (some) times are outside of range covered by IERS table.

When I go ahead and download the IERS table using the tools in astroplan:

from astroplan import download_IERS_A
download_IERS_A()

the code works.  But I need to do this download every time I run the code which is time consuming on code that I want to run many times.  Shouldn?t this be cached?

Any idea why the download is needed every time?

thanks!
Josh

P.S.  Entire code is pasted in below:



from datetime import datetime as dt
from astropy.time import Time
from astropy.coordinates import EarthLocation
import astropy.units as u

# from astroplan import download_IERS_A
# download_IERS_A()

utnow = dt.utcnow()
subaru = EarthLocation.from_geodetic(-155.476111111*u.degree,\
                                     19.8255555556*u.degree,\
                                     height=4139.0*u.meter)
now = Time(utnow, location=subaru)

UTC_string = utnow.strftime('%H:%M:%S.%f')
print(UTC_string)
MJD_string = '{:20.8f}'.format(now.mjd)
print(MJD_string)
LST_string = now.sidereal_time('mean').to_string(sep=':',  precision=1)
print(LST_string)

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/astropy/attachments/20151201/80dd671a/attachment.html>

From ejsaiet at alaska.edu  Fri Dec  4 16:42:45 2015
From: ejsaiet at alaska.edu (Eyal Saiet)
Date: Fri, 4 Dec 2015 12:42:45 -0900
Subject: [AstroPy] normalizing pictures from camera at various settings
Message-ID: <CA+ysReBa0VR=2iZ4UumAR7VB_uHh9HA+1rZk0QGPypc07q5AJw@mail.gmail.com>

Hello,
I am taking an image processing class. My class project involves working
with given camera images of the night sky. Because the camera is set at at
auto, I cannot compare intensity of two images(camera sensitivity varies
due to changes in shutter speed, aperture, and ISO). Is there any algorithm
you would recommend that can infer what the dark night sky should look like
in the histogram, and use that information to adjust the histogram,
therefore enabling me to compare  two image DN values, from different
camera settings?
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/astropy/attachments/20151204/6aea96ed/attachment.html>

From ejsaiet at alaska.edu  Wed Dec  9 02:13:06 2015
From: ejsaiet at alaska.edu (Eyal Saiet)
Date: Tue, 8 Dec 2015 22:13:06 -0900
Subject: [AstroPy] normalizing pictures from camera at various settings
In-Reply-To: <CA+ysReBa0VR=2iZ4UumAR7VB_uHh9HA+1rZk0QGPypc07q5AJw@mail.gmail.com>
References: <CA+ysReBa0VR=2iZ4UumAR7VB_uHh9HA+1rZk0QGPypc07q5AJw@mail.gmail.com>
Message-ID: <CA+ysReDZtt3oh7Y6R6miNAa8ZCwPMnj_RWZcUk0P3TJeWbW_cQ@mail.gmail.com>

Hello colleagues,
I did not get any replies to my question. One idea that stroke me was to
assume the brightens of stars is constant and use its DN value to normalize
my images? I need to dig more into this, but thought maybe someone would
have feedback?

On Fri, Dec 4, 2015 at 12:42 PM, Eyal Saiet <ejsaiet at alaska.edu> wrote:

> Hello,
> I am taking an image processing class. My class project involves working
> with given camera images of the night sky. Because the camera is set at at
> auto, I cannot compare intensity of two images(camera sensitivity varies
> due to changes in shutter speed, aperture, and ISO). Is there any algorithm
> you would recommend that can infer what the dark night sky should look like
> in the histogram, and use that information to adjust the histogram,
> therefore enabling me to compare  two image DN values, from different
> camera settings?
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/astropy/attachments/20151208/29838566/attachment.html>

From evert.rol at gmail.com  Wed Dec  9 03:00:16 2015
From: evert.rol at gmail.com (Evert Rol)
Date: Wed, 9 Dec 2015 19:00:16 +1100
Subject: [AstroPy] normalizing pictures from camera at various settings
In-Reply-To: <CA+ysReDZtt3oh7Y6R6miNAa8ZCwPMnj_RWZcUk0P3TJeWbW_cQ@mail.gmail.com>
References: <CA+ysReBa0VR=2iZ4UumAR7VB_uHh9HA+1rZk0QGPypc07q5AJw@mail.gmail.com>
 <CA+ysReDZtt3oh7Y6R6miNAa8ZCwPMnj_RWZcUk0P3TJeWbW_cQ@mail.gmail.com>
Message-ID: <A4AFB1BA-A690-4586-A201-596F87447B5B@gmail.com>

  Hi Eyal,

> Hello colleagues,
> I did not get any replies to my question. One idea that stroke me was to assume the brightens of stars is constant and use its DN value to normalize my images? I need to dig more into this, but thought maybe someone would have feedback?

Yes, that would be the most sensible thing to do.
The sky background is not that constant that you can histogram it and compare between observations: moon and other background light can influence it. The stars should remain relatively constant.
You want to perform seeing-matched aperture photometry for the best results (if that's manageable or relevant for your images), so that the fraction of light/counts for each star is the same between images.
There is a chance you have some variable stars in your images; if you make sure you use enough stars, you can fairly easily filter out the variable stars and ignore those in your analysis.

  Evert


> Hello,
> I am taking an image processing class. My class project involves working with given camera images of the night sky. Because the camera is set at at auto, I cannot compare intensity of two images(camera sensitivity varies due to changes in shutter speed, aperture, and ISO). Is there any algorithm you would recommend that can infer what the dark night sky should look like in the histogram, and use that information to adjust the histogram, therefore enabling me to compare  two image DN values, from different camera settings?
> 



From ejsaiet at alaska.edu  Wed Dec  9 03:28:48 2015
From: ejsaiet at alaska.edu (Eyal Saiet)
Date: Tue, 8 Dec 2015 23:28:48 -0900
Subject: [AstroPy] normalizing pictures from camera at various settings
In-Reply-To: <A4AFB1BA-A690-4586-A201-596F87447B5B@gmail.com>
References: <CA+ysReBa0VR=2iZ4UumAR7VB_uHh9HA+1rZk0QGPypc07q5AJw@mail.gmail.com>
 <CA+ysReDZtt3oh7Y6R6miNAa8ZCwPMnj_RWZcUk0P3TJeWbW_cQ@mail.gmail.com>
 <A4AFB1BA-A690-4586-A201-596F87447B5B@gmail.com>
Message-ID: <CA+ysReASPUFHqOaAD480xuFhrg=4fxzRuZ1LH40jb_XPksDTJw@mail.gmail.com>

Excellent, with some image processing, I can get average DN values of
several stars excluding the rest of the night sky in the image.
Thanks Evert!
On Tue, Dec 8, 2015 at 11:00 PM, Evert Rol <evert.rol at gmail.com> wrote:

>   Hi Eyal,
>
> > Hello colleagues,
> > I did not get any replies to my question. One idea that stroke me was to
> assume the brightens of stars is constant and use its DN value to normalize
> my images? I need to dig more into this, but thought maybe someone would
> have feedback?
>
> Yes, that would be the most sensible thing to do.
> The sky background is not that constant that you can histogram it and
> compare between observations: moon and other background light can influence
> it. The stars should remain relatively constant.
> You want to perform seeing-matched aperture photometry for the best
> results (if that's manageable or relevant for your images), so that the
> fraction of light/counts for each star is the same between images.
> There is a chance you have some variable stars in your images; if you make
> sure you use enough stars, you can fairly easily filter out the variable
> stars and ignore those in your analysis.
>
>   Evert
>
>
> > Hello,
> > I am taking an image processing class. My class project involves working
> with given camera images of the night sky. Because the camera is set at at
> auto, I cannot compare intensity of two images(camera sensitivity varies
> due to changes in shutter speed, aperture, and ISO). Is there any algorithm
> you would recommend that can infer what the dark night sky should look like
> in the histogram, and use that information to adjust the histogram,
> therefore enabling me to compare  two image DN values, from different
> camera settings?
> >
>
> _______________________________________________
> AstroPy mailing list
> AstroPy at scipy.org
> https://mail.scipy.org/mailman/listinfo/astropy
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/astropy/attachments/20151208/c0d7d18a/attachment.html>

From thomas.robitaille at gmail.com  Mon Dec 14 10:32:29 2015
From: thomas.robitaille at gmail.com (Thomas Robitaille)
Date: Mon, 14 Dec 2015 16:32:29 +0100
Subject: [AstroPy] ANN: Astropy v1.1 released
Message-ID: <CAGMHX_1t6TCaWMF_9EwjpYcU85mgKNMYpG9GN1ci6O0h3Oa0AA@mail.gmail.com>

Dear colleagues,

We are very happy to announce the v1.1 release of the Astropy package,
a core Python package for Astronomy:

 http://www.astropy.org

Astropy is a community-driven Python package intended to contain much
of the core functionality and common tools needed for astronomy and
astrophysics.

New and improved major functionality in this release includes:

* New functions to automatically determine histogram bins, including
  the Bayesian blocks algorithm
* A new interface to transform between Table objects and pandas
  DataFrame objects
* Support for table indexing
* Support for supergalactic and ecliptic coordinates
* A new .info attribute to get summary information about tables and
  columns
* A new show_in_notebook() method to show a table in Jupyter/IPython
  notebooks with additional interactivity features
* Support for new units, including logarithmic units such as
  magnitudes, dex, and decibels
* Support for the Planck 2015 cosmology and significant performance
  improvements in the cosmology sub-package

In addition, hundreds of smaller improvements and fixes have been made.
An overview of the changes is provided at:

  http://docs.astropy.org/en/stable/whatsnew/1.1.html

Instructions for installing Astropy are provided on our website, and
extensive documentation can be found at:

  http://docs.astropy.org

If you make use of the Anaconda Python Distribution, you can update to
Astropy v1.1 with:

  conda update astropy

If you normally use pip, you can upgrade with:

  pip install astropy --upgrade

Please report any issues, or request new features via our GitHub
repository:

  https://github.com/astropy/astropy/issues

Over 160 developers have contributed code to Astropy so far, and you
can find out more about the team behind Astropy here:

  http://www.astropy.org/team.html

As a reminder, Astropy v1.0 (our long term support release) will
continue to be supported with bug fixes until Feb 19th 2017, so if you
need to use Astropy in a very stable environment, you may want to
consider staying on the v1.0.x set of releases rather than upgrading to
v1.1.

If you use Astropy directly for your work, or as a dependency to
another package, please remember to include the following
acknowledgment at the end of papers:

"""
This research made use of Astropy, a community-developed core Python
package for Astronomy (Astropy Collaboration, 2013).
"""

where (Astropy Collaboration, 2013) is a reference to the Astropy paper:

  http://dx.doi.org/10.1051/0004-6361/201322068

Please feel free to forward this announcement to anyone you think might
be interested in this release!

Thomas Robitaille, Erik Tollerud, and Perry Greenfield
on behalf of The Astropy Collaboration


From erik.tollerud at gmail.com  Wed Dec 16 13:23:20 2015
From: erik.tollerud at gmail.com (Erik Tollerud)
Date: Wed, 16 Dec 2015 13:23:20 -0500
Subject: [AstroPy] Time/IERS Question
In-Reply-To: <798E994E-4D04-44A3-B882-14B5B3A54DA9@gmail.com>
References: <798E994E-4D04-44A3-B882-14B5B3A54DA9@gmail.com>
Message-ID: <CAARXUwW0-NR4EHQcX-ZLFFPjv2pPyBb7UYOZeF46u2uf9pSAtA@mail.gmail.com>

Hi Josh,

The short answer here is that it probably should work just the way you're
thinking, but that hasn't been implemented yet. See
https://github.com/astropy/astropy/issues/3275 for some background.

The longer answer is that it's not entirely clear how *often* they should
be downloaded.  In *theory* it should be downloaded every time, because the
IERS A predictions are based on earth-based observations, and so they are
updated at irregular intervals (~1 week).  For almost all applications, the
predictions are more than good enough up to the end of when they're valid
(I think that's 21 days, although I can't recall for sure).

So probably the best solution, and one that would be *nice* to have in
Astropy would be to have the IERS A be cached in a way that expires after
maybe a week or so, and is only re-downloaded after that.  Unfortunately,
that requires some changes to the caching machinery, which we simply
haven't had time to do.  But certainly anyone is welcome to take a shot at
getting this in for Astropy 1.2 - I would love to see it, personally, and
might get to it, but I say that about a lot of things...





---
Erik T

On Tue, Dec 1, 2015 at 6:10 PM, Josh Walawender <jmwalawender at gmail.com>
wrote:

> Hi all,
>
> I?m getting some behavior I don?t understand from astropy.time.  I?m
> trying to make a quick tool for printing out the current time in UT, MJD,
> and sidereal (LMST).  When I run it, I get an error on the step of
> calculating the sidereal time:
>
> LST_string = now.sidereal_time('mean').to_string(sep=':',  precision=1)
>
>
> Traceback (most recent call last):
>   File "time_example.py", line 20, in <module>
>     LST_string = now.sidereal_time('mean').to_string(sep=':',  precision=1)
>   File
> "/Users/joshw/anaconda/lib/python2.7/site-packages/astropy/time/core.py",
> line 523, in sidereal_time
>     gst = self._erfa_sidereal_time(available_models[model.upper()])
>   File
> "/Users/joshw/anaconda/lib/python2.7/site-packages/astropy/time/core.py",
> line 539, in _erfa_sidereal_time
>     for jd_part in ('jd1', 'jd2')]
>   File
> "/Users/joshw/anaconda/lib/python2.7/site-packages/astropy/time/core.py",
> line 704, in __getattr__
>     tm._set_scale(attr)
>   File
> "/Users/joshw/anaconda/lib/python2.7/site-packages/astropy/time/core.py",
> line 372, in _set_scale
>     args.append(get_dt(jd1, jd2))
>   File
> "/Users/joshw/anaconda/lib/python2.7/site-packages/astropy/time/core.py",
> line 834, in _get_delta_ut1_utc
>     delta = iers_table.ut1_utc(jd1, jd2)
>   File
> "/Users/joshw/anaconda/lib/python2.7/site-packages/astropy/utils/iers/iers.py",
> line 234, in ut1_utc
>     raise IndexError('(some) times are outside of range covered '
> IndexError: (some) times are outside of range covered by IERS table.
>
> When I go ahead and download the IERS table using the tools in astroplan:
>
> from astroplan import download_IERS_A
> download_IERS_A()
>
> the code works.  But I need to do this download every time I run the code
> which is time consuming on code that I want to run many times.  Shouldn?t
> this be cached?
>
> Any idea why the download is needed every time?
>
> thanks!
> Josh
>
> P.S.  Entire code is pasted in below:
>
>
>
> from datetime import datetime as dt
> from astropy.time import Time
> from astropy.coordinates import EarthLocation
> import astropy.units as u
>
> # from astroplan import download_IERS_A
> # download_IERS_A()
>
> utnow = dt.utcnow()
> subaru = EarthLocation.from_geodetic(-155.476111111*u.degree,\
>                                      19.8255555556*u.degree,\
>                                      height=4139.0*u.meter)
> now = Time(utnow, location=subaru)
>
> UTC_string = utnow.strftime('%H:%M:%S.%f')
> print(UTC_string)
> MJD_string = '{:20.8f}'.format(now.mjd)
> print(MJD_string)
> LST_string = now.sidereal_time('mean').to_string(sep=':',  precision=1)
> print(LST_string)
>
>
> _______________________________________________
> AstroPy mailing list
> AstroPy at scipy.org
> https://mail.scipy.org/mailman/listinfo/astropy
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/astropy/attachments/20151216/508d254f/attachment.html>

From embray at stsci.edu  Wed Dec 16 15:19:11 2015
From: embray at stsci.edu (Erik Bray)
Date: Wed, 16 Dec 2015 15:19:11 -0500
Subject: [AstroPy] Time/IERS Question
In-Reply-To: <CAARXUwW0-NR4EHQcX-ZLFFPjv2pPyBb7UYOZeF46u2uf9pSAtA@mail.gmail.com>
References: <798E994E-4D04-44A3-B882-14B5B3A54DA9@gmail.com>
 <CAARXUwW0-NR4EHQcX-ZLFFPjv2pPyBb7UYOZeF46u2uf9pSAtA@mail.gmail.com>
Message-ID: <5671C73F.2060603@stsci.edu>

On 12/16/2015 01:23 PM, Erik Tollerud wrote:
> So probably the best solution, and one that would be *nice* to have in Astropy
> would be to have the IERS A be cached in a way that expires after maybe a week
> or so, and is only re-downloaded after that.  Unfortunately, that requires some
> changes to the caching machinery, which we simply haven't had time to do.  But
> certainly anyone is welcome to take a shot at getting this in for Astropy 1.2 -
> I would love to see it, personally, and might get to it, but I say that about a
> lot of things...


Indeed, the astropy download cache is rather lacking in sophisticated features. 
  If the download cache is used, it will prevent re-downloading a file at the 
same URL if it has already been downloaded (so unless the cache is manually 
cleared, or caching is disabled, it will always reused the IERS A table last 
downloaded to the cache).

The main thing astropy's download cache lacks is use of standard(ish) mechanisms 
to detect if a file/resource at a URL has been updated since it was last 
downloaded and cached.  For more background on this issue and hints as to the 
work that needs to be done on it, see this issue:

https://github.com/astropy/astropy/issues/3961

If anyone would like to work on this, it would make for a lovely contribution to 
astropy that doesn't require getting into any of the astro-specific code.

Erik B.


> On Tue, Dec 1, 2015 at 6:10 PM, Josh Walawender <jmwalawender at gmail.com
> <mailto:jmwalawender at gmail.com>> wrote:
>
>     Hi all,
>
>     I?m getting some behavior I don?t understand from astropy.time.  I?m trying
>     to make a quick tool for printing out the current time in UT, MJD, and
>     sidereal (LMST).  When I run it, I get an error on the step of calculating
>     the sidereal time:
>
>     LST_string = now.sidereal_time('mean').to_string(sep=':',  precision=1)
>
>
>     Traceback (most recent call last):
>        File "time_example.py", line 20, in <module>
>          LST_string = now.sidereal_time('mean').to_string(sep=':',  precision=1)
>        File
>     "/Users/joshw/anaconda/lib/python2.7/site-packages/astropy/time/core.py",
>     line 523, in sidereal_time
>          gst = self._erfa_sidereal_time(available_models[model.upper()])
>        File
>     "/Users/joshw/anaconda/lib/python2.7/site-packages/astropy/time/core.py",
>     line 539, in _erfa_sidereal_time
>          for jd_part in ('jd1', 'jd2')]
>        File
>     "/Users/joshw/anaconda/lib/python2.7/site-packages/astropy/time/core.py",
>     line 704, in __getattr__
>          tm._set_scale(attr)
>        File
>     "/Users/joshw/anaconda/lib/python2.7/site-packages/astropy/time/core.py",
>     line 372, in _set_scale
>          args.append(get_dt(jd1, jd2))
>        File
>     "/Users/joshw/anaconda/lib/python2.7/site-packages/astropy/time/core.py",
>     line 834, in _get_delta_ut1_utc
>          delta = iers_table.ut1_utc(jd1, jd2)
>        File
>     "/Users/joshw/anaconda/lib/python2.7/site-packages/astropy/utils/iers/iers.py",
>     line 234, in ut1_utc
>          raise IndexError('(some) times are outside of range covered '
>     IndexError: (some) times are outside of range covered by IERS table.
>
>     When I go ahead and download the IERS table using the tools in astroplan:
>
>     from astroplan import download_IERS_A
>     download_IERS_A()
>
>     the code works.  But I need to do this download every time I run the code
>     which is time consuming on code that I want to run many times.  Shouldn?t
>     this be cached?
>
>     Any idea why the download is needed every time?
>
>     thanks!
>     Josh
>
>     P.S.  Entire code is pasted in below:
>
>
>
>     from datetime import datetime as dt
>     from astropy.time import Time
>     from astropy.coordinates import EarthLocation
>     import astropy.units as u
>
>     # from astroplan import download_IERS_A
>     # download_IERS_A()
>
>     utnow = dt.utcnow()
>     subaru = EarthLocation.from_geodetic(-155.476111111*u.degree,\
>                                           19.8255555556*u.degree,\
>                                           height=4139.0*u.meter)
>     now = Time(utnow, location=subaru)
>
>     UTC_string = utnow.strftime('%H:%M:%S.%f')
>     print(UTC_string)
>     MJD_string = '{:20.8f}'.format(now.mjd)
>     print(MJD_string)
>     LST_string = now.sidereal_time('mean').to_string(sep=':',  precision=1)
>     print(LST_string)
>
>
>     _______________________________________________
>     AstroPy mailing list
>     AstroPy at scipy.org <mailto:AstroPy at scipy.org>
>     https://mail.scipy.org/mailman/listinfo/astropy
>
>
>
>
> _______________________________________________
> AstroPy mailing list
> AstroPy at scipy.org
> https://mail.scipy.org/mailman/listinfo/astropy
>



From dmfaes at gmail.com  Mon Dec 21 12:50:05 2015
From: dmfaes at gmail.com (Daniel M. Faes)
Date: Mon, 21 Dec 2015 14:50:05 -0300
Subject: [AstroPy] Installation error
Message-ID: <CAJ3g4RfpufgZva2jgMZzPtXr7CMJP24RLV-_Sw-0g8Fi2v1UAg@mail.gmail.com>

Dear all,
I'm trying to install astropy in my Ubuntu system, and I getting the
following error (below).
Cheers,
Daniel


- - -
creating build/temp.linux-x86_64-2.7/astropy

x86_64-linux-gnu-gcc -pthread -fno-strict-aliasing -DNDEBUG -g -fwrapv -O2
-Wall -Wstrict-prototypes -fPIC -I/usr/include/python2.7 -c
astropy/_compiler.c -o build/temp.linux-x86_64-2.7/astropy/_compiler.o

astropy/_compiler.c:1:20: fatal error: Python.h: File or directory not found

 #include <Python.h>

                    ^

compilation terminated.

error: command 'x86_64-linux-gnu-gcc' failed with exit status 1

----------------------------------------
Cleaning up...
Command /usr/bin/python -c "import setuptools,
tokenize;__file__='/tmp/pip_build_root/astropy/setup.py';exec(compile(getattr(tokenize,
'open', open)(__file__).read().replace('\r\n', '\n'), __file__, 'exec'))"
install --record /tmp/pip-nXWLvE-record/install-record.txt
--single-version-externally-managed --compile failed with error code 1 in
/tmp/pip_build_root/astropy
Traceback (most recent call last):
  File "/usr/bin/pip", line 9, in <module>
    load_entry_point('pip==1.5.4', 'console_scripts', 'pip')()
  File "/usr/lib/python2.7/dist-packages/pip/__init__.py", line 235, in main
    return command.main(cmd_args)
  File "/usr/lib/python2.7/dist-packages/pip/basecommand.py", line 161, in
main
    text = '\n'.join(complete_log)
UnicodeDecodeError: 'ascii' codec can't decode byte 0xc3 in position 69:
ordinal not in range(128)
= = =
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/astropy/attachments/20151221/ebc699a2/attachment.html>

From embray at stsci.edu  Mon Dec 21 12:56:06 2015
From: embray at stsci.edu (Erik Bray)
Date: Mon, 21 Dec 2015 12:56:06 -0500
Subject: [AstroPy] Installation error
In-Reply-To: <CAJ3g4RfpufgZva2jgMZzPtXr7CMJP24RLV-_Sw-0g8Fi2v1UAg@mail.gmail.com>
References: <CAJ3g4RfpufgZva2jgMZzPtXr7CMJP24RLV-_Sw-0g8Fi2v1UAg@mail.gmail.com>
Message-ID: <56783D36.7010605@stsci.edu>

Hi Daniel,

For installing most non-trivial Python packages (i.e. anything containing C 
code) on Linux you will need the Python-dev package, which is not always 
installed by default:

$ sudo apt-get install python-dev

Erik

On 12/21/2015 12:50 PM, Daniel M. Faes wrote:
> Dear all,
> I'm trying to install astropy in my Ubuntu system, and I getting the following
> error (below).
> Cheers,
> Daniel
>
>
> - - -
> creating build/temp.linux-x86_64-2.7/astropy
>
> x86_64-linux-gnu-gcc -pthread -fno-strict-aliasing -DNDEBUG -g -fwrapv -O2 -Wall
> -Wstrict-prototypes -fPIC -I/usr/include/python2.7 -c astropy/_compiler.c -o
> build/temp.linux-x86_64-2.7/astropy/_compiler.o
>
> astropy/_compiler.c:1:20: fatal error: Python.h: File or directory not found
>
>   #include <Python.h>
>
>                      ^
>
> compilation terminated.
>
> error: command 'x86_64-linux-gnu-gcc' failed with exit status 1
>
> ----------------------------------------
> Cleaning up...
> Command /usr/bin/python -c "import setuptools,
> tokenize;__file__='/tmp/pip_build_root/astropy/setup.py';exec(compile(getattr(tokenize,
> 'open', open)(__file__).read().replace('\r\n', '\n'), __file__, 'exec'))"
> install --record /tmp/pip-nXWLvE-record/install-record.txt
> --single-version-externally-managed --compile failed with error code 1 in
> /tmp/pip_build_root/astropy
> Traceback (most recent call last):
>    File "/usr/bin/pip", line 9, in <module>
>      load_entry_point('pip==1.5.4', 'console_scripts', 'pip')()
>    File "/usr/lib/python2.7/dist-packages/pip/__init__.py", line 235, in main
>      return command.main(cmd_args)
>    File "/usr/lib/python2.7/dist-packages/pip/basecommand.py", line 161, in main
>      text = '\n'.join(complete_log)
> UnicodeDecodeError: 'ascii' codec can't decode byte 0xc3 in position 69: ordinal
> not in range(128)
> = = =
>
>
> _______________________________________________
> AstroPy mailing list
> AstroPy at scipy.org
> https://mail.scipy.org/mailman/listinfo/astropy
>



From dmfaes at gmail.com  Mon Dec 21 13:21:16 2015
From: dmfaes at gmail.com (Daniel M. Faes)
Date: Mon, 21 Dec 2015 15:21:16 -0300
Subject: [AstroPy] Installation error
In-Reply-To: <56783D36.7010605@stsci.edu>
References: <CAJ3g4RfpufgZva2jgMZzPtXr7CMJP24RLV-_Sw-0g8Fi2v1UAg@mail.gmail.com>
 <56783D36.7010605@stsci.edu>
Message-ID: <CAJ3g4RfbHHav4r1D8yejKtEa2zf3RtfJsP9Hccu_2veMfRsHbg@mail.gmail.com>

Erik,
Indeed it worked. Thanks!
Daniel


2015-12-21 14:56 GMT-03:00 Erik Bray <embray at stsci.edu>:

> Hi Daniel,
>
> For installing most non-trivial Python packages (i.e. anything containing
> C code) on Linux you will need the Python-dev package, which is not always
> installed by default:
>
> $ sudo apt-get install python-dev
>
> Erik
>
>
> On 12/21/2015 12:50 PM, Daniel M. Faes wrote:
>
>> Dear all,
>> I'm trying to install astropy in my Ubuntu system, and I getting the
>> following
>> error (below).
>> Cheers,
>> Daniel
>>
>>
>> - - -
>> creating build/temp.linux-x86_64-2.7/astropy
>>
>> x86_64-linux-gnu-gcc -pthread -fno-strict-aliasing -DNDEBUG -g -fwrapv
>> -O2 -Wall
>> -Wstrict-prototypes -fPIC -I/usr/include/python2.7 -c astropy/_compiler.c
>> -o
>> build/temp.linux-x86_64-2.7/astropy/_compiler.o
>>
>> astropy/_compiler.c:1:20: fatal error: Python.h: File or directory not
>> found
>>
>>   #include <Python.h>
>>
>>                      ^
>>
>> compilation terminated.
>>
>> error: command 'x86_64-linux-gnu-gcc' failed with exit status 1
>>
>> ----------------------------------------
>> Cleaning up...
>> Command /usr/bin/python -c "import setuptools,
>>
>> tokenize;__file__='/tmp/pip_build_root/astropy/setup.py';exec(compile(getattr(tokenize,
>> 'open', open)(__file__).read().replace('\r\n', '\n'), __file__, 'exec'))"
>> install --record /tmp/pip-nXWLvE-record/install-record.txt
>> --single-version-externally-managed --compile failed with error code 1 in
>> /tmp/pip_build_root/astropy
>> Traceback (most recent call last):
>>    File "/usr/bin/pip", line 9, in <module>
>>      load_entry_point('pip==1.5.4', 'console_scripts', 'pip')()
>>    File "/usr/lib/python2.7/dist-packages/pip/__init__.py", line 235, in
>> main
>>      return command.main(cmd_args)
>>    File "/usr/lib/python2.7/dist-packages/pip/basecommand.py", line 161,
>> in main
>>      text = '\n'.join(complete_log)
>> UnicodeDecodeError: 'ascii' codec can't decode byte 0xc3 in position 69:
>> ordinal
>> not in range(128)
>> = = =
>>
>>
>> _______________________________________________
>> AstroPy mailing list
>> AstroPy at scipy.org
>> https://mail.scipy.org/mailman/listinfo/astropy
>>
>>
> _______________________________________________
> AstroPy mailing list
> AstroPy at scipy.org
> https://mail.scipy.org/mailman/listinfo/astropy
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/astropy/attachments/20151221/3a18fd52/attachment.html>