Dustin Lang <
dstn...@gmail.com> writes:
> Astrometry.net is compatible with both python2 and python3, but it
> doesn't get to choose how it gets run :) For this problem, you should
> probably ask the debian folks who packaged it; we don't run the
> scripts that way in the vanilla code.
The version we support depends on the distribution: In December 2018, we
switched fom Python 2 to Python 3 for the
astrometry.net Python
module. So, in Debian Stretch it is Python 2, Buster (currently Testing)
will get the Python 3 module. For Ubuntu, probably 19.04 will be the
first with the Python 3 module; therefore I guess this iy Python 2.
I must however say that I don't really understand the problem
here. Dylan, could you provide some system information (distribution,
astrometry.net version etc.)?
> You could also check your PYTHONPATH environment variable -- it looks
> like maybe it's finding an astrometry directory/package, but it
> doesn't have a "util" subdirectory? Can run python -c "import
> astrometry; print(astrometry.__file__)" to find out where it's finding
> astrometry.
That sounds sensible. What also could help is
$ ls -l /usr/lib/python2.7/dist-packages/astrometry/util/
to check whether the files are correctly installed.
On Sun, Apr 14, 2019 at 2:17 PM Dylan Gatlin <
dgat...@gmail.com> wrote:
> Any idea where this comes from? The images are normal and can open in
> DS9. /usr/bin/python is version 2.7.15rc1, which seems strange since
> I thought
astrometry.net runs on python3?
That looks like Ubuntu 18.04, right? At least, there are no bug reports
for
astrometry.net yet.
Best regards
Ole