Use compatible release (tilde-style) versioning for dependencies. Assuming the maintainers of the dependencies use semantic versioning this will prevent backwards-incompatible changes from being unexpectedly introduced, while still getting updates that are compatible with what currently works.
I added an additional constraint to the traitlets dependency, which satisfies option 1 of https://github.com/NREL/ditto/issues/426. However, option 3 is my preferred solution, which would allow for the removal of the second version constraint on traitlets. I submitted a separate PR https://github.com/NREL/ditto/pull/429 for that change.
Use compatible release (tilde-style) versioning for dependencies. Assuming the maintainers of the dependencies use semantic versioning this will prevent backwards-incompatible changes from being unexpectedly introduced, while still getting updates that are compatible with what currently works.
I added an additional constraint to the traitlets dependency, which satisfies option 1 of https://github.com/NREL/ditto/issues/426. However, option 3 is my preferred solution, which would allow for the removal of the second version constraint on traitlets. I submitted a separate PR https://github.com/NREL/ditto/pull/429 for that change.