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
requirements files for notebook #8393
Comments
We don't provide anything like that, but you could write a tool to do it if you want. The fiddly bit would be matching up import names to PyPI names (which are often the same, but they don't have to be). |
Here are 2 packages that can do this for Python code: https://github.com/bndr/pipreqs |
I was setting up my dev environment and there are a number of packages not listed in the requirements file, but necessary to develop ipython. This includes requests and nose - should we add a requirements-tests.txt file? |
@jamesfe we only used requirements.txt for unreleased dependencies. To install IPython and its testing dependencies use |
@minrk can we now remove requirements.txt again? The only thing left in it is traitlets, and I don't think IPython requires an unreleased version of traitlets. |
@takluyver yup, #9132. Also closing here, as we have no plans to implement requirements inside the notebook, and even if we did this is no longer the repo for it. |
Thanks! |
Is there any way to generate requirements files for notebook based on imported/used modules and packages?
The text was updated successfully, but these errors were encountered: