deploy_test.py - Ambiguous import: "call" from package "mock"
Open
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 383
- Forks
- 93
- Avg merge
- 1d 3h
- Merged PRs (30d)
- 1
Description
tensorflow_cloud/core/tests/unit/deploy_test.py
line 32: from mock import call, patch: Ambiguous import: "call" from package "mock": cannot determine whether "call" is an attribute on the package, or a module .
line 32: from mock import call, patch: Ambiguous import: "patch" from package "mock": cannot determine whether "patch" is an attribute on the package, or a module.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with tensorflow_cloud/core/tests/unit/deploy_test.py at line 32 and inspect how the mock imports are used in that test. Run the relevant deploy unit tests or the project's static analysis to confirm the ambiguous-import warnings are resolved without changing test behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- testing-qa
- Issue type
- Bug
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 35/100