-
Notifications
You must be signed in to change notification settings - Fork 5
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
safety: ignore py vulnerabiility #129
Conversation
It's a test dependency, so it's safe to ignore.
|
@Nusnus thanks! do you plan to release it soon? |
thanks @Nusnus . looked into this, but it seems actually 1.0 is a significant change compared to the previous wrapper around Or does 1.0+ support basic setup (no Docker, basic file based backend from Celery, Kombu)? |
v1.x.x basically adds a new layer on top of the legacy QA infrastructure for simulating production-like Celery environments to enable tests the legacy infra was unable to allow. It does that by creating docker containers for all of the architecture entities (workers, brokers, etc.) and making sure they can interact with each other on one side while providing an API to control each entity in a pytest test function. This was developed to allow adding a new smoke tests layer to the QA tests of Celery. For more info, see the official docs. As a client of To elaborate on that a bit, because I understand it may be confusing, the v0.0.0 plugin is basically installing a subset of the celery repo itself, the If you’re planning to use these new features, but also have tests that are using the |
It's a test dependency, so it's safe to ignore.
Revert when celery/pytest-celery#305 gets merged.