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

DOC: use conda-forge in Ubuntu quickstart #14658

Merged
merged 1 commit into from
Aug 28, 2021
Merged

Conversation

fuglede
Copy link
Contributor

@fuglede fuglede commented Aug 28, 2021

Without this, none of pythran, sphinx-panels, or pydata-sphinx-theme can be found. The phrasing is taken from the corresponding point in the macOS workflow.

Reference issue

Closes gh-14654.

Copy link
Member

@tupui tupui left a comment

Choose a reason for hiding this comment

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

LGTM, thanks!

@tupui tupui merged commit 8853c61 into scipy:master Aug 28, 2021
@tupui tupui added the Documentation Issues related to the SciPy documentation. Also check https://github.com/scipy/scipy.org label Aug 28, 2021
@tupui tupui added this to the 1.8.0 milestone Aug 28, 2021
@mdhaber
Copy link
Contributor

mdhaber commented Aug 28, 2021

@fuglede @tupui just curious - did you try out the conda-forge compilers? Just checking because in the past not all compilers have been interchangeable, and I don't have easy access to a Linux machine right now to try

@fuglede
Copy link
Contributor Author

fuglede commented Aug 29, 2021

@fuglede @tupui just curious - did you try out the conda-forge compilers? Just checking because in the past not all compilers have been interchangeable, and I don't have easy access to a Linux machine right now to try

Yep, I was able to successfully build after getting all those packages with -c conda-forge in an otherwise empty conda environment, but I have a bunch of compilers on the OS level as well, and I didn't check if that helped me somehow. But in particular, I did also just use -c conda-forge (where, IIRC, with --add channels conda-forge, packages are still picked up from defaults with higher solver priority?) so my setup wouldn't be one-to-one what these docs give you.

It was also the only way I was able to get it building (without relying on Docker) where until a few months ago I could just build inplace with my OS compilers, avoid conda develop . and all of that, so although I can appreciate the reproducibility that this workflow offers, it did seem like a step backwards UX-wise for my own workflow.

@fuglede fuglede deleted the patch-7 branch August 29, 2021 05:48
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Documentation Issues related to the SciPy documentation. Also check https://github.com/scipy/scipy.org
Projects
None yet
Development

Successfully merging this pull request may close these issues.

DOC: Linux Devdocs workflow requires installing packages that don't exist
3 participants