search

astroconda / astroconda-contrib

Community Submitted Conda Recipes
12 stars 38 forks source link

Build packages for python 3.8 and 3.9 #609

Open jdavies-st opened 4 years ago

jdavies-st commented 4 years ago

Currently all the conda packages here are only built for python<=3.7. Since 3.8 is out and useable, these packages should work under it as well.

jdavies-st commented 4 years ago

One small issue here is that if we do turn on python 3.8 builds for all current contrib packages, we will only have the latest versions of those packages (defined by the current recipe) useable with 3.8.

floydie7 commented 3 years ago

I would like to update this to now Python 3.9 as it was released back in October 2020.

floydie7 commented 2 years ago

I'd like to now update this to Python 3.10 as it was released in October 2021. What exactly is holding astroconda back on Python 3.7 and can I help fix it?

jdavies-st commented 2 years ago

Maybe we can update this issue with future plans for astroconda @nden? I suspect this is issue is now null and void going forward?

jluastro commented 2 years ago

What is the status? Will we ever get stsci meta-package support for python 3.9 and 3.10?

mgregg128 commented 2 years ago

This discussion is about the most relevant I have been able to find for my current problem, which involves trying to update astroconda to python3.9 (or at least 3.8 or greater). I ran into variable type conflicts in tweakreg when running the astrodrizzle example notebook on aligning sparse fields. The STARS help desk says that is because I needed to update my python3.6 installation of anaconda/astroconda to python3.9. I updated anaconda3 to the python3.9.12 level, but now astroconda refuses to install (it hangs on resolving the environment) when issuing the command:

conda create -n astroconda python=3.9 stsci
If I change the version to 3.7, it installs, but since anaconda is running 3.9, there are many other incompatibilities and the notebook in question fails on the very first step instead of tweakreg.
Sooooooooo... anyone have any advice or fixes? I apologize if this is the wrong forum for this kind of issue, but it seems the only place where anything along these lines is being discussed.
Thank you very much for any help!

mgregg128 commented 2 years ago

Apologies, should have mentioned that I'm on a MacBook Pro from 2017 running OSX 10.13.6 (High Sierra), which conceivably could be contributing to the problem... but I hope not. Thanks again.

floydie7 commented 2 years ago

conda create -n astroconda python=3.9 stsci

To be honest, at this point I've given up on the astroconda meta-package. I wasn't using many of the stsci-data-analysis or stsci-hst packages in my work. Also, with Python 3.10 as the current standard and 3.11 is on the horizon, I've since just rolled my own conda environment, cherry-picking all the packages I was using from the astroconda environment.

The easiest way I've found to set up and manage the environment is to create an environment file (see conda documentation).

Once you have your environment file set up you can then create the environment by running: conda env create -f environment.yml

mgregg128 commented 2 years ago

Thank you for the advice; Although I'm knowledgeable about stsci-hst software using iraf/pyraf, I'm still a bit of a newbie at python/conda etc., so your words make sense, and it will take me a while to get comfortable with rolling my own. Good advice though, because this morning I got a reply from the HST help desk that I have encountered a known bug and the astroconda meta-package is in fact non-functional as of 3.7 and up, and they gave me pretty much the same advice you have. This leaves me a bit gobsmacked that no one has bothered to edit the astroconda install page at stsci; unless I'm the only astroconda neophyte left on the planet, I must have plenty of company in this area and many work hours are being lost banging heads against this problem. Grrrr, as someone famous said. Thank you again for your help, I appreciate it very much.