We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
@benchuang11046 Notice that we remove all versions of requirements(here). This might cause some issues when using run_jnb because of mismatch version with nbconvert. Maybe we still need to use fixed version of all modules in both jupyter_api_default_requirements.txt and jupyter_app_default_requirements.txt. What's your thought?
run_jnb
nbconvert
The text was updated successfully, but these errors were encountered:
Yes, we need to fix version in both default requirements. Here will append user requirements if the requirement not in default. Therefore, it must be the fix version in analytics requirements.txt. Based on the jupyter_api_default_requirements.txt and jupyter_app_default_requirements.txt. I think it's ok.
Sorry, something went wrong.
Ok, I found I just missing some lines of code. Understand what happened about requirements in parser.py.
parser.py
No branches or pull requests
@benchuang11046 Notice that we remove all versions of requirements(here). This might cause some issues when using
run_jnb
because of mismatch version withnbconvert
. Maybe we still need to use fixed version of all modules in both jupyter_api_default_requirements.txt and jupyter_app_default_requirements.txt. What's your thought?The text was updated successfully, but these errors were encountered: