-
Notifications
You must be signed in to change notification settings - Fork 8
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Try to simplify NApps requirements/dev.txt
for trusted transitive dependencies from kytos-ng
org
#338
Comments
requirements/dev.txt
for NApps for trusted transitive dependencies from kytos-ng
orgrequirements/dev.txt
for trusted transitive dependencies from kytos-ng
org
We ended up with a stricter pinning approach some time ago, but that was wen even third parties weren't strictly pinned. Also, this opens the possibility for |
After doing some research, with We can use a concept of
Notice that during installation
|
Another alternative for dev requirements it would be to rely on |
Related NApps PRs have landed. |
Currently, NApps are also pinning transitive dependencies from
kytos
in theirrequirements/dev.txt
, which is typically what's generally recommended for Python projects, but in this case specificallykytos
has already pinned on itsrequirements/run.txt
so it's guaranteed that NApps will have it, and we have ownership ofkytos
so we can trust it on NApps unlike other third-parties dependencies.If we manage to simplify this, then wen regenerating core dependencies, it'll only require a single PR as opposed to dozens in cases when it doesn't completely break compatibility (which tends to be most the vast majority of the cases when minor upstream updates or dependencies are bumped), which will drastically improve our team work flow.
The text was updated successfully, but these errors were encountered: