Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix Travis CI for Python 3.3 and conda 4.x #812

Merged
merged 5 commits into from
Mar 8, 2016

Conversation

jakirkham
Copy link
Member

Fixes #810
Includes #811
Includes #809

As of conda 4.0, Python 3.3 is not supported. However, testing continues to happen here for Python 3.3. We have added a workaround to handle installing a version of conda 3.x here for Python 3.3. Also, an error message changes in conda 4.0 so we have included a different check for that warning message. However, if conda 3.x is installed for the Python 3.3 case the old error message check is used instead.

@jakirkham jakirkham changed the title Fix CI conda 4 Fix CI for Python 3.3 and conda 4.x Mar 8, 2016
@jakirkham
Copy link
Member Author

@groutr, would you mind having a look at this and if there are no issues merge it. This will fix Travis CI for conda build to work on Python 3.3 (using conda 3.x) and conda 4.x on all other platforms.

@jakirkham jakirkham changed the title Fix CI for Python 3.3 and conda 4.x Fix Travis CI for Python 3.3 and conda 4.x Mar 8, 2016
@jakirkham
Copy link
Member Author

Passes all tests as expected.

@stuarteberg
Copy link
Contributor

👍

@groutr
Copy link
Contributor

groutr commented Mar 8, 2016

So, there might be a subtle difference. Python 3.3 is should still be supported as a target (ie conda-build should be able to still build packages for python 3.3). However, it looks like conda 4.x itself has dropped support for Python 3.3 (or at least it doesn't test against 3.3).

@jakirkham
Copy link
Member Author

Not sure what you are proposing. The changes here do support Python 3.3 still. We just must install conda 3.x on Python 3.3 for the reasons you have mentioned. The test suite has been updated to support conda 3.x and conda 4.x.

# Get the version of conda as the error message changed in conda 4.
set +e
echo $(conda -V 2>&1) | grep "conda 3\..*"
export IS_CONDA_3=$?
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Switched to treat conda 3 as the special case instead of conda 4. The effect is the same.

@groutr
Copy link
Contributor

groutr commented Mar 8, 2016

The code looks good to me. Pending the CI tests, I think this is good to merge. Thanks for the investigative work.

@jakirkham
Copy link
Member Author

Of course. Looks like it just passed. Please let me know if there is anything else.

groutr added a commit that referenced this pull request Mar 8, 2016
Fix Travis CI for Python 3.3 and conda 4.x
@groutr groutr merged commit ef062a2 into conda:master Mar 8, 2016
@jakirkham jakirkham deleted the fix_ci_conda_4 branch March 8, 2016 21:34
@jakirkham
Copy link
Member Author

There was a build failure on master, but it seems to be caused by too many svn requests. Should probably just rebuild it.

svn: Server sent unexpected return value (429 Too Many Requests) in response to OPTIONS request for 'https://github.com/conda/conda-build'

@github-actions github-actions bot added the locked [bot] locked due to inactivity label May 17, 2022
@github-actions github-actions bot locked as resolved and limited conversation to collaborators May 17, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
locked [bot] locked due to inactivity
Projects
None yet
Development

Successfully merging this pull request may close these issues.

CI: Python 3.3 has unsatisfiable dependencies
3 participants