1👍
Well, here you have multiple options on how to properly handle your needs.
As for django_plotly_dash
, you may check their setup.py file. Note that they expect you to have Django>=2.2,<4.0.0
. So it’s understandable that installation automatically downgrades your Django
version.
So here are the options you may consider:
- Preferable if you really need
django_plotly_dash
lib: downgrade yourDjango
version; - If you have some alternative solutions: look for another solution (get rid of
django_plotly_dash
); - If you feel like you could handle possible issues: fork
django_plotly_dash
, then update setup.pyDjango
requirement toDjango>=2.2
, then install the lib from your personal repo. Again, that may cause you a lot of issues, so you’ll need to test everything properly.
As a bonus to the last option, if you’ll make a successful upgrade, you may make a PR to an original repo and thus contribute to an open-source project.
0👍
Downgrading and upgrading versions can definitely break your project. Especially when you are downgrading major versions.
For your next project you should use the LTS version, not the latest. Especially if you intend to use that code in a production environment. Tools’ developers will consider supporting LTS versions and not the latest versions. The current LTS version for Django is 3.2.
According to the roadmap the next LTS version will be 4.2 in 2023.
I’d consider just using plotly or another library because you have to downgrade many packages to support Dash. Unless you decide to downgrade to use the LTS version.