Closed matthew-brett closed 2 years ago
Certainly. Do you think I should wait until we merge the existing PR or just go for it?
Maybe just release as is, so the PR has time to settle after it gets merged.
On Sat, 19 Feb 2022, 14:43 Zvi Baratz, @.***> wrote:
Certainly. Do you think I should wait until we merge the existing PR or just go for it?
— Reply to this email directly, view it on GitHub https://github.com/open-dicom/dicom_parser/issues/87#issuecomment-1046033513, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAAQQHHXVPUBEYPNWOQ3C63U36UAJANCNFSM5O2O43QQ . Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
You are receiving this because you authored the thread.Message ID: @.***>
Would you consider making a new release?
I just pip-installed Dicom_parser, and JupyterLab, and this gave me a broken JupyterLab:
This ends with output:
Notice the downgrade of Jinja. Next:
Gives:
Web search gives this thread, which suggests:
Sure enough, this fixes it.
Repeating these steps, but installing from latest Master locally, does not downgrade Jinja2, and does not cause this error.
Maybe a new release would prevent this error?