Closed DoDoENT closed 1 year ago
Thanks for the report @DoDoENT
Indeed every crash is a bug by definition.
I am proposing https://github.com/conan-io/conan/pull/14413 to allow remotes usage to automatically resolve missing python_requires
I tried installing your branch, and it indeed works:
$ conan editable add .
conanfile_utils/0.1.0@nenad/testing: Not found in local cache, looking in remotes...
conanfile_utils/0.1.0@nenad/testing: Checking remote: mbtemp
conanfile_utils/0.1.0@nenad/testing: Downloaded recipe revision 22e39d9779ab95f144c79a6c34b21146
Reference 'ml_models_image_capture/1.0.0' in editable mode
However, what's weird is that conan editable --help
does not list new --remote
and --no-remote
flags:
$ conan editable --help
usage: conan editable [-h] [-v [V]] {add,list,remove} ...
Allow working with a package that resides in user folder.
positional arguments:
{add,list,remove} sub-command help
add Define the given <path> location as the package <reference>, so when this package is required, it is used from this <path> location instead of the cache.
list List all the packages in editable mode.
remove Remove the "editable" mode for this reference.
options:
-h, --help show this help message and exit
-v [V] Level of detail of the output. Valid options from less verbose to more verbose: -vquiet, -verror, -vwarning, -vnotice, -vstatus, -v or -vverbose, -vv or -vdebug, -vvv or -vtrace
nor
$ conan editable add --help
usage: conan editable add [-h] [-v [V]] [--name NAME] [--version VERSION] [--user USER] [--channel CHANNEL] [-of OUTPUT_FOLDER] path
Define the given <path> location as the package <reference>, so when this package is required, it is used from this <path> location instead of the cache.
positional arguments:
path Path to the package folder in the user workspace
options:
-h, --help show this help message and exit
-v [V] Level of detail of the output. Valid options from less verbose to more verbose: -vquiet, -verror, -vwarning, -vnotice, -vstatus, -v or -vverbose, -vv or -vdebug, -vvv or -vtrace
--name NAME Provide a package name if not specified in conanfile
--version VERSION Provide a package version if not specified in conanfile
--user USER Provide a user if not specified in conanfile
--channel CHANNEL Provide a channel if not specified in conanfile
-of OUTPUT_FOLDER, --output-folder OUTPUT_FOLDER
The root output folder for generated and build files
Could it be that due to not having -dev
tag, some python files were mixed with my previous conan 2.0.9 installation? But, this time I made sure to delete conan completely from the venv before installing it from your branch.
Sorry, the bump to specify "-dev" was still not done, I have just done it in https://github.com/conan-io/conan/commit/0ad3bd744524bcbdb7d508536e94eb549d6a938b, I hope it helps to avoid future issues
Environment details
Steps to reproduce
conan remove "*" --confirm
.conan editable add .
The workaround is to install at least recipes for all dependencies. The actual binaries are not needed. After that, the package can be put into editable mode.
For the rationale of how I discovered that: it happened on my CI job, where I need to put a package into editable mode in order to cross-build it, as discussed here.
Logs