Skip to content

Conversation

@TomAugspurger
Copy link
Contributor

Closes #29330

This was most likely due to inconsistent constraints between conda-forge & defaults.

Also, pinning to 3.7 for now until the 3.8 buildout is done to make the solver's life a bit easier.

* Switch to conda-forge only
* Remove unused pytest-mock
* Pin to 3.7 until the buildout is done
@TomAugspurger TomAugspurger added this to the 1.0 milestone Nov 6, 2019
@jreback jreback added the Build Library building on various platforms label Nov 6, 2019
@TomAugspurger
Copy link
Contributor Author

Merging this before CI finishes because we have a sprint right now.

@TomAugspurger TomAugspurger merged commit 8b0f806 into pandas-dev:master Nov 6, 2019
@TomAugspurger TomAugspurger deleted the cleanup-env branch November 6, 2019 18:13
Reksbril pushed a commit to Reksbril/pandas that referenced this pull request Nov 18, 2019
* DEV: Cleanup dev environment
proost pushed a commit to proost/pandas that referenced this pull request Dec 19, 2019
* DEV: Cleanup dev environment
proost pushed a commit to proost/pandas that referenced this pull request Dec 19, 2019
* DEV: Cleanup dev environment
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Build Library building on various platforms

Projects

None yet

Development

Successfully merging this pull request may close these issues.

conda env create --file environment.yaml Fails with strict channel_priority

2 participants