Best Python code snippet using refurb_python
mypy_visitor.py
Source: mypy_visitor.py
...72 Any existing mypy module that was imported before needs to be reimported73 before use within the context.74 Upon exiting, the previous implementations are restored.75 """76 def loaded_mypy_modules() -> Iterator[str]:77 """Covenient block to get names of imported mypy modules"""78 for mod_name in sys.modules:79 if mod_name == "mypy" or mod_name.startswith("mypy."):80 yield mod_name81 # First, backup all imported mypy modules and remove them from sys.modules,82 # so they will not be found in resolution83 saved_mypy = {}84 for mod_name in list(loaded_mypy_modules()):85 saved_mypy[mod_name] = sys.modules.pop(mod_name)86 with prefer_pure_python_imports():87 # After the modules are clean, ensure the newly imported mypy modules88 # are their pure python versions.89 # - Pure python: methods are FunctionType90 # - Native: methods are MethodDescriptorType91 from mypy.traverser import TraverserVisitor92 assert isinstance(93 typing.cast(FunctionType, TraverserVisitor.visit_var), FunctionType94 )95 # Give back control96 yield97 # We're back and this is where we do cleanup. We'll remove all imported98 # mypy modules (pure python) and restore the previously backed-up ones99 # (allegedly native implementations)100 for mod_name in list(loaded_mypy_modules()):101 del sys.modules[mod_name]102 for mod_name, module in saved_mypy.items():103 sys.modules[mod_name] = module104def _get_class_globals(target_class: type, localns: Namespace) -> Namespace:105 """106 Get the globals namespace for the full class hierarchy that starts in107 target_class.108 This follows the recommendation of PEP-563 to resolve stringified type109 annotations at runtime.110 """111 all_globals = localns.copy()112 for base in inspect.getmro(target_class):113 all_globals.update(vars(sys.modules[base.__module__]))114 return all_globals...
Check out the latest blogs from LambdaTest on this topic:
I routinely come across test strategy documents when working with customers. They are lengthy—100 pages or more—and packed with monotonous text that is routinely reused from one project to another. Yawn once more— the test halt and resume circumstances, the defect management procedure, entrance and exit criteria, unnecessary generic risks, and in fact, one often-used model replicates the requirements of textbook testing, from stress to systems integration.
These days, development teams depend heavily on feedback from automated tests to evaluate the quality of the system they are working on.
Entering the world of testers, one question started to formulate in my mind: “what is the reason that bugs happen?”.
Are members of agile teams different from members of other teams? Both yes and no. Yes, because some of the behaviors we observe in agile teams are more distinct than in non-agile teams. And no, because we are talking about individuals!
Learn to execute automation testing from scratch with LambdaTest Learning Hub. Right from setting up the prerequisites to run your first automation test, to following best practices and diving deeper into advanced test scenarios. LambdaTest Learning Hubs compile a list of step-by-step guides to help you be proficient with different test automation frameworks i.e. Selenium, Cypress, TestNG etc.
You could also refer to video tutorials over LambdaTest YouTube channel to get step by step demonstration from industry experts.
Get 100 minutes of automation test minutes FREE!!