James

> self.build_folder cannot be accessed in package_info(). When we are talking about ``editable`` packages, the definition of the package happens in ``layout()`` method, not in ``package_info()`` method. The ``self.build_folder`` is...

Hi @vasama Any further question or comment here? Thanks for the feedback.

> I feel like this is a recurring theme. My CMake build script is able to provide all of this information. I can emit a file listing all the relevant...

> Like I said, this seems like a recurring theme. I've made multiple issues where I've had problems with using build artifacts in editable mode. To me that tells that...

Hi @hlewin Thanks for the suggestion. I am trying to fully understand the flow of package creations, lets see if this is correct: - There is some ``sysroot`` installed somehow...

Hi @TareHimself The docs in https://docs.conan.io/2/reference/tools/system/pipenv.html#pipenv say that you can use the ``tools.system.pipenv:python_interpreter`` conf to define the Python interpreter that you want, is this what you were looking for?

> That helps if the Python version already exists, but I was thinking about installing a different Python in the virtual env, in cases where Python on the system is...

Thanks very much for the feedback @TareHimself That ``uv`` usage inside a ``pipenv`` sounds an interesting approach to be able to enforce a given python version. @davidsanfal is having a...

Hi @ErikTempelaarVO Thanks for the question. This sounds it could be some cache corruption. I'd try as a first thing to completely remove the Conan cache from that machine and...

Sorry, it seems that I was missing some details. Are you using the ``local-recipes-index`` feature? The one in https://docs.conan.io/2/devops/devops_local_recipes_index.html? Because you described that you were creating packages from a fork,...