Understanding the flexibility of using conanfile.py vs conanfile.txt section obsolete

[golemik98]

I am reading the docs version 2.0 and see that examples2 repository do not match what tutorial docs says about examples2/tutorial/consuming_packages/conanfile_py. Is it outdated? Actual folder looks like this:

.
├── CMakeLists.txt
├── complete_CMakeLists.txt
├── complete_conanfile.py
├── conanfile.py
├── run_example.py
└── src
    ├── complete_main.c
    └── main.c

1 directory, 7 files

[memsharded]

Hi @golemik98

It is not outdated, but probably needs some clarification. The complete_* files are the "final" state after the tutorial has been finished. The idea is that the conanfile.py and CMakeLists.txt and the src/main.c is the starting point of that tutorial, and after all the changes have been done (add layout(), conditional requirements), the resulting files would be the complete_xxx files.

We use the complete_xxx files to run in CI and make sure it works.