trame v3 is out... #295
jourdain
announced in
Announcements
Replies: 2 comments 4 replies
-
@jourdain what happened to the trame module/package from trame.widgets? We are using trame.ClientStateChange and after testing an upgrade to trame v3 we now get this error? ImportError: cannot import name 'trame' from 'trame.widgets' (/app/.venv/lib/python3.9/site-packages/trame/widgets/init.py) |
Beta Was this translation helpful? Give feedback.
4 replies
-
|
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
And I most likely broke your project if you did not bound the version of trame in your dependency.
But don't worry, upgrading your project is going to be easy.
The new version of trame is removing its implicit dependencies to external widgets and therefore require your application to list the widgets that you are leveraging (i.e.: vtk, vuetify, plotly, vega, router, markdown, matplotlib, deckgl, simput...) as a dependency (
trame-vtk
,trame-vuetify
,trame-*
, ...).The next thing that won't break your project today but will on January 2024 is the change of default client type. You may not know it, but trame is based on vue and support both vue2 and vue3. Right now the default client is using vue2 which has a EOL on December 2023. So we aim to change the default to vue3 in January. Both versions will keep working past that date and core widgets will be made compatible for vue2 and vue3. So the only thing you have to do is to properly assign the client_type that you relying on. So just add the following line to your code base
server.client_type = 'vue2'
.Beta Was this translation helpful? Give feedback.
All reactions