Open mccalluc opened 1 month ago
I think it makes sense to pin the dependencies for devs, but not to pin them for users. Should add another axis to the test matrix and try to install w/ and w/o pinned versions, so we'll have a check that it works with the latest versions, but if there is a failure, the pinned versions will help us narrow down what changed.
The build and tests here are relatively light weight, so I don't feel bad doubling them.
I thought DP Wizard was an application. In what way is it a library?
In what way is it a library?
There is the idea that dp-wizard might be integrated with pysyft, or something like that, so another piece of software would handle user management and access control. This is very vague, but it does suggest that it would be good not paint ourselves into a corner with overly tight dependency version requirements.
If it's an application, we should aggressively lock dependencies (including in pyproject.toml)... but if it's a library that should play well with other software, we should keep them loose.
Not sure which is the best approach right now.
Related