Hi, your project yahoo-groups-backup(commit id: be44eb61e44e49f9af49dc81c7d1704daf4c8f3d) requires "schema==0.5.0" in its dependency. After analyzing the source code, we found that the following versions of schema can also be suitable, i.e., schema 0.6.0, since all functions that you directly (5 APIs: schema.Use.validate, schema.And.init, schema.Use.init, schema.Schema.init, schema.SchemaError.init) or indirectly (propagate to 0 schema's internal APIs and 0 outsider APIs) used from the package have not been changed in these versions, thus not affecting your usage.
Therefore, we believe that it is quite safe to loose your dependency on schema from "schema==0.5.0" to "schema>=0.5.0,<=0.6.0". This will improve the applicability of yahoo-groups-backup and reduce the possibility of any further dependency conflict with other projects.
May I pull a request to further loosen the dependency on schema?
By the way, could you please tell us whether such an automatic tool for dependency analysis may be potentially helpful for maintaining dependencies easier during your development?
Hi, your project yahoo-groups-backup(commit id: be44eb61e44e49f9af49dc81c7d1704daf4c8f3d) requires "schema==0.5.0" in its dependency. After analyzing the source code, we found that the following versions of schema can also be suitable, i.e., schema 0.6.0, since all functions that you directly (5 APIs: schema.Use.validate, schema.And.init, schema.Use.init, schema.Schema.init, schema.SchemaError.init) or indirectly (propagate to 0 schema's internal APIs and 0 outsider APIs) used from the package have not been changed in these versions, thus not affecting your usage.
Therefore, we believe that it is quite safe to loose your dependency on schema from "schema==0.5.0" to "schema>=0.5.0,<=0.6.0". This will improve the applicability of yahoo-groups-backup and reduce the possibility of any further dependency conflict with other projects.
May I pull a request to further loosen the dependency on schema?
By the way, could you please tell us whether such an automatic tool for dependency analysis may be potentially helpful for maintaining dependencies easier during your development?