This post provides important advice for all Conan packagers (especially new ones) which intends to help sidestep a pitfall which has claimed many a packager in the past. When you start working with Conan, you discover that it uses a python class as its descriptor format. This is absolutely a great design, however it includes class variables which are used in class methods. As such, users might be tempted use class variables to share state, but beware… it’s a trap.

## The Trap: A Simple Example


class MyPackageConan(ConanFile):
name = "name"
version = "1.0.0"
something = ""
some_dynamic_path = ""

def source(self):
self.something = "Hello"
some_dynamic_path = find_some_dynamic_path()

def build(self):
print(self.something) # prints "Hello"
use_some_dynamic_path(some_dynamic_path)

def package(self):
print(self.something) # prints "Hello"
use_some_dynamic_path(some_dynamic_path)


If you have the recipe above and run conan create . yourname/testing, your recipe will behave as expected. The source() build() and package() methods will successfully share state, and the example will be able to successfully build and package based on the some_dynamic_path variable that was set in the source() method.

You might be happy and think you created a great package. Unfortunately, it’s flawed.

## Different Conan Commands

The challenge is that there are many different Conan commands which utilize different methods from the recipe, often in isolation. For example, the source(), build() methods won’t be called at all when you run conan package command. Thus, the recipe in the example above will not work with conan package command (nor conan build). Obviously, it’s really annoying to have recipe’s for which some commands work and not others. The fact that the conan create recipe works fine adds to the problem a bit, because it means many new packagers won’t discover the problem until some later date. Often times, it’s other package users and future maintainers of a recipe who discover the problem at which point it’s all different kinds of bad.

The best approach for packagers is simply to imagine that a new instance of your ConanFile is created for each method execution, and the instance is destroyed immediately after the method completes. The conan create command doesn’t work like this, but several others do. So, if you think of it this way you will avoid the biggest pitfall in writing Conan recipes. Here’s some pseudocode that demonstrates it visually:

Here’s how you probably think about it now:

class MyPackageConan(ConanFile):
name = "libname"
version = "1.0.0"
# etc...

def source(self):
# source stuff

def build(self):
# build stuff

def package(self):
# package stuff


class MyPackageConan(ConanFile):
name = "libname"
version = "1.0.0"
# etc...

def source(self):
# source stuff

class MyPackageConan(ConanFile):
name = "libname"
version = "1.0.0"
# etc...

def build(self):
# build stuff

class MyPackageConan(ConanFile):
name = "libname"
version = "1.0.0"
# etc...

def package(self):
# package stuff



## Summary

It seems trivial to think about each method invocation is a separate instance, however most new users dive into Conan and immediately start experimenting without reading all the docs (especially the later docs which talk about corner cases). In these cases, people often start testing with the conan create command and might get the idea that it’s the only command that they need to think about. As such, it gives these “scientists” a “false positive” that certain things work, and they go on experimenting with other things. It’s not a real “false positive” because it does “work”, but new users “don’t know what they don’t know” about the other commands. So, hopefully we’ve shed light on an otherwise shady topic.

Powered by Hydejack v6.6.1