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

better describe how to build the environment #77

Open
12rambau opened this issue Oct 18, 2022 · 1 comment
Open

better describe how to build the environment #77

12rambau opened this issue Oct 18, 2022 · 1 comment
Labels
documentation Improvements or additions to documentation

Comments

@12rambau
Copy link
Contributor

I'm a regular python developer so I know how to build an environment using pip based on the requirement.txt file, the setup.py in or out of a venv. I can more or less do the same using conda and a environment.yml. I never directly deal with either the .bz2 or the .whl of the tools I'm using. I think this describe more or less the classic python lib developer and thus the classic Sphinx user.

Would it be possible to improve the documentation to better understand how I can add matplotlib to the jupyterlite env ?

@12rambau 12rambau added the documentation Improvements or additions to documentation label Oct 18, 2022
@martinRenou
Copy link
Member

Would it be possible to improve the documentation to better understand how I can add matplotlib to the jupyterlite env ?

Definitely we should 👍🏽

What is a federated_extention ? at the moment google result is pointing to a jupyterlite issue which gives no better understanding (https://www.google.com/search?client=safari&rls=en&q=numpy+federated+extension&ie=UTF-8&oe=UTF-8)

A federated extension is an extension for the JupyterLab front-end. In the simple case of Matplotlib, you should not need to know what this is.

In the case of bqplot here, bqplot has both a Python package and a front-end extension based on d3js that is a federated extension.

why do you skip sys_prefix in the exemple ?

This config entry could probably be removed to simplify the config.


I think we should have two sections in the docs:

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Improvements or additions to documentation
Projects
None yet
Development

No branches or pull requests

2 participants