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

Is it possible to allow for a new version of voilà? #124

Closed
jrklasen opened this issue Apr 27, 2022 · 5 comments · Fixed by #154
Closed

Is it possible to allow for a new version of voilà? #124

jrklasen opened this issue Apr 27, 2022 · 5 comments · Fixed by #154

Comments

@jrklasen
Copy link

The Voilà version is set to be <0.3 is there a reason for this restriction?

@danielfrg
Copy link
Owner

Mostly because they were making big changes and I wanted to keep things tight at that point.

I imagine updating would require some changes on the package so might take a minute to update. I will try to test soon

@jmp75
Copy link

jmp75 commented Sep 28, 2022

I think I bumped into an issue related to this, adding jupyter-flex from conda-forge to an environment; voila <0.3 seem to use a deprecated feature of jinja2 :

ImportError: cannot import name 'contextfilter' from 'jinja2' (/blah/envs/bm/lib/python3.9/site-packages/jinja2/__init__.py)

where:

jinja2                    3.1.2              pyhd8ed1ab_1    conda-forge

I am trying to install the jupyter-flex python package from source in dev mode, see if I can help. I am following the contribution instructions, but am a bit unsure of what I am doing (unfamiliar with the javascript world).

@isabelizimm
Copy link

Adding onto this issue-- I've enjoyed using jupyter-flex, but loosening the voila requirements would be super helpful! I had a lot of troubles getting an install with no dependency conflicts, primarily due to the voila constraint.

@danielfrg
Copy link
Owner

Library is updated to work with voila 0.4 but I need to update some docs.
Hopefully today I can release a quick update

@danielfrg
Copy link
Owner

0.9.1 has been released. It should solve this issue

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

Successfully merging a pull request may close this issue.

4 participants