and deterministic dependency graphs. • They are able to extend base classes more naturally without conflicts of ConanFile classes. 12.2.1 Introduction The python_requires feature is a very convenient will be 123 f = self.python_requires["other"].module.otherfunc("some-args") 12.2.2 Extending base classes A common use case would be to declare a base class with methods we want to reuse in several recipes make it available for reuse with: $ conan export . pyreq/0.1@user/channel Note that there are two classes in the recipe file: • MyBase is the one intended for inheritance and doesn’t extend ConanFile.

and deterministic dependency graphs. • They are able to extend base classes more naturally without conflicts of ConanFile classes. 12.2.1 Introduction The python_requires feature is a very convenient will be 123 f = self.python_requires["other"].module.otherfunc("some-args") 12.2.2 Extending base classes A common use case would be to declare a base class with methods we want to reuse in several recipes make it available for reuse with: $ conan export . pyreq/0.1@user/channel Note that there are two classes in the recipe file: • MyBase is the one intended for inheritance and doesn’t extend ConanFile.

and deterministic dependency graphs. • They are able to extend base classes more naturally without conflicts of ConanFile classes. 12.2.1 Introduction The python_requires feature is a very convenient will be 123 f = self.python_requires["other"].module.otherfunc("some-args") 12.2.2 Extending base classes A common use case would be to declare a base class with methods we want to reuse in several recipes make it available for reuse with: $ conan export . pyreq/0.1@user/channel Note that there are two classes in the recipe file: • MyBase is the one intended for inheritance and doesn’t extend ConanFile.

and deterministic dependency graphs. • They are able to extend base classes more naturally without conflicts of ConanFile classes. 13.2.1 Introduction The python_requires feature is a very convenient will be 123 f = self.python_requires["other"].module.otherfunc("some-args") 13.2.2 Extending base classes A common use case would be to declare a base class with methods we want to reuse in several recipes make it available for reuse with: $ conan export . pyreq/0.1@user/channel Note that there are two classes in the recipe file: • MyBase is the one intended for inheritance and doesn’t extend ConanFile.

and deterministic dependency graphs. • They are able to extend base classes more naturally without conflicts of ConanFile classes. 13.2.1 Introduction The python_requires feature is a very convenient will be 123 f = self.python_requires["other"].module.otherfunc("some-args") 13.2.2 Extending base classes A common use case would be to declare a base class with methods we want to reuse in several recipes make it available for reuse with: $ conan export . pyreq/0.1@user/channel Note that there are two classes in the recipe file: • MyBase is the one intended for inheritance and doesn’t extend ConanFile.

def build(self): # Responsible for␣ ˓→invoking the build system cmake = CMake(self) # Helper classes␣ ˓→are available for several build systems ... self.run("bin/unittests") # Run unit tests␣ ˓→compiled and deterministic dependency graphs. • They are able to extend base classes more naturally without conflicts of ConanFile classes. 14.2.1 Introduction The python_requires feature is a very convenient will be 123 f = self.python_requires["other"].module.otherfunc("some-args") 14.2.2 Extending base classes A common use case would be to declare a base class with methods we want to reuse in several recipes

and deterministic dependency graphs. • They are able to extend base classes more naturally without conflicts of ConanFile classes. 12.2.1 Introduction The python_requires feature is a very convenient will be 123 f = self.python_requires["other"].module.otherfunc("some-args") 12.2.2 Extending base classes A common use case would be to declare a base class with methods we want to reuse in several recipes make it available for reuse with: $ conan export . pyreq/0.1@user/channel Note that there are two classes in the recipe file: • MyBase is the one intended for inheritance and doesn’t extend ConanFile.

and deterministic dependency graphs. • They are able to extend base classes more naturally without conflicts of ConanFile classes. 13.2.1 Introduction The python_requires feature is a very convenient will be 123 f = self.python_requires["other"].module.otherfunc("some-args") 13.2.2 Extending base classes A common use case would be to declare a base class with methods we want to reuse in several recipes make it available for reuse with: $ conan export . pyreq/0.1@user/channel Note that there are two classes in the recipe file: • MyBase is the one intended for inheritance and doesn’t extend ConanFile.

and deterministic dependency graphs. • They are able to extend base classes more naturally without conflicts of ConanFile classes. 13.2.1 Introduction The python_requires feature is a very convenient will be 123 f = self.python_requires["other"].module.otherfunc("some-args") 13.2.2 Extending base classes A common use case would be to declare a base class with methods we want to reuse in several recipes make it available for reuse with: $ conan export . pyreq/0.1@user/channel Note that there are two classes in the recipe file: • MyBase is the one intended for inheritance and doesn’t extend ConanFile.

and deterministic dependency graphs. • They are able to extend base classes more naturally without conflicts of ConanFile classes. 13.2.1 Introduction The python_requires feature is a very convenient will be 123 f = self.python_requires["other"].module.otherfunc("some-args") 13.2.2 Extending base classes A common use case would be to declare a base class with methods we want to reuse in several recipes make it available for reuse with: $ conan export . pyreq/0.1@user/channel Note that there are two classes in the recipe file: • MyBase is the one intended for inheritance and doesn’t extend ConanFile.