Update install instructions for dask-dev enviornment
See original GitHub issueThe Development environment Install section of the docs says
conda env create -n dask-dev -f continuous_integration/environment-latest.yaml
conda activate dask-dev
python -m pip install --no-deps -e .
But we got rid of environment-latest.yaml
on https://github.com/dask/dask/commit/5bc14dc7b62f129622c3f11fbe7119c13836de26
We should now point to use environment-3.9.yaml
unless we recommend something different.
The file to modify is: https://github.com/dask/dask/blob/main/docs/source/develop.rst
Issue Analytics
- State:
- Created 2 years ago
- Comments:8 (8 by maintainers)
Top Results From Across the Web
Part 1. Installation | Dash for Python Documentation | Plotly
How to install and upgrade Dash.
Read more >dash/CONTRIBUTING.md at dev · plotly/dash - GitHub
Once changes have been made in the specific directories, the dash-update-components command line tool can be used to update the build artifacts and ......
Read more >Dash by Plotly - Install on Anaconda Virtual Environment
Learn how to create virtual environments with conda and install Dash by Plotly. This will allow you to create awesome interactive data ...
Read more >Update the IDE and SDK Tools - Android Developers
Click the SDK Update Sites tab. · Click Add at the bottom of the window. · Enter the name and URL of the...
Read more >Development — django-plotly-dash documentation
Environment setup¶ ; The script creates a virtual environment and uses pip to install the package requirements from the ; During development, it...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
I’m going to close this, but ping @jrbourbeau so that he’s aware of the issue with the release process.
Rebuild worked, but we need to rethink our release process to get the stable build to complete properly. It looks like the build got messed up because when it tried to install distributed, that referenced dask 2021.11.2 and that wasn’t yet available.