You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I just updated the pysiaf package to v0.6.1 and in trying to update it in astroconda-contrib, I updated the meta.yaml flie with the new version # and one new package requirement, and then ran the line conda build -c http://ssb.stsci.edu/astroconda --skip-existing --python=3.5 pysiaf as a check. It failed for python 3.5, finding tons of conflicts during the Attempting to finalize metadata for pysiaf section, but passed when I set it to python 3.6.
Does astroconda-contrib require that packages pass in python 3.5 to be included (since that's the version used in the ReadtheDocs example)? Also, all our dependencies seem to be 3.5 compatible, but does this build process failing indicate that the package as a whole is somehow no longer python 3.5 compatible? (I'm not sure exactly what is happening within this build command)
I just updated the
pysiaf
package tov0.6.1
and in trying to update it inastroconda-contrib
, I updated themeta.yaml
flie with the new version # and one new package requirement, and then ran the lineconda build -c http://ssb.stsci.edu/astroconda --skip-existing --python=3.5 pysiaf
as a check. It failed for python 3.5, finding tons of conflicts during theAttempting to finalize metadata for pysiaf
section, but passed when I set it to python 3.6.Does
astroconda-contrib
require that packages pass in python 3.5 to be included (since that's the version used in the ReadtheDocs example)? Also, all our dependencies seem to be 3.5 compatible, but does this build process failing indicate that the package as a whole is somehow no longer python 3.5 compatible? (I'm not sure exactly what is happening within this build command)tagging @Johannes-Sahlmann
The text was updated successfully, but these errors were encountered: