Skip to content

Conversation

@rossbar
Copy link
Collaborator

@rossbar rossbar commented Jun 25, 2022

For some reason the conda environment isn't working. My suspicion is that it's due to sphinx 5 - AFAIK the executablebooks tooling doesn't support sphinx 5 yet, so I would expect this to have been taken care of by the conda dependency resolver. Pip seems to get this right anyways...

Attempt number 1: manually pin sphinx.

I don't know why the conda resolver isn't doing this already...
@rossbar
Copy link
Collaborator Author

rossbar commented Jun 25, 2022

Okay that seems to have worked 🤷. I guess there may be a problem with pinning of one or more of the executablebooks packages on conda-forge? It'd be nice to fix this upstream, but in the meantime this gets our CI passing again. If anyone has experience with conda packaging and wants to fix this "properly" that'd be great!

@rossbar
Copy link
Collaborator Author

rossbar commented Jul 12, 2022

I'm just going to go ahead an merge this so our CI is green again. I still suspect this is a packaging problem with one or more of the executablebooks projects on conda-forge; I'll open an issue to remind us to test the removal of this pin in the future, as this will (should? hopefully?) eventually be fixed upstream.

@melissawm
Copy link
Member

Thanks, @rossbar !

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants