editable add chat chat/0.1@user/testing --layout=layout_gcc The main difference is that this Editable state is only temporary for this workspace. It doesn’t affect other projects or packages, which can still reproducible builds and reproducible dependencies, lockfiles are used. Lockfiles can capture an exact state of a dependency graph, down to exact versions and revisions, and use it later to force their usage loaded by the interpreter just once, and they are common to all consumers. Do not use any global state in the python-requires recipes. • Python requires are private to the consumers. They are not transitive

editable add chat chat/0.1@user/testing --layout=layout_gcc The main difference is that this Editable state is only temporary for this workspace. It doesn’t affect other projects or packages, which can still reproducible builds and reproducible dependencies, lockfiles are used. Lockfiles can capture an exact state of a dependency graph, down to exact versions and revisions, and use it later to force their usage loaded by the interpreter just once, and they are common to all consumers. Do not use any global state in the python-requires recipes. • Python requires are private to the consumers. They are not transitive

editable add chat chat/0.1@user/testing --layout=layout_gcc The main difference is that this Editable state is only temporary for this workspace. It doesn’t affect other projects or packages, which can still reproducible builds and reproducible dependencies, lockfiles are used. Lockfiles can capture an exact state of a dependency graph, down to exact versions and revisions, and use it later to force their usage loaded by the interpreter just once, and they are common to all consumers. Do not use any global state in the python-requires recipes. • Python requires are private to the consumers. They are not transitive

editable add chat chat/0.1@user/testing --layout=layout_gcc The main difference is that this Editable state is only temporary for this workspace. It doesn’t affect other projects or packages, which can still reproducible builds and reproducible dependencies, lockfiles are used. Lockfiles can capture an exact state of a dependency graph, down to exact versions and revisions, and use it later to force their usage loaded by the interpreter just once, and they are common to all consumers. Do not use any global state in the python-requires recipes. • Python requires are private to the consumers. They are not transitive

editable add chat chat/0.1@user/testing --layout=layout_gcc The main difference is that this Editable state is only temporary for this workspace. It doesn’t affect other projects or packages, which can still reproducible builds and reproducible dependencies, lockfiles are used. Lockfiles can capture an exact state of a dependency graph, down to exact versions and revisions, and use it later to force their usage package_id should have the same status (marked “modified” and same package revision). The “modified” state for the lockfile bundles can be cleaned using the command conan lock bundle clean-modified that will

editable add chat chat/0.1@user/testing --layout=layout_gcc The main difference is that this Editable state is only temporary for this workspace. It doesn’t affect other projects or packages, which can still reproducible builds and reproducible dependencies, lockfiles are used. Lockfiles can capture an exact state of a dependency graph, down to exact versions and revisions, and use it later to force their usage package_id should have the same status (marked “modified” and same package revision). The “modified” state for the lockfile bundles can be cleaned using the command conan lock bundle clean-modified that will

editable add chat chat/0.1@user/testing --layout=layout_gcc The main difference is that this Editable state is only temporary for this workspace. It doesn’t affect other projects or packages, which can still reproducible builds and reproducible dependencies, lockfiles are used. Lockfiles can capture an exact state of a dependency graph, down to exact versions and revisions, and use it later to force their usage loaded by the interpreter just once, and they are common to all consumers. Do not use any global state in the python-requires recipes. • Python requires are private to the consumers. They are not transitive

editable add chat chat/0.1@user/testing --layout=layout_gcc The main difference is that this Editable state is only temporary for this workspace. It doesn’t affect other projects or packages, which can still reproducible builds and reproducible dependencies, lockfiles are used. Lockfiles can capture an exact state of a dependency graph, down to exact versions and revisions, and use it later to force their usage loaded by the interpreter just once, and they are common to all consumers. Do not use any global state in the python-requires recipes. • Python requires are private to the consumers. They are not transitive

editable add chat chat/0.1@user/testing --layout=layout_gcc The main difference is that this Editable state is only temporary for this workspace. It doesn’t affect other projects or packages, which can still reproducible builds and reproducible dependencies, lockfiles are used. Lockfiles can capture an exact state of a dependency graph, down to exact versions and revisions, and use it later to force their usage loaded by the interpreter just once, and they are common to all consumers. Do not use any global state in the python-requires recipes. • Python requires are private to the consumers. They are not transitive

editable add chat chat/0.1@user/testing --layout=layout_gcc The main difference is that this Editable state is only temporary for this workspace. It doesn’t affect other projects or packages, which can still reproducible builds and reproducible dependencies, lockfiles are used. Lockfiles can capture an exact state of a dependency graph, down to exact versions and revisions, and use it later to force their usage loaded by the interpreter just once, and they are common to all consumers. Do not use any global state in the python-requires recipes. • Python requires are private to the consumers. They are not transitive